Update takes too long

  • That test was done using SQL Server 2014 Dev Edition. (Local instantaneous running on a laptop)

  • Jason A. Long (5/14/2015)


    That test was done using SQL Server 2014 Dev Edition. (Local instantaneous running on a laptop)

    Local instantaneous? That's fast!

    The absence of evidence is not evidence of absence
    - Martin Rees
    The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
    - Phil Parkin

  • I don't recall recording any specific time measurements. I was more interested in verifying that the execution plan was changing based on the existence of index (and that the index was being used when it existed).

    If I recall correctly, it was about 12 to 14 seconds to render the results

    In both cases, the bulk of the time was spent on rendering the output, so the actual times weren't too far apart, despite the drastic change in cost.

    Speaking of which... Has anyone figured out how to toggle the "Discard results after execution" property is SSMS, using code?

    Switching back and forth using the Options window in a pain... It would be super convenient to be able to toggle is with a code snippet...

  • When I want to just measure server performance I put all outputs from a select directly into variables. Then no return to SSMS no matter how many rows affected.

    Best,
    Kevin G. Boles
    SQL Server Consultant
    SQL MVP 2007-2012
    TheSQLGuru on googles mail service

  • When using a local or development envisonment to troubleshoot a performance issue in production, I focus my efforts on reducing logical reads or maybe CPU.

    A small box with 2 or 4 CPU, 8GB RAM, and local storage isn't just a scaled down version of production; the hardware architecture of a production server is a different animal, and decreasing runtime performance of a query in development by 50% simply won't correspond to a 50% decrease in production.

    "Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

  • Phil Parkin (5/14/2015)


    Jason A. Long (5/14/2015)


    That test was done using SQL Server 2014 Dev Edition. (Local instantaneous running on a laptop)

    Local instantaneous? That's fast!

    WOW!!! I really am a big dumb animal... Missed it twice... :blush:

Viewing 6 posts - 31 through 35 (of 35 total)

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