Performance Problem that I can't pin down

  • Frankly he should be on at least SP1, preferably SP2 regardless of problems....

    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
  • Bob Fazio (9/12/2011)


    There is also a patch we are strongly looking at. http://support.microsoft.com/default.aspx?scid=kb;EN-US;976700

    The reason why we are leaning towards the patch, is because I think everyone agrees, one bad query shouldn't take down a server of this (or really any) size.

    It's also included in SP1, which we might also apply.

    Oh yeah, I've seen a single query take down a server before. It doesn't take much unfortunately. The right combination of bad code & bad structure... things can go downhill rather quickly.

    ----------------------------------------------------
    The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore Roosevelt
    The Scary DBA
    Author of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd Edition
    Product Evangelist for Red Gate Software

  • GilaMonster (9/12/2011)


    Frankly he should be on at least SP1, preferably SP2 regardless of problems....

    I am on SP2 -CU3 for SQL 2008 I am referring to Windows 2008 R2 (SP1)

  • After tuning nearly every query in our app (of course a good thing) we still couldn't explain why even at what appeared to be relatively low CPU loads, the system would crawl. So we applied SP1 to windows 2008 R2... And the result has been night and day. It is finally running like I would expect a system to run. No question in my mind, this was our issue all along.

Viewing 4 posts - 31 through 34 (of 34 total)

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