This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(70.4, 13%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
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
For the baseline, Query Store is your answer right there.
For testing querie, restoring a backup better, since if you sciprt tables, the statistics histogramme may come out different. But if the database is very big, you may need to compromise.
Thank you sir.
Sir, I question I have.
In what scenarios just updating statistics would help instead of rebuilding and reorganizing indexes?
What is the logic behind it?
If indexes are not fragmented, there is no point in rebuilding them. But statistics can still be out of date. And whehter you need to rebulid indexes these days to address logical fragmentation, that is, page links being out of order, is disputable. But physical fragmentation, that is, you have a lot free space on your pages, is still a good reason to rebuild your index.