January 31, 2011 at 6:10 am
any plz one explain scd in detail..........
i tried that, after creating scd automatically three tasks are generated
suppose
OLE DB Source-------(after Edit connect to SCD)----->SCD------(after
edit SCD)-----(automatically 3 tasks are generated)
can any one please explain SCD, and there Types and those automatically generated tasks in detail......
[font="Verdana"]SRIHARI(:~[/font]
January 31, 2011 at 6:22 am
It creates three tasks to handle updates, inserts and deletes into the dimension according to the type of SCD you chose.
I would recomend not using the SCD transformation, instead create your own dataflows to handle the logic in a set-based method,
February 1, 2011 at 3:51 am
http://msdn.microsoft.com/en-us/library/ms141715.aspx
But as steveb already suggested: forget about this component. The bad performance will kill your package.
Create a set-based dataflow yourself (there are plenty of examples on the internet) or use the Kimball SCD (downloadable on Codeplex if I'm not mistaken).
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
February 1, 2011 at 3:58 am
Koen (da-zero) (2/1/2011)use the Kimball SCD (downloadable on Codeplex if I'm not mistaken).
+1 from me for that suggestion , http://kimballscd.codeplex.com/
February 1, 2011 at 6:20 pm
+1 for Kimball SCD. However, there are times when you can still use the standard SCD component that is default in SSIS. For example if your dimension table contains a small number of rows (less than 20,000) or if you prefer the wizard style step by step process for building the SCD. Because um, the Kimball SCD requires you to manually create each one of the outputs.
February 1, 2011 at 11:42 pm
jeff122877 (2/1/2011)
+1 for Kimball SCD. However, there are times when you can still use the standard SCD component that is default in SSIS. For example if your dimension table contains a small number of rows (less than 20,000) or if you prefer the wizard style step by step process for building the SCD. Because um, the Kimball SCD requires you to manually create each one of the outputs.
Even with samll dimensions, I still prefer building the SCD myself. Just to save a few seconds during debugging and testing 🙂
I have a template laying around, so I can quickly generate new packages with SCD functionality.
Thus, my advice to the OP: create it yourself and make a template out of it. Easy to re-use and it can come in handy when your employer doesn't want 3rd party tools like the Kimball SCD installed on their production server.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
February 3, 2011 at 1:14 pm
I've used the inherent SCD component for my ETL with no issues. I don't have a particularly large download each time, and I have read that for high performance requirements it would be better to use set queries, but for small to mid range, I find it very effective.
February 3, 2011 at 8:07 pm
One of the issues with the SCD component in SSIS is that the generated INSERT component does not use the fast load options. If I use the SCD component, this is one of the things that gets changed. It is a bit of a pain because these edits are lost if you re-run the SCD wizard.
June 30, 2011 at 5:30 am
Why don't you change the asynchronous transformation tools to synchronous transformation while editing the SCD. I will work very faster, that's what is said performance tuning.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply