Fri, May 4 2007 12:05
bradley
So what happens to your other MSDE's after the WSUS 3.0 upgrade?
So the other day I blogged a "Got Milk" kind of post....
http://msmvps.com/blogs/bradley/archive/2007/05/02/sbs-2003-r2-wsus-3-0.aspx
...and I don't think I was clear enough about what happens to the other SQL/MSDE instances on a SBS box when you install WSUS 3.0 over the top of WSUS 2.0 which upgrades the WSUS 2.0 database from MSDE to SQL 2005 embedded.
Nothing.
And that's as it should be... because SBS Monitoring needs to stay on msde and your Sharepoint can stay on WMSDE. The only thing that automagically flips up to the SQL 2005 edition of databases is WSUS.... nothing else will get automagically updated.
At the "real baby" at the office I have the following --
FWDB - That's Scorpion Software's firewall dashboard still on msde
ISA 2004 still on msde
SBS Monitoring - still on msde (and it should stay there)
That's Sharepoint on SQL 2005 workgroup (I'm running R2)
and that's the WSUS database on SQL 2005 embedded edition
Bottom line the only thing that's impacted when you upgrade from WSUS 2.0 to WSUS 3.0 is WSUS's database. All the others are running just like they should be.
Filed under: SQL Server
![[There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not.]](http://www.sbslinks.com/images/headertop.png "There's a reason that Yoda is the unofficial mascot of SBS. Size indeed matters not!")