I am having trouble moving and SQL Server install from
one partition to another.
The current situation:
I have a server with a single disk that is broken into
two partitions. One partition contains the OS (Win2k
Server) and the other contains my application files
including my complete SQL Server install. The second
partition (with SQL Server) is mounted under a directory
(C:\myApplication), it does not have its own drive letter.
This situation works great and it does everything I need
it to do and I have no problems with it.
I set the box up this way because I had hoped that when
the day came (and it has) where I needed more space for
my database, I could simply install an additional disk in
the server, move my database over to it, and then simply
mount that new disk under the same directory name (after
unmounting the partition that is currently under that
Here is what I did:
Installed the new disk.
Mounted a new directory over the new disk
Copied everything from C:\myApplication to
Unmounted both directories.
Mounted the new disk under c:\myApplication.
Everything worked great to this point. However, the
database would not start. It seemingly knew that a
change had occurred and complained about many different
things. After a brief struggle to try and tweak the
registry to make things work, I gave up and reverted to
the original config.
Yes, I could reinstall everything onto the new disk, but
I'm really trying to avoid having to do that as downtime
for this box is an extreme issue.
Is there any way to fool the database into not know that
such a switch has occurred? I had hoped that the virtual
directory would be transparent to the database, but SQL
Server obviously has some lower level interaction with
the disk and was wise to my ploy.