Answer by BenchmarkIT
I don't know if this counts but the first thing I ask is "What has changed?" and this speaks to the importance of gather good meaningful baseline metrics and being able to quantify what "poorly...
View ArticleAnswer by nigelrivett
I first ask what is meant by performing slowly. Is it millisecond queries that are now taking seconds or hour long queries that now take days (don't laugh) or just something that takes longer than the...
View ArticleAnswer by K. Brian Kelley
Hopefully I have a baseline as Colin (BenchmarkIT) has pointed out. If I don't, like when I go to a new client, I first check the OS basics:CPUDiskMemoryI want to see what the overall system is doing....
View ArticleAnswer by Grant Fritchey 1
Assuming it's a new machine, I just do the basics, run perfmon to collect counters to see what sort of load is on the system, wait states, and queues. I'll also set up a server side trace to collect...
View ArticleAnswer by Kristen
I don't have to get involved with new, unfamiliar, servers (well, not very often); so I am in the happy position that I only have my own applications to worry about.We log every Sproc execution to a...
View ArticleAnswer by mrdenny
Assuming that no changes have gone into production recently...I usually start with looking for which execution plan suddenly is wrong.A quick peek at a query like this usually tells me which plan is...
View ArticleAnswer by Wes Brown
Always look at execution plans like Mr Denny recommends.Rarely is performance "all of the sudden" poor. I find it has been slowing down for quite a while and you have hit the tipping point where people...
View ArticleAnswer by Jonathan Kehayias
Personally I subscribe to the well vetted and published troubleshooting methodology covered in the Troubleshooting Performance Problems in SQL Server 2005 whitepaper. Basically focus first on Resource...
View Article
