In the past few blog posts I’ve showed you how to use several methods to track things in SQL Server. You can use the “tags” to the right of this post here at this site to list things like PowerShell, Performance Tuning and so on. Now that you’re armed with these tools, what should you track?
Well, one of the items I track is time. I track the time it takes for lots of things, but they fall into three general buckets:
- Queries – Normally I track the five longest running queries with their query plans.
- Maintenance – From how long each backup takes to index reorgs and rebuilds, I want to know how long these things take.
- Jobs – Most all of us have SQL Server Agent Jobs, and developing a schedule of how long they are running is very useful.
For each of these, I track the minimum, maximum and average times. I look for outliers – things that suddenly change and so on.
There are a lot of uses for this information. From performance tuning to developing a recovery plan, all of these actions need to be taken into account.
I think I’ll write up an article sometime on how I do this – it’s a little long for a blog post.