September 15, 2017 at 3:33 am
Hiya,
I'm using SSIS on 2016 via Project Deployment.
I can query [SSISDB].[catalog].[executions] to find when my packages ran which is helpful.
My master packages appear in this view.
The packages have sequence containers each containing a bunch of 'Execute Package' tasks.
I can query [SSISDB].[catalog].[executable_statistics] and see the steps that occur in the sub packages.
What I am after is the name of the table inside the OLEDB Destination, inside the Data Flow of a package.
I've got a lot of packages, that aren't consistently named, can this be done via TSQL ?
Thank you
Rich
September 15, 2017 at 4:12 am
r5d4 - Friday, September 15, 2017 3:33 AMHiya,
I'm using SSIS on 2016 via Project Deployment.I can query [SSISDB].[catalog].[executions] to find when my packages ran which is helpful.
My master packages appear in this view.The packages have sequence containers each containing a bunch of 'Execute Package' tasks.
I can query [SSISDB].[catalog].[executable_statistics] and see the steps that occur in the sub packages.What I am after is the name of the table inside the OLEDB Destination, inside the Data Flow of a package.
I've got a lot of packages, that aren't consistently named, can this be done via TSQL ?
Thank you
Rich
Nope, afraid not. The details of the tasks are stored in a varbinary, which you won't be able to decrypt.
You'll need to check the packages themselves I'm afraid, either using SSDT, or looking at the XML itself.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
September 15, 2017 at 7:14 am
You can look at [catalog].[execution_component_phases] for the logging information on individual data flow components. However, unless you're using Performance or Verbose logging mode, you won't see anything in this table. It won't log that information on Basic logging, which is the default.
Tim Mitchell
TimMitchell.net | @tmitch.net | Tyleris.com
ETL Best Practices
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply