September 3, 2015 at 5:55 am
Hi Team,
I have a fact load process which is in progress of design . I have notice i would need many of the lookup control to get populate dim keys .
I still not sure in all of the design show to use Lookup control . I know cashing is one of the adv but it has limitation depends on memory.
Can anyone help me to see the proc and cons of the below approach .
Case1:-
Use of Lookup Control in the data flow task . In my case around 15 lookup is required
Case2:
Use Left join on source . In this case i need to join 15 tables to populate Surrogate key.
Thanks in advance ...
September 3, 2015 at 9:50 pm
These two blogs are giving better understanding to me about the issue
http://www.sqlservercentral.com/blogs/jamesserra/2011/08/29/when-to-use-t_2D00_sql-or-ssis-for-etl/
https://derekdb.wordpress.com/2012/03/13/ssis-lookup-or-t-sql-join/
September 4, 2015 at 9:26 am
I would do it on the source. It performs much better.
Alternatively, I would join schedule a job for night time which joins 15 tables, and store the data in flattened table, and then use data from flattened table as a source.
SSIS lookups can be expensive operations.
------------
🙂
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply