- Create an index on your dimension table for the business key, followed by the current row identifier. If a clustered index does not already exist, create this index as a clustered index, because this will prevent a query plan lookup from getting the underlying row. This will help the lookup that happens in the SCD as well as all of the updates.
- The row - by - row updates can be changed to set - based updates. To do this, you will need to change the OLE DB command to a Destination adapter to stage the records to a temporary table, then in the Control Flow, add an Execute SQL Task to perform the set - based update.
- If you remove all the OLE DB command transformations, then you can also change the Insert Destination to use fast load and essentially bulk insert the data, rather than performing row - at - a - time inserts.
This blog is home to share my experiences, views, learning and findings on BIG Data, MongoDB, Elasticsearch, Hadoop, D3, SQL Server, SQL Azure, MS BI - SSIS, SSAS, SSRS, MDX, Visual BI methods, Excel Services, Visio Services, PPS, Powerpivot. I am co-author of the SQL Server MVP Deep Dives - Volume 2 and have reviewed several other books. Feel free to involve me in your projects. I would be happy to help. You can contact me @ contactsidmehta@gmail.com
Or use http://kimballscd.codeplex.com
ReplyDelete