is there a way to capture what gets written to the progress tab to a table, or is it overwritten on each execution as xml somewhere so it can be saved kind of like an odometer? the mission is to be able to audit the results of a load, or even if it doesnt turn out to be a load, then document the run.
similarly, is there a way to watch what executes to see what actually runs during a merge join transform, iow, something that exposes ssis to trace? how do i find it?
thanks
drew
You have perf counters but they don't go down as low as individual components (I don't think).
I like the idea of persisting load metadata. Maybe suggest that at the Product Feedback Center.
-Jamie
|||
thanks...as much as id like to take credit for it i got the idea from Kimball and Caserta, quite a great book...though i dont know how workable their recommendations wrt overhead are, not having tried or built any of them yet, but having worked in darkness before makes it all the more appealing to actually try a method for a change <g>.
i thought i would read about their practice recommendations first before diving into the tool. i understand there is another Kimball tome written wrt ssis, so i am up to chapter nine in the first one, and when i finish with the abstraction, i will get into the concrete. here, i have read everything up to last September, and am working my way through the list.
not that you need it (<g>) but i did find a great teaching resource at
https://www.microsoftlearning.com - Course 2943: Updating Your ETL Skills to Microsfot SQL Server Integration Services.
i was very pleased with the lab, and intend to use it as the backbone of my exploration of all the new stuff the new product.
best
drew
