Use the following steps to migrate the WSUS database from a Windows Internal Database instance to an instance of SQL Server 2005.

1. Install SQL Server 2005 with the Server and Client Tools option and SQL Server 2005 Service Pack 1 or a later version on your WSUS server.
   
   
2. Click Start, point to Programs, point to Administrative Tools, and then click Services.
   
   
3. Right-click IIS Admin Service, and then click Stop.
   
   
4. Right-click Update Services, and then click Stop.
   
   
5. Run the following SQL command to detach the WSUS database (SUSDB) from the Windows Internal Database instance, by using the sqlcmd utility. This utility can be downloaded from Feature Pack for Microsoft SQL Server 2005 (http://go.microsoft.com/fwlink/?LinkId=70728). For more information about the sqlcmd utility, see sqlcmd Utility (http://go.microsoft.com/fwlink/?LinkId=81183).
   
   
   sqlcmd -S np:\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
   use master
   alter database SUSDB set single_user with rollback immediate
   go
   sp_detach_db SUSDB
   go

6. In SQL Server Management Studio, under the instance node, right-click Databases, select Properties, and then click Attach.
   
   
7. In the Attach Databases box, under Databases to attach, locate the susdb.mdf file (by default, this is C:\WSUS\UpdateServicesDbFiles if you installed Windows Internal Database), and then click OK.
   
   
8. In this step, you will verify that NT AUTHORITY\NETWORK SERVICE has login permissions to the instance of SQL Server and to the WSUS database. If it does not, you will have to add it to both locations. This account should also be a member of the webService role on the WSUS database.
   
   
   • To verify permissions on the instance of SQL Server, in SQL Server Management Studio, open the instance and select Security, and then Logins. The NT AUTHORITY\NETWORK SERVICE account should be listed as a login. If it is not, it should be added.
     
     
   • To verify permissions on the database, right-click the database, select Properties and then click Permissions. The NT AUTHORITY\NETWORK SERVICE account should be listed as a login. If it is not, it should be added.
     
     
   • To verify members of the webService role, under the WSUS database, select Roles, right-click webService, and then select Properties. The NT AUTHORITY\NETWORK SERVICE account should be listed as a member of this role. If it is not, it should be added.
     
     
9. In this step, you will edit the registry to both point WSUS to the instance of SQL server that now holds the WSUS database and recognize the new database for future WSUS updates. If you have not already done this, export the keys in the registry that you plan to edit, or back up the whole registry.
   
   
   1. Click Start, click Run, type regedit, and then click OK.
      
      
   2. Find the following key: HKLM\SOFTWARE\Microsoft\UpdateServices\Server\Setup\SqlServerName, and in the Value box, type [ServerName]\[InstanceName], and then click OK. If the instance name is the default instance, type [ServerName].
      
      
   3. Find the following key: HKLM\Software\Microsoft\Update Services\Server\Setup\wYukonInstalled. In the Value box, type 0, and then click OK.
      
      
10. Click Start, point to Programs, point to Administrative Tools, and then click Services.
    
    
11. Right-click IIS Admin Service, and then click Start.
    
    
12. Right-click Update Services, and then click Start.
    
    
13. Verify that the database migration was successful by opening the WSUS administrative console. (Click Start, click Administrative Tools, and then click Microsoft Windows Server Update Services 3.0.)
    
    

Note
You might have to restart the server for these settings to take effect.

The goal of this scenario is to take the WSUS database running in a Windows Internal Database instance on the WSUS server and move and upgrade it to an instance of SQL Server 2005 that is running on a remote server. Only a full SQL Server 2005 database may be used in a remote SQL installation. Each step, where appropriate, indicates the server on which you perform the procedure.

Remote SQL scenario limitations

Prerequisites