September 8, 2010 at 7:40 pm
Hi,
Currently ism migrating DTS packages to SSIS. There are around 100 packages. I migrated all the packages and tested in my dev server. Now i want to release these packages in to production.
How can i change the connection with in the package dynamically? Because it will be a tedious job for the DBA to open each package and change the server connection. Is there any other way for this?
In DTS package we can open the package from the server itself so that the changes can be done. But for SSIS packages we can't open the packages without SSBIS right? DBA need to open each package in SSBIS, change the connection, then again export to Server?
Please advice.
Thx,
Shiju
September 8, 2010 at 9:03 pm
Set up a configuration file for the server name. Modify each package to use the configuration file (yep, it's labor intensive for 100 packages). On the production server, put the configuration file in the path, and modify it for the proper server name. Then, just deploy your packages, and they will access the configuration file for the server name.
Oh - IMO, it would be best to load the server name into a variable, and use that variable as an expression in all of your connections.
What I do: I have a base SSIS package set up, that uses the configuration file, and has one standard connection. They are all set up to go - just add everything else you need to it.
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
September 9, 2010 at 7:57 am
WayneS (9/8/2010)
... yep, it's labor intensive for 100 packages ...
I agree, but it's not that bad if you think about it before you start. There's lots of benefits associated with proper planning.
Wayne, I agree, a package template is the way to go.
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply