Edward Whalen

I recently was called on to set up SQL Server monitoring in my OEM system in my lab.  The OEM server is Oracle Linux 7 and my SQL Server platform is Windows 2016.  It turns out that with only a few bumps, Configuring SQL Server Monitoring in OEM 13c is possible. 

The first part was to install the OEM 13c agent on Windows from a Linux server.  This was covered in my previous blog. https://www.perftuning.com/blog/install-an-oem-windows-agent-from-a-linux-oem-platform/

The second phase is to configure SQL Server monitoring in OEM 13c.

This involves two parts:

1.) Configure SQL Server for OEM access

2.) Configure OEM to monitor SQL Server 

Because of what is involved in these parts I’ll split it up into two blog entries.

Part 1:  Setting up SQL Server for OEM access

There are a few things that must be done in order to setup SQL Server monitoring in OEM.  The first is to make sure that the database is set up for TCP/IP access.  By default (at least in my installations) it was not. 

From the start menu choose the SQL Server Connection Manager from your SQL Server installation and select SQL Server Network Configuration.  If TCP/IP does not show Enabled, right click on it and select Enable.  My completed setting is shown here.

Next, create a SQL Server user (if you don’t already have one) that will be used to monitor the SQL Server database.  This can either be a SQL Server authenticated user or a Windows user.

This user must be granted sysadmin in order to be able to monitor all of SQL Server. 

If you are setting up a SQL Server authenticated user, you must change the SQL Server instance property in order to allow mixed-mode authentication.

This is really all that is needed in order to be prepared for OEM monitoring.

Part 2:  Configure OEM monitoring of SQL Server

The next part of this blog will describe how to configure OEM for SQL Server monitoring.