Moving WSUS 3.0 database and content

If ever you wish to move this sizable chunks of data to a different partition, you can do it.  Each data type has its own method for moving.

The WSUS content is moved via the wsusutil command-line utility.  This is something I briefly covered yesterday …or was that this morning?  The days and nights are running together – ughh its only Monday! :O

The database, SUSDB, is a bit more involved being that it runs on SQL or the Windows Internal Database (the default SBS 2003 R2 location).  The general steps are to detach the database from its instance (default is MICROSOFT##SSEE), move the actual files – SUSDB.mdf & SUSDB_log.ldf, and then re-attach these files from their new placement.

Those steps each involve a lot of special knowledge.  Just gaining access to the database can be a challenge and may require using the named pipe path that I’ve blogged on before.  Once there you cannot merely detach the database as it will be in use.  To end these usage tentacles you need to fully stop the W3SVC & WsusService services – World Wide Web Publishing Service & Update Services respectively.  When stopped you should be able to gain the green light from SQL Server Management Studio Express to detach the database.  Once done then you move the files via your method of choice such as xcopy …etc or a simple cut and paste.  After moved, you again use the SSMSE tool to attach the database files.


That’s it.

References – different and not the exact same techniques but worthy of noting:

**tip**  Use the search tool of this blog to find related topics previously blogged.


2 responses to “Moving WSUS 3.0 database and content

  1. Thanks for the very Usefull article! To connect to the Db one needs to use the following instead of the default that the SQL Management tool fills in:

    If you do not one gets the following error message. I think adding this would make life easier for alot of people reading this post.

    Cannot connect to DENEWSUS01\MICROSOFT##SSEE.

    An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)

    Kind Regards.

    • I’ve actually covered the named pipe pathing elsewhere in this blog but it is a very good idea to refer to it again here. There is also a UAC element to running the SQL UI “As Admin” which is needed in Win2k8+ OS’s. Glad this was of help to you.

      Thanks for contributing.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s