Melissa Connors (MelikaNoKaOi) walks through some key features of the event log management tools in SentryOne for Windows Event Logs as well as SQL Server.
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.
When it comes to SQL Sentry, we love for you to upgrade for your benefit and ours, and we really work hard to make it easy to do so. So here are some great reasons to upgrade your SQL Sentry environment to the most recent release just as soon as you are able to.
Since its introduction in SQL Server 2005 SP1, mirroring has become a common method to provide high availability for critical databases. With any HA strategy, proper monitoring is a must to ensure everything is working as planned with minimal data loss and disruption incurred in the event of a failover.
SQL Server has built-in methods to monitor database mirroring, but there are several limitations and known issues. I'll show you how to use SQL Sentry's software to work around those and gain much more insight and visibility into your database mirroring performance.