Urgent: Need Help to change server connection of SSIS packages

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » SQL Server 2005 Integration Services » Urgent: Need Help to change server connection...

Urgent: Need Help to change server connection of SSIS packages

Rate Topic

Display Mode

Topic Options

Author

Message

shiju.cusat

Posted Wednesday, September 08, 2010 7:40 PM

Forum Newbie

Group: General Forum Members
Last Login: Thursday, September 16, 2010 5:46 PM
Points: 1, Visits: 3

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

Post #982750

WayneS

Posted Wednesday, September 08, 2010 9:03 PM

SSCertifiable

Group: General Forum Members
Last Login: Today @ 3:13 PM
Points: 6,386, Visits: 8,286

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

If you can't explain to another person how the code that you're copying from the internet works, then DON'T USE IT on a production system! After all, you will be the one supporting it!

Links: For better assistance in answering your questions, How to ask a question, Performance Problems, Common date/time routines,
CROSS-TABS and PIVOT tables Part 1 & Part 2, Using APPLY Part 1 & Part 2, Splitting Delimited Strings

Post #982769

Alvin Ramard

Posted Thursday, September 09, 2010 7:57 AM

Hall of Fame

Group: General Forum Members
Last Login: Today @ 10:49 AM
Points: 3,035, Visits: 7,396

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.

Alvin Ramard
Memphis PASS Chapter

All my SSC forum answers come with a money back guarantee. If you didn't like the answer then I'll gladly refund what you paid for it.

Post #983098

« Prev Topic | Next Topic »

Permissions