Completely Removing SQL Server 2005 Express

I've recently tried to load SQL Server 2005 Express onto the main server that services our small company of 10 people. The server is a W2K Server, and acts as our domain controller. I've had NUMEROUS problems trying to get SQL Server 2005 Express to work on this system - so much so that I've given up trying. However, in attempting to uninstall this, I've now encountered even bigger issues. It seems that the uninstaller leaves files behind (such as VSS Writer, Set up Files) that then will not uninstall themselves. So, being the novice I am, I tried re-installing SQL Server Express as a whole, removing the above files, then uninstalling SQL Server Express "proper." Well, that didn't work either - I got the subordinate stuff to come off, but now the main files won't remove - nor can I reinstall the whole thing any more.

This is an absolute mess - and I need help getting out of it. Can anyone direct me to help on how to SAFELY remove the ENTIRE instance of SQL Server 2005 Express so that nothing else is interrupted/harmed? Any sound advice at this point is most appreciated.

I ve got the same Problem here. Ive installed the Beta of Visual Studie - even after de-installation it was not possible to install Sql Server Developer edition.
I think it is something wrong in registry...|||Not sure about uninstalling, but I think I saw a blurb somewhere on the books online stating you shouldn't install SQL 2005 on a domain controller...|||

SQLWriter and Support files (amongst other 'leftovers') should uninstall just fine after SQL is gone. They may pop up a message saying that removing them may cause other dependent applications to fail. But if you have already removed all instances of SQL Server 2005, you should be fine.

In the situation where you removed them while SQL Express was already on the box, I would suggest installing Express again (to let the installer put back what you deleted), then uninstalling Express, then uninstalling the leftovers.

If that fails, as a last resort you can use the Windows Installer clean up tool. However this may leave some services behind. I definitely recommend

http://download.microsoft.com/download/E/9/D/E9D80355-7AB4-45B8-80E8-983A48D5E1BD/msicuu2.exe

complete bkup & log size

Hi ,
does a complete backup automatically reduce a log file size by removing
the inactive entries and those already written to the database ?
i have created a completed database backup on a weeklt basis but it still
seem that the log file is quite huge around 11 GB ?
could anyone kindly advise how i can approach this backup issue ?
tks & rdgsBackups do not reduce the size of any files. You must issue regular log
backups in addition to FULL backups if your database recover model is set to
FULL. or Bulk Logged. If you don't wish to do log backups you should change
it to simple mode. To shrink the file once you have fixed the process you
can use DBCC SHRINKFILE.
--
Andrew J. Kelly SQL MVP
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:4BF03439-3AA2-4B9C-9E90-D9C046F88A29@.microsoft.com...
> Hi ,
> does a complete backup automatically reduce a log file size by removing
> the inactive entries and those already written to the database ?
> i have created a completed database backup on a weeklt basis but it still
> seem that the log file is quite huge around 11 GB ?
> could anyone kindly advise how i can approach this backup issue ?
> tks & rdgs