Performance tunning SQL 2005

  • Hi Experts,

    I am not so experianced with SQL server performance tunning process. Can you please guide me where to start from if some one says I have performance issues with your server.

    I know it is not straight forward but still your direction to start with will greatly help me.

    Thanks in advance.

    Cheers,

    DBA_2005

  • Start by running a profiler trace and perfmon session.

    There are many articles on this siteif you search for them...

  • Google it.:-) that can hep you better because nobody has precise answers/description for your query.

    -------Bhuvnesh----------
    I work only to learn Sql Server...though my company pays me for getting their stuff done;-)

  • David Sorauer (6/16/2010)


    Start by running a profiler trace and perfmon session.

    There are many articles on this siteif you search for them...

    Running the profiler in the first place is always always a bad idea.

    Here are the basic check you can do:

    1) Find out if only the DB (or a single query) is slow or the entire instane of SQL Server is slow.

    2) Check if there are any blockings on your SQL Server

    3) Check for the Query wait statistics (if applicable)

    4) Side-by-side, take a look on database health wiz. Index health, Stats etc.. and you can also take a look on default trace for historical activities.

    The above should give you enough hint to which direction you should be heading towards.

    -Forum Etiquette: How to post Performance Problems[/url]

    -Forum Etiquette: How to post data/code to get the best help [/url]

  • Maybe start here: http://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-1/

    http://www.simple-talk.com/sql/performance/finding-the-causes-of-poor-performance-in-sql-server,-part-2/

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • Vishal Singh (6/16/2010)


    David Sorauer (6/16/2010)


    Start by running a profiler trace and perfmon session.

    There are many articles on this siteif you search for them...

    Running the profiler in the first place is always always a bad idea.

    Here are the basic check you can do:

    1) Find out if only the DB (or a single query) is slow or the entire instane of SQL Server is slow.

    2) Check if there are any blockings on your SQL Server

    3) Check for the Query wait statistics (if applicable)

    4) Side-by-side, take a look on database health wiz. Index health, Stats etc.. and you can also take a look on default trace for historical activities.

    The above should give you enough hint to which direction you should be heading towards.

    I disagree with your sweeping statement vishal. None of us know exactly what information the op has or doesn't have- he asked a general question...

  • Thank you all for your reply.

    This will help me lot.

  • The posted replies are very good. I especially use Gail Shaw's articles and I've found them very useful.

    But even before I go digging into performance issues that I haven't observed myself, I will always ask "Exactly what isn't performing well?". It may not be an overall condition of the server. I may just be one stored procedure or report. This will help narrow it down.

    Todd Fifield

Viewing 8 posts - 1 through 7 (of 7 total)

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