![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Sorry if this is inappropriate in DTS ... this was the closest I could find for 2005 and SSIS. I'm trying to create a single, all-purpose SSIS package that would move data from a source database table to a matching target database table. The requirement is to create the package such that the SQL statement used by SSIS could be supplied at runtime. This would allow a single package to be used for different SQL statements, representing different tables, rows and columns, etc. as needed. The data movement combinations are highly variable, so I'm hoping to find a flexible one-size-fits-all solution with a single package. I've looked at setting up a string variable for the SQL statement, and populating it at runtime using a config file or command line SET statement. The package is initially built with a temporary SQL statement for the variable ("select x from dual" -- appologies to the Oracle folks.) When I use a config file and substitute in the SQL statement I want to use on a given run (i.e. select * from myTable) SSIS complains about verification, column mismatch problems, etc. I've played with shutting off validation, but I'm not sure how to get around the output and metadata column problems, etc. I'd like to try to avoid writing custom components w/ C# for this. Before I go down that route I was wondering if anyone had tried this or had a suggestion. Thanks so much! -- Doug |
#3
| |||
| |||
|
|
Doug, Have you looked at creating a wrapper (parent) package that could pass in a variable? I don't know that that would work for this scenario but it *might* get round the mismatch problems. Maybe worth exploring? Andrew Watt MVP - InfoPath On Mon, 17 Oct 2005 19:55:03 -0700, "Doug" Doug (AT) discussions (DOT) microsoft.com> wrote: Sorry if this is inappropriate in DTS ... this was the closest I could find for 2005 and SSIS. I'm trying to create a single, all-purpose SSIS package that would move data from a source database table to a matching target database table. The requirement is to create the package such that the SQL statement used by SSIS could be supplied at runtime. This would allow a single package to be used for different SQL statements, representing different tables, rows and columns, etc. as needed. The data movement combinations are highly variable, so I'm hoping to find a flexible one-size-fits-all solution with a single package. I've looked at setting up a string variable for the SQL statement, and populating it at runtime using a config file or command line SET statement. The package is initially built with a temporary SQL statement for the variable ("select x from dual" -- appologies to the Oracle folks.) When I use a config file and substitute in the SQL statement I want to use on a given run (i.e. select * from myTable) SSIS complains about verification, column mismatch problems, etc. I've played with shutting off validation, but I'm not sure how to get around the output and metadata column problems, etc. I'd like to try to avoid writing custom components w/ C# for this. Before I go down that route I was wondering if anyone had tried this or had a suggestion. Thanks so much! -- Doug |
![]() |
| Thread Tools | |
| Display Modes | |
| |