Data Management

Configure a remote database for System Center Operations Manager 2007 R2

As with any enterprise application, requirements can exist to keep database installations on centralized servers that provide shared SQL Server installations. Learn how to set System Center Operations Manager 2007 R2 to use a remote database server.

In my previous tip on automating the prerequisite component configuration for a new Microsoft System Center Operations Manager (SCOM) 2007 R2 installation, the database portions were not mentioned, as that intended configuration would use a remote database server. There are a lot of benefits to using a remote SQL Server — primarily, separation of duties and, in many cases, licensing can be kept under control that way.

For SCOM 2007, the database roles can be on a central database server, with the core SCOM roles being performed on a separate server. SCOM 2007 requires SQL Server 2008 SP1 or higher, as well as reporting services to be installed and configured. Like the standard application server, the database components requirements check tool can be run on the database server, and the local server name is resolved in the SQL Server Name field of the tool. Figure A shows a database server (DB1) running the prerequisite checker for SCOM. Figure A

Click the image to enlarge.

Once the prerequisites have passed, on the application server (FA2) the SQL Server name is specified during the SCOM installation. Unfortunately, the remote SQL connection for SCOM is not a standard ODBC call, so the interactive installation requires some information during the installation process.

The database needs to be built on the SQL Server with the SCOM installation tool. The default SQL database name is "OperationsManager." I will tweak it a bit and change the name to "fa2_scom," so the database name is self-documenting in regards to the server that will be using the database. The installation and this tweak are shown in Figure B. Figure B

Click the image to enlarge.
Once this is complete, on the SCOM application server, we can start the install and select all components except the database for local installation. We will then specify the DB server that was just used (DB1) for the remote database. These steps, performed on the SCOM application server (FA2), are shown in Figure C. Figure C

Click the image to enlarge.

Once a few other questions about authentication and service accounts are answered, the SCOM installation will proceed and utilize the newly created database on the remote server.

Have you employed tricks for the SCOM database residing remotely? If so, share your tricks below.


Rick Vanover is a software strategy specialist for Veeam Software, based in Columbus, Ohio. Rick has years of IT experience and focuses on virtualization, Windows-based server administration, and system hardware.

Editor's Picks