Scott Fallen - SentryOne Team Blog

Scott Fallen

Scott (@ScottFallen) leads SentryOne’s Solutions Engineering team. He and the rest of the team interact with customers and prospective customers at conferences and trade shows, and provide demos and online webinars to existing and future users of the SentryOne platform. Scott has been teaching the SQL Server community and our customers about our products since 2010. Scott’s blog covers events that the SentryOne team attends and offers tips on using our software. Whether you are an existing customer, evaluating the software, or just curious who we are, be sure to check out his blog to see what is going on at SentryOne.
Back to SQLBits

Back to SQLBits

Scott Fallen (@ScottFallen) invites you to join SentryOne at SQLBits 2017, from the 5th to 8th of April.

SQL Server Alerts : Best Practices

SQL Server Alerts : Best Practices

Strategies and best practices for SQL Server alerts. Alert priorities, avoiding alert fatigue, and having a solid overall strategy are key.

Come and see SQL Sentry at this Spring's SQLintersection Conference

Scott Fallen talks about SQL Sentry's participation in the upcoming SQLintersection conference being held in Orlando, April 17-22.

SQL Sentry and System Center Operations Manager

Scott Fallen (@ScottFallen) explains how SQL Sentry software can co-exist and even integrate with Microsoft System Center Operations Manager.

Alerting on a Call Schedule with SQL Sentry

Sales Engineer Scott Fallen (@ScottFallen) describes how to set up SQL Sentry alerting so that the right people are notified during the right time frames.

As a SQL Server DBA, Why Do I Need Performance Advisor for Windows?

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:

Simplify your on-call hours with SQL Sentry's alerting and response features

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.

Submitting a Better Support Request

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.