InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comTue, 18 Jun 2013 01:33:32 GMT20http://www.sqlservercentral.com/Forums/Topic624488-258-1.aspxmishaluba, you're right - if you're doing a lot of transformation, storage will be a key consideration. I worked recently with a very large ETL process in which tens of millions of records were converted from a legacy system, and every single record had some sort of transformation on it. The auditing tables more than doubled the size of our staging database, but my staff has had to return to that auditing data several different times for forensic purposes.Sat, 05 Sep 2009 21:34:23 GMTTim Mitchellhttp://www.sqlservercentral.com/Forums/Topic624488-258-1.aspxVery good example of auditing in SSIS. Something to keep in mind is if the percentage of "bad" records is significant, your Audit table will rival in size the actual destination table, so this should be considered at design time. Thank you!Tue, 30 Dec 2008 17:40:05 GMTmishalubahttp://www.sqlservercentral.com/Forums/Topic624488-258-1.aspxNice one...:)Thu, 25 Dec 2008 04:35:45 GMTAnipaulhttp://www.sqlservercentral.com/Forums/Topic624488-258-1.aspxComments posted to this topic are about the item [B]<A HREF="/articles/SQL+Server+Integration+Services/65115/">Auditing Changes in ETL with SSIS</A>[/B]Tue, 23 Dec 2008 00:26:37 GMTTim Mitchell