This blog has been moved to: http://sqlblog.com/blogs/jorg_klein/
This blog post has been moved to: http://sqlblog.com/blogs/jorg_klein/archive/2008/10/22/ssis-decrease-your-fact-table-loading-time-up-to-40.aspx
Great post Jorg. Sometimes the most obvious way of achieving something isn't the best way as you've demonstrated here.
Just one thing - the second screenshot (of the new dataflow) isn't showing up.
Pingback from Lookup performance and buffer usage - SimonS Blog on SQL Server Stuff
I'm trying to apply this method in our ETL solution and the following questions came up:
- the method itself is really straightforward and easy to design but how did you make the logging?
I need to have all the lookup error rows in a log table with the info that which lookup was failed. If I try to implement it at the end of the data flow I don't know how to insert this column.
The so far final result is a hybrid: we won't use Union All only a Multicast and a Derived Column after each LookUp ...
Or maybe I'm just missing some point :)
Anyway your idea is superb because I hate Union All from the dev point of view. Thanks for sharing!
The SQL Server Integration Services team added valuable new caching options (and scalability) to the
SSIS Blog Post Thank you
Learn more about Lookup and its new features: A compilation
Pingback from SSIS Blog Post Thank you | Aaron LoweAaron Lowe