Historically, if I go to rename a database that is currently being used by SQL Server, I get an exception.
On this Windows 8 desktop I'm in.. my primary desktop.. I'm able to MOVE SQL Server database files to a different partition.. without getting any errors.. even if the files are currently 'in use'. I don't understand WHY I can do this, I want to get an error when I go to move a file and it should be listed as being attached in SQL Server
I am also able to rename a file that is currently in use. The punchline is that I was talking to my network admin today, and he actually attempts to rename a
.MDF file, in order to determine if this file is in use.
I don't like this. What I really want to be able to do is to MOVE files (using a DOS command) from one disk partition to another, but if they're currently attached to the default SQL Server instance, then don't try to move the file.
I was counting on this to work as advertised. I shouldn't be able to rename or move a file that is currently being used as an attached database in SQL Server.
Also, I'm sorry.. but I do have an non-standard hard-drive config.
Disk 0 System Reserved 350mb D: SSD Disk 1 C: (Primary volume, Windows 8 Enterprise, etc)
I'm specifically using this SSD solely for SQL Server Express on this machine, I have a half dozen attached databases at any one time and I'm actually working towards creating a MILLION detached databases (and occassionally re-attaching some of them casually when I need them).