Friday, September 11, 2015

Installing SQL 2008 R2 for System Center 2012 Operations Manager



In the first part of the series, we installed the software prerequisites for System Center 2012 Operations Manager. This is a three part series about installation of SCOM 2012 on Windows 2008 R2 sp1 server. We recommend you to read the first part before you go through this article.

SCOM 2012 supports all kind of SQL version that supports 64 bit architecture. Here is a list of SQL server supported by SCOM 2012 operations database.

  1. SQL Server 2008 SP1
  2. SQL Server 2008 SP2
  3. SQL Server 2008 SP3
  4. SQL Server 2008 R2
  5. SQL Server 2008 R2 SP1
  6. SQL Server 2008 R2 SP2
  7. SQL Server 2012 or SQL Server 2012 SP1.
For purpose this second part of the article, we are installing SQL 2008 R2 on Windows 2008 R2 Sp1 server.
Once you run the setup for SQL 2008 R2 the SQL Installation Center will open up with lot of options. But click Installation on the left and select New Installation or add features to an existing installation.

SQL Installation Center

The Setup Support Rules will find initial problems related to installation and report it.

Setup Support Rules

You can view detailed report of setup support rules. Problems must be corrected before we proceed with the installation.
Then click on OK.

Select SQL Edition

Next we need to enter product key to install, if you do not have a product key then specify a free edition which a Evaluation.

SQL License Agreement

Then select I accept the license terms and click next. In the next screen, click Install.

Under Setup Support File > Click Install

Once again we have a report from setup support rules in which all rules have passed except the .Net Application Security. Click on the warning to check the warning message.

Setup support rules with list of rules that have passes or not passed

.Net Application Security warning details

The warning is about access to
http://crl.microsoft.com/pki/crl/products/MicrosoftRootAuthority.crl. When we tested the url on browser, it was found working and prompted with a download shown in the screenshot below.

MicrosoftRootAuthority.crl file

MicrosoftRootAuthority.crl is accessible and available for download. But downloading is not necessary. So safely ignore the warning in setup support rules and click next.

Choose a setup role to install

We need to decide what components or SQL features to install under Setup Role page. There are three choices.

  1. SQL Server Feature Installation
  2. SQL Server Power Pivot for Sharepoint.
  3. All Features with Defaults
The SQL Server Feature Installation allows you to select feature that you want to install. You can choose to install Database Engine Services, Analysis Services, Reporting Services, Integration Services and other features.

The second option, SQL Server Power Pivot for SharePoint requires SharePoint server for Power Pivot data.
The third option, will install all the features available for this installation. Select All Features with Defaults.

Unselect the options you do not want

The all features default also allows you to remove some of the feature that you do not want, otherwise click next to complete the installation.

Installation Rules

The setup runs Installation Rules to determine if there is any issue. All the issues must be fixed before continuing installation. If you want to see the default reports then click the link View detailed report.

Instance Configuration

We have to configure the instance or select the Default instance. The default instance is called MSSQLSERVER. Click next to continue with the installation.

Disk summary page

The next page is Disk Space Requirements which shows a summary of available disk space and allotted disk space, Click next to continue.

Configure Service Accounts

In the server configuration page, we define the service accounts to be used for different sql services. You must specify the account for services which are not defined. Select different accounts for different services and no need to enter the password.
Click next to continue with the installation.

Database Engine Configuration

Configure the database engine configuration and to select the account for Windows Authentication mode, click Add Current user. Then click next.

Analysis Service Configuration

Configure Analysis Service Configuration and click Add Current User to specify administrator account. This account will have unrestricted access to analysis service.

Reporting Service Configuration

For reporting service configuration, click install the native mode default configuration. This option will make sure that reporting services is ready as soon as we finish the setup.

Skip the Error Reporting screen, if you want to report errors to Microsoft select this error reporting otherwise click next.

View detailed reports of installation rules

The installation configuration rules will check for possible problems and we must resolve any issues that might block the SQL setup.

Now we are ready to install SQL

Finally we are ready to complete the installation, view the summary for configuration and click INSTALL to start the installation.

Installation Completed successfully

The installation will take several minutes depending on features selected and system resources. Click Close to finish the installation.


In the second part of this series, installing System Center 2012 Operations Manager. we have selected and installed SQL 2008 R2 with all required features. Microsoft recommends enough system resouces for SQL server for better performance. SCOM 2012 configuration and reports are stored in SQL databases. So we must ensure effortless communication with SQL server.

No comments:

Post a Comment