I have an issue with addressing column length change and data type changes in packages
Hi, We have packages with flat files / database as the source. We are seeing the data length and data type changes in the source columns frequently. Our project is completely stabilized. For every change in the source its becoming a rework on packages and Cubes. We have searched for options like data profiling and DQS , but nothing seem to address these issues. Is there a way that we can address these issues out of the box. The issue seems simple but its becoming a hectic job for us to rewrite the code. Any suggestions/ Recommendations, Welcome ! Thanks, Srihari Thakkelapati Srihari
June 28th, 2012 4:48am

hard luck here Srihari.... there is no direct way to solve this problem. if you are using the DFT to load the data than FYI .... DFT doesn't support dynamic metadata. Work Around: 1: Write a Script to check the metadata of the file (Need to create a reference table to check the metadata)----> change metadata accordingly and create a new file for your DFT -----> load the data. OR 2: create separate package for each condition and route the flow accordingly. OR 3: Manually change the file data --Let us TRY this | My Blog :: http://quest4gen.blogspot.com/
Free Windows Admin Tool Kit Click here and download it now
June 28th, 2012 6:13am

hard luck here Srihari.... there is no direct way to solve this problem. if you are using the DFT to load the data than FYI .... DFT doesn't support dynamic metadata. Work Around: 1: Write a Script to check the metadata of the file (Need to create a reference table to check the metadata)----> change metadata accordingly and create a new file for your DFT -----> load the data. OR 2: create separate package for each condition and route the flow accordingly. OR 3: Manually change the file data --Let us TRY this | My Blog :: http://quest4gen.blogspot.com/
June 28th, 2012 6:20am

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

Other recent topics Other recent topics