|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Wednesday, May 08, 2013 4:11 PM
Points: 1,033,
Visits: 2,593
|
|
|
|
|
|
SSCarpal Tunnel
       
Group: General Forum Members
Last Login: Yesterday @ 6:03 AM
Points: 4,787,
Visits: 1,335
|
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 5:54 PM
Points: 525,
Visits: 617
|
|
Very 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!
|
|
|
|
|
Ten Centuries
      
Group: General Forum Members
Last Login: Wednesday, May 08, 2013 4:11 PM
Points: 1,033,
Visits: 2,593
|
|
mishaluba, 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.
Tim Mitchell SQL Server MVP www.TimMitchell.net twitter.com/Tim_Mitchell
|
|
|
|