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 |
|
avmreddy17
Posting Yak Master
180 Posts |
 Posted - 2006-05-10 : 11:47:35
|
| Recently we renamed one of the SQL Server 2000 Server from NAME1 to NAME2. In the msdb..sysjobs table the originating_server name is still the old name ( NAME1 ). As SQL server 2000 suports multiple instanaces it will not rename it back to local.So my Question is If I update the sysJobs table's Originating_Server Column to the new Server Name ( NAME2 ) . Will I have any issues. Because I not able to make any changes to the Jobs as it throws an 14274 Error. I don't want to rename the server back to the original name and do all the process as its given in the MSDN Article.ThxVenu |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2006-05-10 : 16:29:58
|
| It's never caused me problems and is the only way I've found to be able to maintain jobs after a server name change.==========================================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. |
 |
|
|
avmreddy17
Posting Yak Master
180 Posts |
Posted - 2006-05-10 : 16:59:00
|
| Thanks ... I just updated the table and looks good for now |
|
|
|
|
|
|
msdb..sysjobs