Instead of entering a new part to my ongoing series of understanding and utilizing Microsoft’s System Center Suite for SQL Server DBAs, I want to take a break here in the series and catch up on 2 things:
I just finished setting-up a new prototype environment for a customer today and there are 2 really neat areas in Operations Manager that I did not highlight on my earlier posting on SCOM with the SQL Server Management Pack:
One of the nice ways that SCOM takes the perfmon and SQL counters and wraps those up is the Health Explorer (see screenshot) below. Notice the way that it rolls-up aggregated counters up to the top-level objects and targets within your SQL Server environment. When managing large SQL Server footprints, this can be very, very helpful:
You can also integrate SSRS reports by importing RDL into the SCOM reporting capabilities. What I am working on now is taking the SQL Server Management Data Warehouse reports and making those available right from SCOM so that I won’t need to jump into SSMS first to interrogate the offending queries and execution plans that are causing database performance issues.
I want to also call-out System Center Audit Collection Services (ACS), which I called out in my description of an end-to-end auditing solution in SQL Server 2008 R2 using the Security Audit tools here. With ACS, you get the same benefit that SCOM provides in that you can audit not only your SQL Server activity, but also the rest of your Windows environment (and non-Windows, too), meaning that you’ll capture all server activity. ACS integrates with the SQL Server Audit capability through Event or Windows logs and extends the SQL Server built-in capabilities far beyond what SQL Server provides out of the box: