Microsoft SCOM SQL server monitoring are of different types. Let’s explore each of them one by one. At Bobcares, with our Microsoft SQL Server Support Service, we can handle your SCOM issues.

SCOM SQL Server Monitoring | Configuration Details

System Center Operations Manager(SCOM) is a cross-platform data center monitoring tool for OS and hypervisors. The following monitoring modes are provided by Management Pack for SQL Server:

Agent monitoring: In this monitoring mode, all managed systems that use the System Center Operations Manager agent service have stand-alone and clustered instances of SQL Server automatically found by the management pack. TCP/IP, Named Pipes, and Shared Memory are the protocols supported by this monitoring. The SCOM agent monitors agents and only supports SQL on Windows.

Agentless monitoring: Workflows for the management pack are run on management servers and gateway servers during this monitoring mode. The SQL Server Monitoring Pool is mapped to both servers. All Management Servers Pool is used in the absence of a defined SQL Server Monitoring Pool. SQL on Windows and SQL on Linux are both supported by this monitoring mode. TCP/IP and Named Pipes are supported in this mode.

Mixed monitoring: The management pack plants its seed on every PC that has the System Center Operations Manager agent in this monitoring mode. Then, using this seed, all instances of SQL Server running on Windows are automatically found. Management Servers and Gateway Servers that are a part of the SQL Server Monitoring Pool handle all of the monitoring. This mode only supports SQL on Windows. The protocol supported in this mode is TCP/IP.

Configuring Different SCOM SQL Server Monitoring Modes

Agentless Monitoring Mode

1. Firstly, got to Authoring | Management Pack Templates in the Operations Manager console.
2. Then right-click Microsoft SQL Server, and select Add Monitoring Wizard.
3. Select Microsoft SQL Server from Monitoring Type menu and click Next.
4. Now enter a new name and description for General Properties menu.
5. Choose the management pack that we wish to use to store the template from the drop-down list labelled Select destination management pack. Click New to create a new management pack.
6. Also, click Add Instances to add instances that we want to monitor under Service Details menu.
   • Choose the preferred authentication method from the options of Windows AD credentials or SQL credentials.
   • Choose a regular Run As Account created in Operations Manager with the proper credentials, or select New to create a new one.
   • Provide the connection strings and/or data sources.
7. Now click OK and wait for the connection to establish. Sometimes an error message “An error occurred discovery: A connection was successfully established with the server, but then an error occurred during the login process” may appear. To fix this, reduce the intervals for both Discover All Management Servers Pool Watcher Discovery and MSSQL: Generic Monitoring Pool Watcher Discovery to force them to execute immediately, then restore the prior setting.
8. In order to view properties after connection is established, select an instance and click Edit Instance.
9. Then select the Skip Test Connection and enter this data manually checkbox to skip connection testing and enter data manually.
10. Finally, click Create after reviewing summary details under Summary menu.

Mixed Monitoring Mode

1. Firstly, select Object Discoveries under Authoring | Management Pack Objects in the Operations Manager console.
2. Then right-click MSSQL: Discover Local SQL Database Engines on Windows and select Overrides > Override the Object Discovery > For all objects of class: MSSQL on Windows: Local Discovery Seed.
3. Also, select the Mixed Monitoring in the Override Properties window and enable it.
4. Finally, indicate the instances for which agentless monitoring is desired in the Override Value box. We can use commas to separate the instances. To add all instances, including instances with the same name and instances that are located on different servers, use asterisk (‘*’).

Viewing Monitoring Mode

We can customize views and configure auxiliary columns that show used monitoring types. Perform the below steps:

1. Firstly, right-click the Database Engines view. Then choose Personalize View.
2. Secondly, n the Columns to display list, select the Monitoring Type checkbox.
3. Lastly, enable the Monitoring Type checkbox so that the monitoring types become available in the Database Engines table.

[Looking for a solution to another query? We are just a click away.]

Conclusion

To conclude, our Support team went over the SCOM SQL server monitoring details, along with its configuration steps.