Finally settled on a permanent solution (for the time being)
Now that many of us are using SSIS on a daily basis, we’ve all reached conclusions and personal “best practices” for SSIS Configurations. SSIS configurations allow you to have flexibility when executing an SSIS package, whether it be for pointing it to a different server, changing attributes at run-time (such passing variables), or simply locking in values (such as connection string passwords) so that they are not lost when the package executes. There are a few blogs on these – I just searched on Google! and found one from Jamie Thomson, a well known SSISer who runs a blog full of tips – that have some good ideas on administering packages with SSIS configurations.
Anyway, what seems to be working for me is to 1) create an XML file configuration for the SQL Server which I am working with, and then 2) for all other configurations add them to a SQL Server table. The use of the XML file allows me to change servers quickly, and the table (which can be moved easily) seems to be working very well for things such as connection string user names and passwords, as well as package passwords. For my current project, I am not putting variable names in the table; if I do this, I am not able to call and send parameters to SSIS packages via the web service that I blogged about earlier. So far so good with this setup, but I’ll continue to experiment and refine of course.
Lee
-----------------------------
Anyone else tired of “metadata out of synch” errors yet?
443868de-628e-484b-9229-441dfe6ab2f3|0|.0