March 7, 2012 at 8:49 am
Hi All,
I have to deliver a 'generic' SSIS package, that the client will make multiple copies of, deploy and schedule each copy for different source databases. I have a single SSIS Configuration table in a separate common database. I would like to use this single configuration table for all connections. However the challenge is with the configuration filter. When client make a copy of my package, it will have the same configuration filter just like others. I would like to give an option to the client to change the configuration filter before deploying, because for this new copy, the source database can be different.
Is there a way to change the configuration filter from outside the package (without editing the executable .dtsx file)?
-Shahul
March 7, 2012 at 1:11 pm
I don't think that there is a way to do this. I think you'd be better off going with a file configuration and deploying the file with the package and making the changes there.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
March 8, 2012 at 12:02 am
Jack Corbett (3/7/2012)
I don't think that there is a way to do this. I think you'd be better off going with a file configuration and deploying the file with the package and making the changes there.
+1
Different sources equals different config files.
Unless the copies of the packages are executed on different servers.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
March 8, 2012 at 5:11 am
shahuls2000 (3/7/2012)
Hi All,I have to deliver a 'generic' SSIS package, that the client will make multiple copies of, deploy and schedule each copy for different source databases. I have a single SSIS Configuration table in a separate common database. I would like to use this single configuration table for all connections. However the challenge is with the configuration filter. When client make a copy of my package, it will have the same configuration filter just like others. I would like to give an option to the client to change the configuration filter before deploying, because for this new copy, the source database can be different.
Is there a way to change the configuration filter from outside the package (without editing the executable .dtsx file)?
-Shahul
Is this a custom configuration table or one created in the same way as the configuration xml files (SSIS configurations)?
1. If its a custom config table you can add a filter column based on hostname or an SSIS variable which is passed into the package.
2. If its not a custom config table (SSIS configurations) you "could" create multiple logical databases using filtered views. The SSIS configuration tables use a SQL connection which "could" have its initial catalog set as an expression (pass a database name in as a variable again). I cant see a way to do the same with a table yet but that would be tidier.
3. You can also set the Configuration string as a windows environment variable which would also be dynamic.
March 8, 2012 at 5:13 am
None of these options are ideal which is why I would go for a custom table with settings for centralised management. Avoiding the SSIS section completely. This does mean you'll have to load all the settings manually though.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply