By default, WSUS 3.0 on SBS 2003 R2 server uses Windows Internal Database.
If WSUS 3.0 uses other versions of SQL server, the moving steps will be a little different, but the procedures are almost same. They are:
1. Detach SUSDB from SQL Server.
2. Move SUSDB.mdf and SUSDB_Log.ldf to the new location.
3. Attach SUSDB to SQL Server again.
If WSUS 3.0 is using Windows Internal Database, please follow these steps to move SUSDB:
1. Open a "CMD" command window, and run these commands to stop the WSUS service and IIS:
net stop wsusservice
2. Detach the SUSDB.
a. Follow the instructions to download and install "Microsoft SQL Server Management Studio Express" on the WSUS server:
(Please note: we need to install MSXML6 and .Net Framework 2.0 first. If this tool already exists, please ignore this step.)
b. Click "Start"->"All Programs"->"Microsoft SQL Server 2005"->"SQL Server Management Studio" to run this tool.
c. Select the SQL server/instance used by WSUS, and then click Connect. For WSUS 3.0 with Windows Internal Database, please copy/paste this name:
(If this name is unreachable, please WSUS may not use Windows Internal Database, please verify this registry value to confirm the SQL name:
HKEY_LOCAL_MACHINE\Software\Microsoft\Update Services\Server\Setup\SqlServerName.%computername%\MICROSOFT##SSEE means Windows Internal Database.)
d. Expand the "Databases" node from the left pane; Right click the "SUSDB", then click "Tasks"->"Detach" and "OK".
If it fails, please select the "Drop Connections" checkbox and try again.
3. Move the SUSDB.mdf and SUSDB_Log.ldf to a new location by Windows Explorer. By default, they are in the "<Driver>:\WSUS\UpdateServicesDbFiles" folder.
4. Attach the SUSDB database from the new location.
a. Switch back to the Management Studio and right click the "Databases" node, and then click "Attach".
b. Click "Add" button; Navigate to the new location, and then select the SUSDB.mdf and click "OK".
5. Start the WSUS and IIS services with these commands:
net start wsusservice