How to remove an Instance on a SQL Server

Sometimes it's needed to remove an Instance on a SQL Server, because of database migration or SQL Server cleanup. When doing this in a production environment, this is a exciting action. This because of other production databases, which may be running in a different Instance. I've done this a few months ago, and it all went fine.

Just read the guides on Microsoft TechNet first before doing this:

-To uninstall an instance of SQL Server 2008 http://technet.microsoft.com/en-us/library/ms143412(v=sql.100).aspx

-To uninstall an instance of SQL Server 2008 R2 http://technet.microsoft.com/en-us/library/ms143412(v=sql.105).aspx

-To uninstall an instance of SQL Server 2012 http://technet.microsoft.com/en-us/library/ms143412(v=sql.110).aspx

Here are the steps which are needed to remove the Instance. Just make sure which one must be removed and there are no databases on it.

-Open Control Panel, Programs and Features
-Select "Micosoft SQL Server {version}"
-Choose "Uninstall/Change"
-Choose "Remove"
-Setup Support Rules > Next
-Remove SQL Server {version}
-Select Instance > Choose "SQL Instance"
-Select Features > Choose "Specific features" (not shared features)
-Removal Rules > Next
-Ready to Remove > Next
-Removal Progress
-Complete

After following this steps the selected Instance is removed. There's no reboot needed on the SQL Server, and other databases will still have connection. Just make sure reading the guides, and you are fine!

How to install OpsMgr 2007 R2 on SQL Server 2008 R2

Last week I installed System Center Operations Manager (OpsMgr) 2007 R2 on SQL Server 2008 R2. This is supported by Microsoft, but the OpsMgr wizard does not recognize a SQL Server 2008 R2 installation. Therefore a specific installation order is needed to have it all functional. All steps needed will be explained in this blogpost. Just follow them for having a correct installation.

I won't describe the SQL 2008 R2 installation here, so make sure it's ready before installation. First choose "Check Prerequisites" on the OpsMgr server. The following Roles and Role Services must be added:

• Application Server
• Web Server (IIS)
• Common HTTP Features (Static Content, Default Document, Directory Browsing, HTTP Errors)
• Application Development (ASP.NET, .NET Extensibility, ISAPI Extensions, ISAPI Filters)
• Health and Diagnostics (HTTP Logging, Request Monitor)
• Security (Windows Authentication, Request Filtering)
• Performance (Static Content Compression)
• Management Tools (IIS Management Console, IIS 6 Metabase Compatibility, IIS 6 WMI Compatibility)

The "Microsoft ASP.NET 2.0 AJAX Extensions 1.0" is needed here also. When Prerequisites looks fine the installation can be continued. There are 2 service accounts needed for OpsMgr functionality (Administrator and Action account).

Normally the installation starts with "Install Operations Manager 2007 R2" for installing the databases. This because the specific order which must be followed during installation:

1. OperationsManager database component (SQL Server)
2. OperationsManager Data Warehouse component (SQL Server)
3. OperationsManager Management Server and console components (OpsMgr Server)
4. OperationsManager Reporting component (SQL Server)

Now another utility is used for creating the database and Data Warehouse components. It's called DBCreateWizard.exe which is found in the <OpsMgr source>\SupportTools\AMD64 folder. Use it twice for creating both databases and decide the name and size in it.

Then Operations Manager can be installed on the OpsMgr server with the default GUI. Just start with "Install Operations Manager 2007 R2" again and select all components except "Database". Follow all necessary steps during setup for a complete installation. There is the possibility to install it on another location or drive here.

Again a different approach is needed now. Before the Reporting component can be installed a workaround is needed. Otherwise it won't be functional. Have a look at local groups on the SQL Server and rename “SQLServerReportServerUser$<OpsMgr Server>$MSRS10_50.MSSQLSERVER” to “SQLServerReportServerUser$<OpsMgr Server>$MSRS10.MSSQLSERVER”.

This is described here: http://support.microsoft.com/kb/2425714

 

Now the Reporting component can be installed with the default GUI. Just start with "Install Operations Manager 2007 R2 Reporting" and select the "Reporting Server" component only. No Data Warehouse installation is needed on SQL Server 2008 R2. Follow all necessary steps during setup for the installation. Again there is the possibility to install it on another location or drive.

All components are installed now, but the local group must be changed again. Rename the local group to “SQLServerReportServerUser$<OpsMgr Server>$MSRS10_50.MSSQLSERVER” back again. After that Operations Manager is installed and usable. The Reporting component is even functional then.

To install latest hotfixes CU3 is needed. It can be download here: http://www.microsoft.com/download/en/details.aspx?id=17893

All steps needed for a functional installation are explained now. Hope you like it and use these steps for instaling OpsMgr 2007 R2 yourself!