Nevertheless, in this article I’ll try to offer a straightforward explanation of why, in my experience, you’ll get a better return-on-investment by supplementing SCOM with a specialist database monitoring tool. As a pre-sales engineer at Redgate, I must confess up front to a natural bias towards this latter option. The obvious alternative to extending SCOM with the SQL Management Packs is to buy a dedicated SQL Server monitoring tool.
Many of them encounter problems with configuring the SQL Server Monitoring, alert management, and with the incompleteness of the SQL monitoring data. I have first-hand experience with SCOM, and I have spoken to many businesses who have gone down the route of extending SCOM to monitor their SQL Servers. However, it’s not as simple as it sounds. SCOM will discover and start monitoring all your SQL Server instances and databases, and raising alerts on any errors, abnormal conditions, and so on.Įxtending SCOM to monitor SQL Server is an obvious option for any IT Manager who has existing System Center licenses, and system administrators who already use it to monitor other parts of their infrastructure.
Server hardware monitor install#
Likewise, if you need to start monitoring SQL Server, you can install and configure the relevant SQL Management Packs. If you need to start monitoring VMWare, you install and configure the relevant VMWare management packs. Via its array of Management Packs, you can extend SCOM to monitor a range of different systems. It is a useful a system-wide monitor of the availability, performance and security of their server hardware, system services, operating systems, hypervisors and applications.
Many sysadmin teams will use a tool like System Center Operations Manager (SCOM).
0 kommentar(er)
