Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SSIS and Import/Export (2005)
 any experience with dtloggedexec

Author  Topic 

tybaltzeke
Starting Member

28 Posts

Posted - 2009-09-10 : 20:03:28
we are trying to determine which lookup in a series of 10-15 is causing a package to execute slowly. i'm wondering if anyone out there has experience with dtloggedexec?

does it do a good job of showing which component in a dataflow task is taking the most time? does it as advertised show starttime endtime and rows processed for EACH component in a dataflow task?

is there any way WITHIN SSIS ITSELF (without external utility) provide starttime endtime and rows processed for each component in a dataflow task (more detailed than the dataflow package as a whole)? We could put each component in its own container and do logging by container but it would be preferable to do this without modifying the code (production code freeze).

YellowBug
Aged Yak Warrior

616 Posts

Posted - 2009-09-11 : 10:32:26
I've never used dtloggedexec - but it looks good.
Suggest you look at codeplex for other tools, if this doesn't work out.
This may help: http://ssisloganalyzer.codeplex.com/

You're right. You have to change the logging in the package (to include the pipeline events).
Go to Top of Page

tybaltzeke
Starting Member

28 Posts

Posted - 2009-09-11 : 11:52:17
thanks! point of clarification

in order to get granulurity of logging to the data flow COMPONENT level,
do you mean i 'you're right' you have to add task containers around each component
or do you mean i can just change the way i log pipeline events , and if so how.

the latter would be much better because i wouldnt have to modify packages in production.
Go to Top of Page

YellowBug
Aged Yak Warrior

616 Posts

Posted - 2009-09-12 : 07:14:34
No, to change the logging you have to modify the package. And the logging events are specified at container level.
I was suggesting you include the OnPipelineRowsSent event in the logging on the package and containers.

How do you structure your packages? Do you usually use containers or not?

Do you have BIDS Helper installed? If not, it's well worth installing. And it has a "Pipeline Component Performance Breakdown" that could help you find the bottleneck.
http://bidshelper.codeplex.com/Wiki/View.aspx?title=Pipeline%20Component%20Performance%20Breakdown
Go to Top of Page
   

- Advertisement -