In my VM lab at home I have a SQL Server 2005 system that is also running System Center Configuration Manager. This SQL Server is also hosting the WSUS susdb database. Unfortunately I have recently discovered that the SQL Server is getting hammered hard enough that it’s causing timeouts with disk reads/writes to the point that the underlying Server 2003 R2 OS thinks that the disk is going bad (which it’s not…the OS just thinks that). I’ve decided to migrate the WSUS susdb database from the SQL Server 2005 to the WSUS server itself.

The first problem I had was figuring out where I could find a copy of the Windows Internal Database (WID) or as it is sometimes called – SQL Server Embedded Edition. Well the problem here is that you can’t get it as a standalone product (just like you can’t get SQL Server Management Studio as a standalone product). It either comes with the OS (Server 2008 ) or with another product like WSUS 3.0. So, I have a few choices — either uninstall and then re-install WSUS 3.0 or move the susdb database from the SQL Server 2005 on the SCCM VM to a SQL Server 2005 database running on the WSUS VM or move the susdb database from the SQL Server 2005 on the SCCM VM to a SQL Server 2005 Express Edition running on the WSUS VM.

Given that I don’t really see the need for two full versions of SQL Server 2005 in my VM lab I have opted for option #3 — migrate susdb to a SQL Server 2005 Express Edition database on the WSUS VM. (BTW — asked around and no, this is not a supported configuration). But, since it apparently hasn’t been done before I figure — “why the hell not?

Now, it can be done…however there are limitations due to the SQL Server 2005 Express Edition software. My VM lab is only about 20 images. That’s one of the problems — SQL Server 2005 EE is limited in database size. But, given the small size of my VM lab this should not be a problem for me. As I get this project done I’ll post more updates.

Advertisements