Just a quick blog post today.

I wanted to see how long all my packages were taking to run in SSIS on SQL Server 2012, due to there being some storage issues, which related to the jobs taking longer to run.

So below is the query that I used to pass my parent package, so that I could then get back all the child packages.


        Distinct (EX.executable_id)








  FROM[internal].[executables]asEXwith (nolock)

       Innerjoininternal.executable_statisticsasEXSwith (nolock)


  whereEx.package_name=‘SCOM Parent Package.dtsx’


NOTE: Just change the Ex.Package_Name to your package you want to view the SSIS history for.

In my next blog Post I will show you how to use Power Query and by passing a parameter to then view the output of your query.

0 thoughts on “SSIS – Package duration time”

  1. Select Distinct (EX.executable_id),
    (EXS.execution_duration/1000) asDurationInSeconds,
    convert(Date, EXS.start_time) as ExecutionDate,
    FROM internal.executables as EX with (nolock) Inner join internal.executable_statistics as EXS with (nolock)
    on EX.executable_id = EXS.executable_id
    where Ex.package_name = ‘SCOM Parent Package.dtsx’

    Msg 208, Level 16, State 1, Line 1
    Invalid object name ‘internal.executables’.

  2. Please check the version: Microsoft SQL Server 2012 (SP3) (KB3072779) – 11.0.6020.0 (X64)
    Oct 20 2015 15:36:27
    Copyright (c) Microsoft Corporation
    Developer Edition (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1)

Leave a Reply

Your email address will not be published. Required fields are marked *