I want to write a SSIS which picks up the source and destination tables at runtime is it possible. As we have a SSIS which is used to pull data from oracle but the source and destination table name changes.
If the metadata changes (that is the column names change and/or data types) then you cannot do this without manually accounting for the differences.If the structures are the same, then you can build SQL statements to select against the appropriate table name. You can build the SQL in a variable expression.|||
Would you please give an example for this.
|||A little bit of searching will help you out...I found: http://blogs.conchango.com/jamiethomson/archive/2005/12/09/2480.aspx|||
All the source tables have different data type and columns, so I think it is not possible to have 1 common SSIS for all of them.
We are storing our packages under the FileSystem on the server and executing them via jobs. So my question is if we make the changes in the package in BIDS(our Solution file) will it be reflected in the job or we'll have to import the package in File System?
|||Paarul wrote:
All the source tables have different data type and columns, so I think it is not possible to have 1 common SSIS for all of them.
We are storing our packages under the FileSystem on the server and executing them via jobs. So my question is if we make the changes in the package in BIDS(our Solution file) will it be reflected in the job or we'll have to import the package in File System?
If you edit the package that's being referenced in the job, then the changes will be picked up on the next iteration.
No comments:
Post a Comment