In this article I will be discussing the moving of database files within a SQL Server instance. We'll also work through a typical move scenario, looking at the scripts we should use and the meta data available to help us.
Let's first begin with what we do know.
Under SQL Server 2000, altering database paths was all but limited to the TempDB database. You had to detach the user database and then re-attach it, or you could use backup, then restore. Hmm, messy to say the least.
Under normal operation, once SQL Server has a handle on a database you will not be able to manipulate the files at the OS level. Any attempt to copy the files, etc., will result in the dialog box below.
To address the first point, thankfully in SQL Server 2005 onwards, this is no longer necessary, and in fact
SP_ATTACH_DB has been deprecated and will be removed in a future version of SQL Server. You should now use:
CREATE DATABASE ... FOR ATTACH
To address the second point, in order to release the handle the database engine has on the user database files we merely need to Offline the database. We do not need to stop the SQL Server services.
Let's just re-cap that; we do not need to stop the SQL Server services.
You may issue the following command to Offline the database;
ALTER DATABASE [yourDB] SET OFFLINE
If you have active connections and wish to roll them back and take the database offline you may do so using;
ALTER DATABASE [yourDB] SET OFFLINE WITH ROLLBACK IMMEDIATE
Once the database is Offline you may move and\or rename your database files. Just remember that if you delete or rename the files, the database will not come back online again. When attempting to Online the database you will usually receive an error along the lines of:
You must first amend the system catalogs to provide the new paths\filenames, this is done using the ALTER DATABASE command passing in the MODIFY FILE parameters as shown in the following query construct:
ALTER DATABASE [yourDB] MODIFY FILE ( name=logicalfilename, filename=N'c:\folder1\folder2\adbfile.mdf' )
Important Note: When using the T-SQL command above, SQL Server will accept whatever you type and issue in the ALTER DATABASE statement so be careful and check your typing!
For example this would be valid
ALTER DATABASE [yourDB] MODIFY FILE(name=logicalfilename, filename=N'c:\MSSQL\DATA\gobbeldygook.dat')
If the path\filename does not exist when the database tries to start you will receive an error!!
Moving the Files
With the above in mind, let's look at how we would achieve the goal of moving a databases disk files to new locations.
The server drives are filling up quickly and you have been asked by the manager to move the disk files to a new set of drives provided by the Windows administrator. The engineer has created your new file paths for you and retained all NTFS ACLs required for the SQL Server services. The drives\paths supplied are as follows (I am using my C drive but this could easily be G or F or some other drive letter);
C:\Program Files\Microsoft SQL Server\MSSQL10_50.DBA\MSSQL\Data
Before making any changes to the OS files and their locations first check the metadata available to you in the following system catalog: master.sys.master_files. The important metadata to collect consists of the Logical Filenames and the Physical Names. You may obtain this information using the following query;
SELECT database_id, name, physical_name FROM sys.master_files WHERE database_id = DB_ID('SampleServiceCompany2009')
For my database I have the following:
I need to amend these paths from the "C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Data" directory to match the new location provided to me. The first task is to construct a set of T-SQL move commands. The ALTER DATABASE ... MODIFY FILE command really only needs 2 parameters for the file move: the files logical name and the physical_name. Both of these are retrieved in the query shown above. The move commands are extremely simple and as shown earlier take the following form;
Issuing these commands now will update the system catalogs, however, the new paths will not take effect until the database has been restarted (or taken Offline then brought back Online). The following message informs us of this:
I'll now take the database Offline using the command highlighted below.
With the database Offline, I may now move the files(and even rename them if I really wanted to).
A word of caution here. It is advisable to copy and paste the files to the new locations. Only when the database comes online successfully would I then remove the old files.
Once you have copied the files to the new locations you would then bring the database Online, this is done using:
ALTER DATABASE [yourDB] SET ONLINE
Shown below are the typical screenshots you will see if the database fails to start. From the information dialog below click the message column and you will see details of the issue.
The error details show below provide an indication to the issue, the files probably do not exist (in fact that's generally exactly what an OS Error 2 means).
If the database starts successfully you will see the following
Help, My Database Won't Start
In every scenario I have encountered whereby a database file move has failed, the issue has been down to a mistyped path and\or filename, resulting in the DBA then getting into a vicious loop trying to correct themselves. Should your database fail to start, don't panic. Perform the following tasks;
- Check the script you used to modify the database file locations, have you got the paths and filenames correct?
- Have your admin check the permissions to the new path for the SQL Server Database Engine service account.
- Query the catalog
master.sys.master_files, do the paths\filenames here match what you're expecting?
- If you are unable to complete the move successfully, revert back to the original file paths\names. As you left the files in the source directory simply issue the appropriate ALTER DATABASE ... MODIFY FILE statements and bring the database back online.
master.sys.master_files to obtain the current database file paths
This is a very easy task to complete providing you pay full attention to the task in hand. If you encounter an error, stop and review what you currently have in place both from the system catalog metadata and the physical OS locations\filenames.
As always, enjoy and if you're still stuck post back and I'll help all I can