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 |
|
Chainwhip
Starting Member
33 Posts |
 Posted - 2003-07-29 : 16:11:28
|
| What is the best way to copy my local packages from Server A to Server B? I will be using TCP/IP and the sa login. |
|
|
setbasedisthetruepath
Used SQL Salesman
992 Posts |
Posted - 2003-07-29 : 16:16:29
|
| Neither the network protocol nor the logon method affect your issue (provided the account you use has sufficient access, of course).The mechanism for transfer is not as important as isolating any machine-specific references in your packages. Take local drive references as an example. Physically moving the package would break it until the appropriate change was made.If there are no machine-specific references at all, you may consider inserting the appropriate msdb..sysdtspackages rows to your destination server. Otherwise, the best method may be to open each package on Server A, select save as ..., and save it to Server B, and then make the necessary changes.Jonathan{0} |
 |
|
|
Chainwhip
Starting Member
33 Posts |
Posted - 2003-07-29 : 16:22:25
|
| Ok just wanted to check I had to do it in EM. I thought there might be a simple sproc that I might be able to call. |
|
|
|
setbasedisthetruepath
Used SQL Salesman
992 Posts |
Posted - 2003-07-29 : 16:26:14
|
| As I said earlier, you don't have to use EM if you want to issue the appropriate INSERT statements to the sysdtspackages table in the msdb database. I do agree with you that for most situations this isn't the "best" method because the packages have to be manually changed when moved anyway, so one might as well use EM all the way through.Jonathan{0} |
|
|
|
|
|
|
Copying Local Packages across servers