![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi, When I copy my DTS packages (in the .DTS format) from my developpment PC to my production Server and then re-create the packages on the server, I have a problem with the package which synchronizes the other packages : The Ids referenced by it are no longer valid (since the packages have been re-created), so I have to re-select each package. Has anyone a solution so that the link would be kept, as long as the name is correct ? Thank you for your help Benoit |
#3
| |||
| |||
|
|
Hi, When I copy my DTS packages (in the .DTS format) from my developpment PC to my production Server and then re-create the packages on the server, I have a problem with the package which synchronizes the other packages : The Ids referenced by it are no longer valid (since the packages have been re-created), so I have to re-select each package. Has anyone a solution so that the link would be kept, as long as the name is correct ? Thank you for your help Benoit |
#4
| |||
| |||
|
|
-----Original Message----- The action of Save As creates a new package, hence a new package GUID, not just a new version. Two methods- Stop referencing the package by GUID, just use the name. There is no reason to use the GUID unless your own business/development processes use this for consistency. Transfer the packages via an alternative method, such as copying between the sysdtspackages system tables. Transferring DTS Packages (http://www.sqldts.com/default.aspx?204) . |
#5
| |||
| |||
|
|
Concerning your 1st method... I don't see what you mean, even if I select a package using its name, it stores the guid ! |
![]() |
| Thread Tools | |
| Display Modes | |
| |