Moving your WSUS 3 database

I had need to move the database my Windows Server Update Services is using from the Windows Internal Database to my full SQL Server (2005). Following are my steps: 1. Microsoft Article on the steps required, I used this as a guide, but as I had already installed WSUS, I had to vary things a bit.

2. Enabling Nested Triggers on your SQL 2005 database

How to: Configure the nested triggers Option (SQL Server Management Studio) Use the nested triggers option to control whether an AFTER trigger can cascade; that is, perform an action that initiates another trigger, which initiates another trigger, and so on. When nested triggers is set to 0, AFTER triggers cannot cascade. When nested triggers is set to 1 (the default), AFTER triggers can cascade to as many as 32 levels. INSTEAD OF triggers can be nested regardless of the setting of this option. To set the nested triggers option 1. In Object Explorer, right-click a server, and then select Properties. 2. On the Advanced page, set the Allow Triggers to Fire Others option to True (the default) or False.

3. Manage the Windows Internal Database with SQL Management Studio

SQL Server Embedded Edition is just a specially configured named instance of the SQL Server Express database engine which can be accessed only by certain Windows Services, or by SQL Server Management Studio Express using \.pipemssql$microsoft##sseesqlquery as server name.

4. Detach the WSUS database, copy it across to the new location and attach it to the SQL Server.

5. At this point I pulled a bit from the WSUS 2.0 article here. Specifically about adding the computer account of the front end server to the SQL Server security logins, and

6. Adjust the registy of the front end server to point to the new database location. Close your management console and restart the Update Services service, and IIS. Boom!

Enjoy.