Tomorrow morning I’ll fly to Seattle for the usual PASS Community Summit. I’m really happy for the next week. Even if this period is really full of work and a week away means that at my return I’ll have *really* busy times, the PASS Conference is always a nice break: meeting old and new friends, learning new things, enjoying beers and cocktails and dinners, and, of course, plan and look ahead into the future. Yes I’m really looking forward to be there.
In addition, this year, if you’re into Business Intelligence or Data Integration you’d better not miss my session, dedicated to some of the most common problems and requirements: logging, monitoring and auditing.
Instrumenting, Monitoring and Auditing of SSIS ETL Solutions
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 profiling. 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.
Here’s a sneak peak of what you’ll be able to obtain from your SSIS Packages, after coming to my session, without the needing to write a single line of code or change existing packages:
See you there!