Post reply

statistics time on

  • October 13, 2007 at 4:38 am

    #125882

    SQL Server Execution Times:

    CPU time = 0 ms, elapsed time = 0 ms.

    (1700206 row(s) affected)

    SQL Server Execution Times:

    CPU time = 43905 ms, elapsed time = 308705 ms.

    Below given result is statistics time on :For better performance what is elapsed and cpu time should be available.

    SQL Server Execution Times:

    CPU time = 43905 ms, elapsed time = 308718 ms.

    SQL Server Execution Times:

    CPU time = 43905 ms, elapsed time = 308718 ms.

  • October 13, 2007 at 10:10 am

    #741792

    If you're asking how long we think it should take for you to process the 1.7 million rows that your are... we have no clue because we don't know what your process is doing. I can tell you that it's taking 43 seconds worth of computer time and that it probably got blocked several times or is heavily RBAR because it took 308 seconds (about 7 1/2 times) longer duration wise to execute than there was CPU time.

    I've found that high performance queries, regardless of the activity on the server, have very little difference between the CPU time and the elapsed time. You might want to SET STATISTICS IO on and see what it's doing to the hard disk for reads and writes. That could certainly be part of the problem, as well.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

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

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