Building your own scripts to monitor SQL Server seems like a very reasonable thing to do. We’re smart folks and SQL Server is what we do for a living—we should be able to figure this out. Upon further inspection, we found it was easier for us to focus on what we do—database administration, and let the developers focus on what they do—build software. This episode explores our choice of SolarWinds SQL Sentry as the monitoring standard for SQL Data Partners.
How does daylight savings time affect disaster recovery? by Paul Randal
SQL Server Agent and Daylight Saving time by Matthew McGiffen
Get your SQL Data Partners Podcast T-shirt!
Support the livestream here
Never Miss An Episode
Subscribe to get podcast notifications by email.
For your crime scene investigation, you have security camera footage. Trying to catch [issues] in the act can be difficult.
Eugene Meidinger
3 Takeaways
- Using a monitoring tool allows us to focus on DBA tasks rather than software development.
- SolarWinds SQL Sentry allows us to connect different data points together easily.
- SQL Server Agent Job Visualization makes choosing a job schedule easy.
Leave a Reply
You must belogged in to post a comment.