deploying SSIS packages

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Jocky Mac - 30 Jun 2008 17:47 GMT

I have an SSIS package which calls many other SSIS packages. Each of
these was created with the import wizard in SSMS. As a result, they
all have SourceConnectionOLEDB and DestinationConnectionOLEDB
connections listed under the Connection Manager in the package
designer.

T deploy the packages to another server I have saved all of the
packages as files. I can open each file in BIDS to create the
packages on the new server but it will have a different name and
different database names. I do not want to have to edit every single
source and destination connection for each package in BIDS.

Is there a quick way round this?

Reply to this Message

Steve - 30 Jun 2008 21:34 GMT

Google SSIS package configuration.

This like might help:

http://vyaskn.tripod.com/sql_server_2005_making_ssis_packages_portable.htm

> I have an SSIS package which calls many other SSIS packages. Each of
> these was created with the import wizard in SSMS. As a result, they
[quoted text clipped - 9 lines]
>
> Is there a quick way round this?

Reply to this Message