how to handle primary key violation after 2nd time ETL process
I have 5 data sources in which daily new data is coming the thing I have done ETL once and all data is in my dimension and fact table(s) but how I will handle new data as It will also process the previous data too and primary key will violate so how to handle it (like I dont want to change previous data but I want new data to goto dimension tables so that primary key will not be violated)Tahir Ayoub
October 24th, 2011 4:19am

u can use slowly changing dimension concepts the unchanged data will be ignored new and updated data will be processed into the dimension tables
Free Windows Admin Tool Kit Click here and download it now
October 24th, 2011 4:42am

I have 5 data sources in which daily new data is coming the thing I have done ETL once and all data is in my dimension and fact table(s) but how I will handle new data as It will also process the previous data too and primary key will violate so how to handle it (like I dont want to change previous data but I want new data to goto dimension tables so that primary key will not be violated) Tahir Ayoub There are a number of ways of doing this which I discuss at SSIS: Checking if a row exists and if it does, has it changed? I recommend that you don't use the SCD Dimension Wizard, particularly if your data volumes are anything but tiny.http://sqlblog.com/blogs/jamie_thomson/ | @jamiet | About me
October 24th, 2011 5:01am

u can use slowly changing dimension concepts the unchanged data will be ignored new and updated data will be processed into the dimension tables
Free Windows Admin Tool Kit Click here and download it now
October 24th, 2011 11:27am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics