Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


what performance metrics to show before and after optimization/tuning - to show improvement


what performance metrics to show before and after optimization/tuning - to show improvement

Author
Message
VoldemarG
VoldemarG
Valued Member
Valued Member (69 reputation)Valued Member (69 reputation)Valued Member (69 reputation)Valued Member (69 reputation)Valued Member (69 reputation)Valued Member (69 reputation)Valued Member (69 reputation)Valued Member (69 reputation)

Group: General Forum Members
Points: 69 Visits: 190
question: If I am optimizing performance of a few dozen of SPs that i identified via Profiler Trace as taking most time while being the ones most often executed,
and did certain things to improve performance for particularly those SPs. Created some indexes, modified some TSQL inside those SPS, etc.
Now, after I roll out those changes to Production, i will need to show that my improvements/optimization actually has done something, and the performance/metrics are now improved.
Is the best way to prove that changes brought about positive results is to also run Profiler Trace and note that the same SPs ave(duration) and READS have become smaller values? Or is there something else that is useful to
show that modifications (mainly a few dozen of new indexes) have worked and performance is improved? I am thinking what would be most useful to include into my report to management that will show improvement after this tuning/optimization.
Thanks.


Voldemar
likes to play chess
Ravid_ds
Ravid_ds
SSC Journeyman
SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)SSC Journeyman (77 reputation)

Group: General Forum Members
Points: 77 Visits: 550
You can test by mentioning SET STATISTICS ON/OFF while executing the SP.
Jeff Moden
Jeff Moden
SSC-Forever
SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)

Group: General Forum Members
Points: 45430 Visits: 39942
Ravid_ds (1/3/2014)
You can test by mentioning SET STATISTICS ON/OFF while executing the SP.


Oh be careful now. SET STATISTICS is a known liar when it comes to certain forms of code. Please see the following article for proof of that.
http://www.sqlservercentral.com/articles/T-SQL/91724/

--Jeff Moden

RBAR is pronounced ree-bar and is a Modenism for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Wink

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
Jeff Moden
Jeff Moden
SSC-Forever
SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)SSC-Forever (45K reputation)

Group: General Forum Members
Points: 45430 Visits: 39942
VoldemarG (1/2/2014)
question: If I am optimizing performance of a few dozen of SPs that i identified via Profiler Trace as taking most time while being the ones most often executed,
and did certain things to improve performance for particularly those SPs. Created some indexes, modified some TSQL inside those SPS, etc.
Now, after I roll out those changes to Production, i will need to show that my improvements/optimization actually has done something, and the performance/metrics are now improved.
Is the best way to prove that changes brought about positive results is to also run Profiler Trace and note that the same SPs ave(duration) and READS have become smaller values? Or is there something else that is useful to
show that modifications (mainly a few dozen of new indexes) have worked and performance is improved? I am thinking what would be most useful to include into my report to management that will show improvement after this tuning/optimization.
Thanks.


You need to show both because the indexes and other changes you make may have an impact on other things. Here's a URL to help you establish a baseline and then check and see what happens after the changes.
http://www.sqlservercentral.com/articles/baselines/94656/

--Jeff Moden

RBAR is pronounced ree-bar and is a Modenism for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
Although they tell us that they want it real bad, our primary goal is to ensure that we dont actually give it to them that way.
Although change is inevitable, change for the better is not.
Just because you can do something in PowerShell, doesnt mean you should. Wink

Helpful Links:
How to post code problems
How to post performance problems
Forum FAQs
VoldemarG
VoldemarG
Valued Member
Valued Member (69 reputation)Valued Member (69 reputation)Valued Member (69 reputation)Valued Member (69 reputation)Valued Member (69 reputation)Valued Member (69 reputation)Valued Member (69 reputation)Valued Member (69 reputation)

Group: General Forum Members
Points: 69 Visits: 190
Thank you Jeff.
Great article on base-lining that you have referred to. http://www.sqlservercentral.com/articles/baselines/94656/
1) So ideally base-lining would be an ongoing (daily) process with a job setup
that will write a snapshot of config + performance data to base-line tables?
2) and how about the query/SP performance data? The one that comes from DMVs. It does not appear too useful to store a snapshot of such info as the one from sys.dm_exec_query_stats or sys.dm_exec_procedure_stats on a daily basis because the metrics returned by this view get reset when Server restarts and SP is recompiled, etc. ? In other words, my main question is is what's the best way (in addition to Profiler Trace data) to also include an ongoing query performance info into the kind of recurring base-line data collection like the one referred to in the above article?


Voldemar
likes to play chess
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search