No More SQL Run As Account?

A good friend of mine, Ralph Kyttle, who works at Microsoft as an MCS Consultant in the DC area, recently pinged me about a new configuration he was testing which circumvented the use of a traditional SQL Run As Account.  Rather than configuring the traditional SQL Run As Account (we all know how much fun that is), the Health Service was configured to use a Service Security Identifier (SID) which allows the SCOM agent to monitor SQL server without all of the tedious permission configuration.  To add even more value, Kevin Holman published a great blog post yesterday highlighting the details of this configuration and added a really cool monitor and tasks to help ensure that this configuration is functioning properly. Very cool stuff!

Have a look at Kevin’s blog post here for more details.



SQL MP Version Removed Due To Transaction Log And Visualization Issues

UPDATE: (12/14/2015): Version has now been released and is the current version.

UPDATE (11/12/2015): Version which includes a fix for the issue mentioned below has been released. Please see Released: System Center Management Pack for SQL Server and Replication ( for more information.

Microsoft has posted a mitigation as a workaround to resolve issues caused by importing the new SQL management pack (version   As stated in the SQL Release Services blog, the management pack has been removed for download and will be re-released once the issue is resolved.

New SQL Dashboards – BIG changes in SQL dashboards in the new SQL MP

The new SQL Management Pack has been released, and by far the biggest change that I have noticed is visualization aspects.  The OOB Database Instance and Database dashboards are GONE.  These dashboards have been replaced by a SQL Server x Summary Dashboard and the Datacenter Dashboard and Instance View Dashboards, both of which I will detail below.

You can download the new management pack here.

Continue reading

SCOM – Use SQL Server Profiler to capture SQL queries used by the SCOM console

There have been many scenarios where a customer has asked what query is being used in a report, dashboard, view, etc. in the SCOM console.  This information can be useful for many reasons, but in particular, I find that I often utilize it for reverse engineering reports and queries and for troubleshooting.  There is a fairly simple way to obtain this information using SQL Server Profiler traces…

Continue reading