Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Kleber
Yak Posting Veteran
67 Posts |
 Posted - 2004-01-26 : 10:47:02
|
| Hi allI have two SQL Servers 7.0. One of them behold several DTS Packages, some of them very complex and weird. So I ask to you all, how should i proceed to migrate these packages?I realy don't want to recreate it.Tks.Kleber Brazil |
|
|
smccreadie
Aged Yak Warrior
505 Posts |
Posted - 2004-01-26 : 10:50:55
|
| Open the package and choose Save As from the package menu. Here you can specify the new server. You'll have to make some manual tweaks if the connection information changes within the package. |
 |
|
|
Kleber
Yak Posting Veteran
67 Posts |
Posted - 2004-01-26 : 10:55:48
|
| Yeap... I did it. And it works fine, what i wanted, was way to change automaticaly the content of packages. Changing the connection issues automaticaly... But... as i can see, I will have some manual work at all.Tks a lot. |
|
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2004-01-26 : 10:59:16
|
| You could copy packages by just copying rows from msdb..sysdtspackages.I prefer to save and load packages from files - then it is just a matter of copyin the files.You can include an activex script to set connections from a global variablehttp://www.nigelrivett.net/SetDTSRunTimeValues.htmlOr use a set dynamic properties task (but be careful about specific database names in transformations(You are v7 so can't use this).Or create a loader which changes all the connections before running the package (my preference). This could be in t-sql but is probably more natural in a client app language like VB or an activex script in a dts package.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
|
|
|
|
|
|
Migrating DTS Packages