Scott Fallen (@ScottFallen) invites you to join SentryOne at SQLBits 2017, from the 5th to 8th of April.
Strategies and best practices for SQL Server alerts. Alert priorities, avoiding alert fatigue, and having a solid overall strategy are key.
Scott Fallen talks about SQL Sentry's participation in the upcoming SQLintersection conference being held in Orlando, April 17-22.
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.
It's never fun when something goes wrong with a piece of software or hardware we depend on. Often this situation necessitates some form of support engagement with the vendor. Vendor support varies greatly in quality, and I'm lucky to be writing this from the perspective of a member of the technical team at SQL Sentry – a company that has an excellent support team. That being said, my experiences as a support customer of various companies has run the gamut from great to terrible. While the quality of the support team you are working with may vary, I would like to offer some suggestions for making the process better from the customer side.