February 7, 2011 at 3:54 pm
Has anyone here ever used the Kimball Slowly Changing Dimension component with two sources? If so, is the KSCD supposed to combine the rows from both sources and then process them? That isn't happening for me.
February 9, 2011 at 3:06 am
I take it your talking about the KimballSCD from codeplex and not the standard one in SSIS ? If I have source data from multiple sources I stage it into one table then run it through the KimballSCD , or just union the sources in the flow before putting into the KimballSCD.
I can't imagine how you would use the KimballSCD to combine the rows from both sources then process
Can you explain what you have feeding each of the sources on the SCD and what outputs you have hooked up?
Three inputs available:
Source System : um for your new data from source(s)
Existing Dimension : the exisiting dimension data
Special Members : special dimension members that you don't want touched, like the 'unknown' member
February 28, 2011 at 12:15 pm
Please pardon the delay. This is definitely the Kimball Method Slowly Changing Dimension from Codeplex instead of the standard SSIS SCD. Here is how we have it set up:
There are two sources. One source is from our SQL Server staging database. The second source is from a SharePoint list using something called a SharePoint List Source object.
The output is a SharePoint list using the SharePoint List Destination object.
February 28, 2011 at 5:16 pm
I need to make a correction. The exisiting dimension is a SharePoint list. The source system is a SQL Server table. The output is a different SharePoint list. I guess it becomes a question of whether the Kimball Slowly Changing Dimension can handle a SharePoint List Source as an existing dimension.
March 1, 2011 at 8:36 am
If I have source data from multiple sources I stage it into one table then run it through the KimballSCD , or just union the sources in the flow before putting into the KimballSCD.
This is the way to go. There should be at least one staging data base prior to adding the data to the database that is the warehouse so that the data can be combined and conformed.
March 1, 2011 at 9:23 am
imani_technology (2/28/2011)
I need to make a correction. The exisiting dimension is a SharePoint list. The source system is a SQL Server table. The output is a different SharePoint list. I guess it becomes a question of whether the Kimball Slowly Changing Dimension can handle a SharePoint List Source as an existing dimension.
I've no experience with using share point lists in SSIS (presumably your using the sharepoint adapters like http://msdn.microsoft.com/en-us/library/dd365137.aspx ),
Your above statement doesn't make sense to me in that your exisiting dimension share point list is a 'different' list to the destination ? Unless your two lists are linked in some manner, I'm suspecting your attempting to do something with the KSCD that its not supposed to do!
March 1, 2011 at 11:11 am
Yes, one SharePoint list is an existing dimension and a different SharePoint list is the destination. I need to ask the boss why it is being done this way.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply