First, some background.
I am building an archive process that sends records from an operational data store to a separate archive server and database. A list of tables whose records are to be sent across are pulled into a DTSX package. Aforeachloop container cycles through the tables one at a time. Inside the container is ascript task. The script task programmatically builds a new DTSX package and populates it with adata flow task containing both source and destination components. I have successfully sent data across our servers using this new dynamically generated package, however, there is a problem.
One of the tables has a computed column. This computed column is a part of the table schema on both the ODS and archive databases. Trying to insert data into a computed column will cause the package to fail. I have spoken with the DBA and gotten a few suggestions (change archive table schema, store values "normally" and adjust logic to populate it, use DMVs to look for computed columns, etc.) but I'm hoping something within the SSIS API can help me out. Is it possible to ignore any column in the destination (input) that would throw a read-only error? Is there something within the metadata objects I could use to do so?
Thanks in advance.