Hi,
I've inherited a fair bit of undocumented stuff and work and usually I can work things out pretty well but this has me stumped. It's either a pretty nifty windows feature that I wasn't previously aware of or someone has pulled some proper weird voodoo trick on this server!
The OS is server 2003 with 1 drive split into 2 partitions. C: is pretty small and I needed to free up some space, we have an install of SQL2005 on there so I cleaned up a few old databases, shrunk a massive transaction log etc and was disappointed to find that I hadn't really freed up much space. Then I noticed that D: had a lot more space on it than previously.
Obviously the first thing I did was check that the databases were actually on C: and that I wasn't going mad. In the process of doing this I spotted that there is a "Program Files" folder on both C: and D: Nothing inherently bad about that, sometimes people install onto D: to save space on the primary drive. Then I realised that I can access SQL via either drive but somehow end up at the same actual files. They have matching file sizes, datestamps etc. If I create a file on one drive it's immediately visible on the other. It's as if the files are physically stored on D: but somehow show up in the Program Files path on C: as well.
Anyone seen anything like this before? I'd like to understand what's going on really as this is a new one on me.
I've inherited a fair bit of undocumented stuff and work and usually I can work things out pretty well but this has me stumped. It's either a pretty nifty windows feature that I wasn't previously aware of or someone has pulled some proper weird voodoo trick on this server!
The OS is server 2003 with 1 drive split into 2 partitions. C: is pretty small and I needed to free up some space, we have an install of SQL2005 on there so I cleaned up a few old databases, shrunk a massive transaction log etc and was disappointed to find that I hadn't really freed up much space. Then I noticed that D: had a lot more space on it than previously.
Obviously the first thing I did was check that the databases were actually on C: and that I wasn't going mad. In the process of doing this I spotted that there is a "Program Files" folder on both C: and D: Nothing inherently bad about that, sometimes people install onto D: to save space on the primary drive. Then I realised that I can access SQL via either drive but somehow end up at the same actual files. They have matching file sizes, datestamps etc. If I create a file on one drive it's immediately visible on the other. It's as if the files are physically stored on D: but somehow show up in the Program Files path on C: as well.
Anyone seen anything like this before? I'd like to understand what's going on really as this is a new one on me.
) and I used to symlink stuff to my second disk all the time when I was running out of space; saves a re-install 
.