Erin Stellato (@erinstellato) adds another entry to her series on proactive health checks for SQL Server, this time treating database and instance settings.
Today I want to take a minute to talk about gaps. Not the kind where you find trendy clothes for the young (and young at heart) folks, but the kind that you might see in a performance chart on the SQL Sentry Performance Advisor Dashboard.
I've found myself explaining this to a few customers in recent months, and I wanted to get this down somewhere so that others may be able to find it on their own, or if they do ask I have reference material for them.
SQL Sentry Performance Advisor (PA) for Windows is one of our newer product offerings, and I think one that could use a little bit of use-case clarification. I am often asked questions like this: "Why would I need Performance Advisor for Windows when Performance Advisor for SQL Server already shows me Windows metrics?"
There are several possible answers to this question:
For many DBAs and other IT professionals, on-call hours are part of the job. Keeping critical servers and applications running 24/7 requires the ability to respond to problems at any time of day. This usually means that a call or page to the on-call administrator when something does go wrong off-hours. With SQL Sentry's extensive automated alerting and response capabilities, this isn't always necessary. Let's take a look at how it works.