Have you ever been struck by the lack of detailed logging available within SQL Server Integration Services (SSIS) packages?
If the answer to this question is yes, then you are probably a seasoned Business Intelligence solutions builder. The packages that make up your solutions probably contain extra code to facilitate effective monitoring, control and profileing. However, increasingly, SSIS is being used to unify data found on disparate yet related transactional systems. The batch processes that perform this activity thus become a vital part of the information processing ecosystem. These need to be monitored and profiled in the same way as formal BI solutions but often the resources available are much more meager. What do you do when something goes wrong and the functionality of the packages is not transparent via internal state reporting.
This session will introduce you to an improved version of DTExec. By passing the appropriate state flags it can reveal the internal activity of packages without having to make any changes to the packages themselves.