Monitoring [in IT] sucks and I am probably more critical of its state than most IT people. Over the next few posts I’m going to integrate a sample application with several logging and data services, evaluating them against my own needs and expectations. Besides the comparison, and perhaps more importantly, the examples will show how easy it is to instrument our applications and start getting visibility into what is actually happening behind the scenes.
Less Than Dot is a community of passionate IT professionals and enthusiasts dedicated to sharing technical knowledge, experience, and assistance. Inside you will find reference materials, interesting technical discussions, and expert tips and commentary. Once you register for an account you will have immediate access to the forums and all past articles and commentaries.
One of the great things about Diagnostic Manager is the ability to create custom alerts. This is something I believe needs a bit more work, but even in its current state, it is really useful.
I am putting a wiki page together on what a SQL Server DBA needs to monitor daily, weekly, monthly, quarterly and yearly. So far I have created a couple of things here: What does a DBA need to check for daily, weekly, monthly, quarterly and yearly
There are hundreds if not thousands of T-SQL Scripts, Powershell Cmdlets, .NET programs and even old vbscript scripts and on out there to monitor SQL Server and Operating System level performance. I’ve written hundreds of them myself over the years. All of that time and work absolutely paid off. I know a lot about monitoring, going after the right information when something specific is wrong. It also gives me a bag of tricks that mostly causes laptops to run out of disk space often. Disk is cheap though, these days.
In the last post, “Baseline, Performance Reporting and being a proactive DBA” touched on baselines and using them to set thresholds for actively monitoring performance problems on SQL Server. From that post we briefly discussed that every database server is unique. That even being true when the databases we attach to SQL Server are packaged installations from third party applications (like SAP, Dynamics etc…). I received feedback from my good friend Aaron Lowe (Twitter | Blog) on this topic and a very good conversation on how we create these baselines. Aaron had a great point regarding there not being much out there on exactly how to do this so I thought I’d write up a follow-up to the article and some points you can use to create your own baselines.
As database professionals, our intent is to be as proactive as possible when it comes to delivering data with security, stability and speed in mind. Being proactive means active monitoring, reporting performance variations and most important, baseline capture. Adding to these three objectives, we can add Performance Notes to also provide key points of long […]