Prev: MS-SQL computer ports
Next: Object Explorer Details
From: Jocky Mac on 30 Jun 2008 12:47
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?
From: Steve on 30 Jun 2008 16:34
Google SSIS package configuration.

This like might help:

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




"Jocky Mac" wrote:

> 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?
>
 | 
Pages: 1
Prev: MS-SQL computer ports
Next: Object Explorer Details