Create an “DTSJob.ini” file on the SQL Server like this:

[Server Settings]
Dbtag1=Server1\Instance
Dbtag2=Server2\Instance
Dbname1=DbName1
Dbname2=DbName2

Add a Dynamic Properties Task as the FIRST step in the job and set the
following properties

Connection 1
DataSource
Source: INI File
File: D:\DB\job\Dbtag1\DTSJob\DTSJob1.INI
Section: Server Settings
Key: Dbtag1

Connection 1
Catalog
Source: INI File
File: D:\DB\job\Dbtag1\DTSJob\DTSJob1.INI
Section: Server Settings
Key: DbName1

Connection 2
DataSource
Source: INI File
File: D:\DB\job\Dbtag1\DTSJob\DTSJob1.INI
Section: Server Settings
Key: Dbtag2

Connection 2
Catalog
Source: INI File
File: D:\DB\job\Dbtag1\DTSJob\DTSJob1.INI
Section: Server Settings
Key: DbName2

Make sure this step executes prior to anything else. If you need to
make changes, just change the INI file. The DTS Package itself will
never have to change again.

Trevor

---------------------------------------------------------------------
Original Message:

Why is it that every time I want to make a simpe connection change in a
DTS package that I essentially have to re-write everything? Am I the
only one that has problems with this? I change the connection and have
to re-do the transformations, then, when I run it, it still point to the
old tables/connection even though I have changed everything.

Frustrated again



---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
Website : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html





MS Sql Server LazyDBA home page