Home Forums SQL Server 2008 SQL Server 2008 Performance Tuning what performance metrics to show before and after optimization/tuning - to show improvement RE: what performance metrics to show before and after optimization/tuning - to show improvement

  • January 3, 2014 at 10:33 pm

    #1677487

    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.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)