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 |
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
 Posted - 2003-05-12 : 04:24:45
|
| Anyone know about issues using DTS from SQL 2000 (sp2, + slammer patch) to import jobs from a SQL 7 SP2 server ?WE have found that the old jobs now believe thery are MSX (multiserver admin) jobs, and that the new SQL server is the Target. Part of the complications - potentially even the problem, is that as part of the swop over, the new SQL server (2K) was renamed to the same name as the old SQl server (SQL 7). We note that the SQL jobs, which we can't edit, believe that the Master of the MSX jobs is the OLD name for the SQL 2K server ...Can we defect target server ? Can we update jobs to ensure they aren't MSX (since they never were!) ?Ciao*#&#* *#&#* *#&#* *#&#* Chaos, Disorder and Panic ... my work is done here! |
|
|
smccreadie
Aged Yak Warrior
505 Posts |
Posted - 2003-05-12 : 12:50:13
|
| I've moved jobs by scripting them and then running the script in SQL2K. That works well - haven't tried it with DTS. |
 |
|
|
jasper_smith
SQL Server MVP & SQLTeam MVY
846 Posts |
Posted - 2003-05-12 : 18:45:02
|
| You need to update sysjobs to reflect the new server name in the originating_server column. You can use this sp to do that [url]http://sqldev.net/download/sqlagent/sp_sqlagent_rename.sql[/url]HTHJasper Smith0x73656c6563742027546f6f206d7563682074696d65206f6e20796f75722068616e6473203f27 |
|
|
|
|
|
|
issues with DTS migrated jobs ..