The official blog for Windows Server Essentials and Small Business Server support and product group communications.
EPS Team Blogs
[Today's post comes to us courtesy of Rod White]
When trying to free up space, customers frequently have questions about moving WSUS Content and Databases to different partitions. Our objective is to explain three things:
Start by checking the size of the Volumes by looking at the Server Storage. Open SBS Console and select the Backup and Server Storage Tab. Next, select Server Storage to determine the space available on each partition. When highlighting the C: drive you'll see the size of the different components that you may wish to move with the Storage Wizards. Today we will focus on moving the WSUS Components. Under the Storage Task the Move Windows Update Repository Data Wizard only moves the downloaded content. This will not move the WSUS Metadata or SUS database (SUSDB.mdf and SUSDB.ldf).
During the move the wizard will create a WSUS directory on the new location and will begin copying the contents into the <Drive>:\WSUS\WsusContent directory.
Note: We recommend you perform these steps after hours due to significant resource requirements.
I am using both SQL 2005 and 2008 on the server and do not find Start > Programs > Microsoft SQL Server 2005 > SQL Server Management Studio Express. Kindly advise.
After moving my database I try to attach the database and get a message about read only mode.
Now my SUSDB is in read-only. How do I resolve this?
To move the SUSDB you need to bring the following services offline:
•Update Services Notifications
•IIS (including all dependencies like WWW service etc.)
Thanks for the article.
This was of great assistance.
Just like Rajiv K K in 2009, I have both SQL 2005 & 2008 on the server, and there is no 2005 SQL Server Management Studio Express. The 2008 equivalent gives me an error trying to connect to the SQL Server with a network related or instance specific error.
"error 26 - Error locating Server/Instance specified..."
Is there a solution to this that has been documented?
With SQL2012 the connection to SQL has change to...
Worked well, ty