isitdevops.com/databases

To move a system database data or log file as part of a planned relocation or scheduled maintenance operation, follow these steps. This procedure applies to all system databases except the master and Resource databases.

1. For each file to be moved, run the following statement.

   Copy

   ALTER DATABASE database_name MODIFY FILE ( NAME = logical_name , FILENAME = 'new_path\os_file_name' ) 

2. Stop the instance of SQL Server or shut down the system to perform maintenance. For more information, see Start, Stop, Pause, Resume, Restart the Database Engine, SQL Server Agent, or SQL Server Browser Service.

3. Move the file or files to the new location.

4. Restart the instance of SQL Server or the server. For more information, see Start, Stop, Pause, Resume, Restart the Database Engine, SQL Server Agent, or SQL Server Browser Service.

5. Verify the file change by running the following query.

   Copy

   SELECT name, physical_name AS CurrentLocation, state_desc FROM sys.master_files WHERE database_id = DB_ID(N''); 

If the msdb database is moved and the instance of SQL Server is configured for Database Mail, complete these additional steps.

1. Verify that Service Broker is enabled for the msdb database by running the following query.

   Copy

   SELECT is_broker_enabled  FROM sys.databases WHERE name = N'msdb'; 

   For more information about enabling Service Broker, see ALTER DATABASE (Transact-SQL).

2. Verify that Database Mail is working by sending a test mail.

If a file must be moved because of a hardware failure, follow these steps to relocate the file to a new location. This procedure applies to all system databases except the master and Resource databases.

Important
If the database cannot be started, that is it is in suspect mode or in an unrecovered state, only members of the sysadmin fixed role can move the file.

1. Stop the instance of SQL Server if it is started.

2. Start the instance of SQL Server in master-only recovery mode by entering one of the following commands at the command prompt. The parameters specified in these commands are case sensitive. The commands fail when the parameters are not specified as shown.

   • For the default (MSSQLSERVER) instance, run the following command:

     Copy

     NET START MSSQLSERVER /f /T3608 

   • For a named instance, run the following command:

     Copy

     NET START MSSQL$instancename /f /T3608 

   For more information, see Start, Stop, Pause, Resume, Restart the Database Engine, SQL Server Agent, or SQL Server Browser Service.

3. For each file to be moved, use sqlcmd commands or SQL Server Management Studio to run the following statement.

   Copy

   ALTER DATABASE database_name MODIFY FILE( NAME = logical_name , FILENAME = 'new_path\os_file_name' ) 

   For more information about using the sqlcmd utility, see Use the sqlcmd Utility.

4. Exit the sqlcmd utility or SQL Server Management Studio.

5. Stop the instance of SQL Server. For example, run NET STOP MSSQLSERVER.

6. Move the file or files to the new location.

7. Restart the instance of SQL Server. For example, run NET START MSSQLSERVER.

8. Verify the file change by running the following query.

   Copy

   SELECT name, physical_name AS CurrentLocation, state_desc FROM sys.master_files WHERE database_id = DB_ID(N''); 

To move the master database, follow these steps.

1. From the Start menu, point to All Programs, point to Microsoft SQL Server, point to Configuration Tools, and then click SQL Server Configuration Manager.

2. In the SQL Server Services node, right-click the instance of SQL Server (for example, SQL Server (MSSQLSERVER)) and choose Properties.

3. In the SQL Server (instance_name) Properties dialog box, click the Startup Parameters tab.

4. In the Existing parameters box, select the –d parameter to move the master data file. Click Update to save the change.

   In the Specify a startup parameter box, change the parameter to the new path of the master database.

5. In the Existing parameters box, select the –l parameter to move the master log file. Click Update to save the change.

   In the Specify a startup parameter box, change the parameter to the new path of the master database.

   The parameter value for the data file must follow the -d parameter and the value for the log file must follow the -l parameter. The following example shows the parameter values for the default location of the master data file.

   -dC:\Program Files\Microsoft SQL Server\MSSQL.MSSQLSERVER\MSSQL\DATA\master.mdf

   -lC:\Program Files\Microsoft SQL Server\MSSQL.MSSQLSERVER\MSSQL\DATA\mastlog.ldf

   If the planned relocation for the master data file is E:\SQLData, the parameter values would be changed as follows:

   -dE:\SQLData\master.mdf

   -lE:\SQLData\mastlog.ldf

6. Stop the instance of SQL Server by right-clicking the instance name and choosing Stop.

7. Move the master.mdf and mastlog.ldf files to the new location.

8. Restart the instance of SQL Server.

9. Verify the file change for the master database by running the following query.

   Copy

   SELECT name, physical_name AS CurrentLocation, state_desc FROM sys.master_files WHERE database_id = DB_ID('master'); GO 

The location of the Resource database is drive>:\Program Files\Microsoft SQL Server\MSSQL.instance_name>\MSSQL\Binn\. The database cannot be moved.

If you have moved all of the system databases to a new drive or volume or to another server with a different drive letter, make the following updates.

• Change the SQL Server Agent log path. If you do not update this path, SQL Server Agent will fail to start.

• Change the database default location. Creating a new database may fail if the drive letter and path specified as the default location do not exist.