SSIS

Hi I am about to create a new ssis project containing lots of packages...

the packages will point to two databases on a dev server. At a later date i want to move the packages to point to databases of the same name but on a live server...

where am i best to create the connections so i can edit them at a later date to point to different server...
ac_davis2002Asked:
Who is Participating?
 
Jason Yousef, MSSr. BI  DeveloperCommented:
Hi,
You'll need to utilize the SSIS configurations, it's a dynamic configuration property for each environment you move your packages to.

currently there's multiple ways of doing it, the easiest way is using the XML file

Please check these article and decide

http://www.mssqltips.com/sqlservertip/1405/sql-server-integration-services-ssis-package-configuration/

http://www.mssqltips.com/sqlservertip/1434/using-xml-package-configurations-with-integration-services-ssis/

http://www.mssqltips.com/sqlservertip/2459/using-a-sql-server-alias-for-ssis-package-configuration-database-connection-string/

Let me know if you need more help.
Regards,
Jason
0
 
momi_sabagCommented:
there are several options you can use
read this
http://msdn.microsoft.com/en-us/library/ms141682.aspx
0
 
Simone BSenior E-Commerce AnalystCommented:
We are currently using the same scenario, with large numbers of packages on test and live servers. We have found the most efficient way to do this without having to make any connection changes, is to always use localhost in the connection instead of specifying a server name. Then after testing changes to the package(s), we simply copy to production. Because our packages are deployed to the file system, no further changes are required.
0
 
ac_davis2002Author Commented:
Thanks for all your help!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.