Post reply

Difference between task time and sys.dm_exec_query_stats time

  • October 18, 2019 at 10:56 am

    #3690069

    Hello

     

    I have a SQL task that ran through yesterday in around 23 minutes

    It executes an SP and performs a couple of updates

    If I look at the DMV stats, this task is is showing as taking around 20 hours!

    sys.dm_exec_query_stats time total_worker_time

    Also sys.dm_exec_procedure_stats

    There's only one execution for ths SP

    It's definitely this one as the creation_time and last_exection time corresponds and there's only been 1 execution

     

    Any ideas what causes this discrepency?

    It's almost like it kicks it off and then just goes and completes the package BUT, it takes 23 mins in sysssislog

     

    Thanks

     

    - Damian

  • October 18, 2019 at 3:03 pm

    #3690191

    When looking at the dynamic management views, total_worker_time is CPU usage, you would have to look at total_elapsed_time to find the duration the query executions were actually running.  Does this query have any parallelism in the execution plan?

     

  • October 20, 2019 at 4:22 pm

    #3690450

    Thanks Chris

    I will take a look when I am back in the office

    In this instance, it ran once

    I don't think parallelism shows up in the plan

    If it did though, would it not impact the task time?

    I've seen parallelism cause high CXPACKET waits but this usually extends the the task time in ssislog

     

    Thanks

    - Damian

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

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