Defining a process for troubleshooting performance issues

  • Hello there!

    The issue of poor database performance is one which presents itself from time to time and there are many techniques which can be employed to examine the root cause of slowness.

    Does anyone have a clearly defined process which they use to troubleshoot performance, like a tried and tested 'works for me' method for investigating issues?

    For me I might employ the following (not necessarily in this order)

    -check if data index/statistics maintenance ran successfully (if possible/appropriate re-run if failed)

    -examine fragmentation of indexes (rebuild/re-organ depending on frag amount)

    -examine the last time statistics were updated (maybe update stats depending on age and whether a -large number of data changes had taken place)

    -check if there's any blocking (kill off the offending process if appropriate)

    What would others add/delete from the above list?

    A repeatable process for troubleshooting for all performance issues might be difficult to gather but it were possible it would certainly be useful starting point 🙂

  • You could take a look at this book. It's a complete process for troubleshooting SQL Server

    http://www.sqlservercentral.com/articles/books/76296/

    Luis C.
    General Disclaimer:
    Are you seriously taking the advice and code from someone from the internet without testing it? Do you at least understand it? Or can it easily kill your server?

    How to post data/code on a forum to get the best help: Option 1 / Option 2
  • Thanks - i'll give it a go 🙂

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply