• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 45
  • Last Modified:

Best approach for history retention in SSIS ETL

I am looking for advise what would be the best approach for storing history of ETL load. The way ETL works is I am receiving flat file and it is loaded to staging area and from staging area to a production table and to a view
What would be the best approach in case I got duplicate file and load it I do not want that to happen
  • 2
1 Solution
zephyr_hex (Megan)DeveloperCommented:
If you want to prevent a duplicate file load, you need a unique way to identify the file.  How would you know it's a duplicate?  Does the file have a unique name?  Or time stamp?  Or column with a unique id ?
robertfl77Author Commented:
Actually there is no unique field in a data that is being provided, execept filename
zephyr_hex (Megan)DeveloperCommented:
If the filename is unique, you can track previously loaded filenames before inserting the new file.  So, for example, add a column to your table for the filename.  Before you load a new file, check and see if any records exist with the filename equal to the filename you're about to load.  If you find at least one, you know the file has been previously loaded and you should not load it again.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now