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.
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.