February 22, 2023 at 5:03 pm
Hi All,
We don't have baselines in our env. I mean, no monitoring tool. We use sp_whoisactive every 5 mins. Currently, we are facing some query performance issues.
Want to know what are the things to be considered or how to take query performance baselines? like rows counts, indexes, execution plans etc..
Also, suppose I want to test the same query in sub-prod env, do we need to restore entire prod database of the issue day or just dump those required tables/objects into a testdb and then do the testing on the smaller dataset testdb?
Please suggest.
Thanks,
Sam
February 22, 2023 at 5:58 pm
If this is a production sysyem, and given the amount you have posted recently, it may be cheaper to bring in a consultant. If you are based in India maybe someone like Pinal Dave at SQLAuthority.
February 22, 2023 at 7:57 pm
Broadly speaking, SQL Server performance comes down to indexes (assuming you don't have major issues with RAM, disk I/O, other basics).
Therefore, first I'd suggest reviewing your indexes for performance. Unfortunately, there are very few people who know how to do that properly (and, esp., reasonably quickly).
Note that I'm NOT speaking primarily of rebuilding indexing or that type of maintenance. But, instead, making sure the clustered indexes all have the best keys for each specific table, vs. what you have now, and what missing indexes are critically needed. After that you can worry about rebuilding, etc..
SQL DBA,SQL Server MVP(07, 08, 09) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply