If you don't know if the SQL DB is doing anything important, I highly suggest you stop the service first and see what breaks. Don't just remove it.
You can also open SQL Studio Manager and look at what DB/instances are running on the server to help determine what its doing. SQL 2005 is the last CD in the install separate from a fully operations SBS Server setup. On the same CD is ISA 2004 and SQL 2005. -----Original Message----- From: Jim Majorowicz [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 16, 2008 1:56 PM To: NT System Admin Issues Subject: RE: SQL 2005 AdventureWorks Is this an R2 server? Did you reciently upgrade to WSUS 3.0 SP1? -----Original Message----- From: Anthony [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 16, 2008 10:44 AM To: NT System Admin Issues Subject: SQL 2005 AdventureWorks I'm trying to cleanup an SBS Premium 2003 SP1 Server. I noticed that I have SQL 2005 Workgroup that appears to be only serving up the database AdventureWorks_Data.mdf. I don't see any other databases other than the stock system databases (master, tempdb, etc). I think AdventureWorks is a Microsoft sample database. All of my other instances of SQL on this server (Sharepoint, Wsus, Msfw) appear to be using the SQL 2000 MSDE. I don't recall installing the SQL 2005 Workgroup version but the time and date match when I setup this server. Any idea why it's there (did it piggy back with some other system component?) and if it is safe to remove? Anthony ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
