Post reply

Tools to Measuring Query Performance and Implications

  • May 24, 2011 at 7:22 am

    #1329044

    Grant Fritchey (5/24/2011)

    Having had really horrific procedures that had compile time problems, I used to sweat that when I saw the size of a query exceed a certain point, but that was only clearing the procedure cache, not everything.

    Yeah, but that's when dealing with a compile time problem, not for general tuning.

    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

  • May 24, 2011 at 9:54 am

    #1329188

    GilaMonster (5/24/2011)

    Grant Fritchey (5/24/2011)

    Having had really horrific procedures that had compile time problems, I used to sweat that when I saw the size of a query exceed a certain point, but that was only clearing the procedure cache, not everything.

    Yeah, but that's when dealing with a compile time problem, not for general tuning.

    No, absolutely. For general tuning I will run the query three or four times, toss the first result and take the average, just in case I hit some silly contention issue on one of the runs.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

Viewing 2 posts - 16 through 16 (of 16 total)

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