![]() | |
![]() |
| | Thread Tools | Display Modes |
#11
| |||
| |||
|
|
Tom, Did the jobs really originate from an MSX server? If so, then you should read: http://msdn.microsoft.com/en-us/libr...9(SQL.80).aspx Or was msdb restored from another server? (This might have happened, for example, in creating a new server and restoring all of the databases from the old server.) If the latter case, then what you should do is: SELECT job_id, originating_server, name FROM msdb.dbo.sysjobs Is the originating_server column all naming some other, non-MSX, server? If so, then simply: UPDATE msdb.dbo.sysjobs SET originating_server = 'NewServer' WHERE originating_server = 'OldServer' Of course, you need to have enough rights to run this script but that should set the names correctly. In order to work with these jobs through SQL Agent, I believe that you have to stop then restart SQL Agent in order to refresh its cache. RLF "Tom Parke" <Tom Parke (AT) discussions (DOT) microsoft.com> wrote in message news:ADEA14D8-1BBE-4CD9-82F7-A2D5AD865C47 (AT) microsoft (DOT) com... I am running MS SQL 2000. There are some agent jobs that I can not delete - Error 14274: Cannot add, update or delete a job that originated from an MSX server. How do I delete these jobs? Tom |
#12
| |||
| |||
|
|
Tom, Did the jobs really originate from an MSX server? If so, then you should read: http://msdn.microsoft.com/en-us/libr...9(SQL.80).aspx Or was msdb restored from another server? (This might have happened, for example, in creating a new server and restoring all of the databases from the old server.) If the latter case, then what you should do is: SELECT job_id, originating_server, name FROM msdb.dbo.sysjobs Is the originating_server column all naming some other, non-MSX, server? If so, then simply: UPDATE msdb.dbo.sysjobs SET originating_server = 'NewServer' WHERE originating_server = 'OldServer' Of course, you need to have enough rights to run this script but that should set the names correctly. In order to work with these jobs through SQL Agent, I believe that you have to stop then restart SQL Agent in order to refresh its cache. RLF "Tom Parke" <Tom Parke (AT) discussions (DOT) microsoft.com> wrote in message news:ADEA14D8-1BBE-4CD9-82F7-A2D5AD865C47 (AT) microsoft (DOT) com... I am running MS SQL 2000. There are some agent jobs that I can not delete - Error 14274: Cannot add, update or delete a job that originated from an MSX server. How do I delete these jobs? Tom |
#13
| |||
| |||
|
|
Tom, Did the jobs really originate from an MSX server? If so, then you should read: http://msdn.microsoft.com/en-us/libr...9(SQL.80).aspx Or was msdb restored from another server? (This might have happened, for example, in creating a new server and restoring all of the databases from the old server.) If the latter case, then what you should do is: SELECT job_id, originating_server, name FROM msdb.dbo.sysjobs Is the originating_server column all naming some other, non-MSX, server? If so, then simply: UPDATE msdb.dbo.sysjobs SET originating_server = 'NewServer' WHERE originating_server = 'OldServer' Of course, you need to have enough rights to run this script but that should set the names correctly. In order to work with these jobs through SQL Agent, I believe that you have to stop then restart SQL Agent in order to refresh its cache. RLF "Tom Parke" <Tom Parke (AT) discussions (DOT) microsoft.com> wrote in message news:ADEA14D8-1BBE-4CD9-82F7-A2D5AD865C47 (AT) microsoft (DOT) com... I am running MS SQL 2000. There are some agent jobs that I can not delete - Error 14274: Cannot add, update or delete a job that originated from an MSX server. How do I delete these jobs? Tom |
#14
| |||
| |||
|
|
Tom, Did the jobs really originate from an MSX server? If so, then you should read: http://msdn.microsoft.com/en-us/libr...9(SQL.80).aspx Or was msdb restored from another server? (This might have happened, for example, in creating a new server and restoring all of the databases from the old server.) If the latter case, then what you should do is: SELECT job_id, originating_server, name FROM msdb.dbo.sysjobs Is the originating_server column all naming some other, non-MSX, server? If so, then simply: UPDATE msdb.dbo.sysjobs SET originating_server = 'NewServer' WHERE originating_server = 'OldServer' Of course, you need to have enough rights to run this script but that should set the names correctly. In order to work with these jobs through SQL Agent, I believe that you have to stop then restart SQL Agent in order to refresh its cache. RLF "Tom Parke" <Tom Parke (AT) discussions (DOT) microsoft.com> wrote in message news:ADEA14D8-1BBE-4CD9-82F7-A2D5AD865C47 (AT) microsoft (DOT) com... I am running MS SQL 2000. There are some agent jobs that I can not delete - Error 14274: Cannot add, update or delete a job that originated from an MSX server. How do I delete these jobs? Tom |
#15
| |||
| |||
|
|
Tom, Did the jobs really originate from an MSX server? If so, then you should read: http://msdn.microsoft.com/en-us/libr...9(SQL.80).aspx Or was msdb restored from another server? (This might have happened, for example, in creating a new server and restoring all of the databases from the old server.) If the latter case, then what you should do is: SELECT job_id, originating_server, name FROM msdb.dbo.sysjobs Is the originating_server column all naming some other, non-MSX, server? If so, then simply: UPDATE msdb.dbo.sysjobs SET originating_server = 'NewServer' WHERE originating_server = 'OldServer' Of course, you need to have enough rights to run this script but that should set the names correctly. In order to work with these jobs through SQL Agent, I believe that you have to stop then restart SQL Agent in order to refresh its cache. RLF "Tom Parke" <Tom Parke (AT) discussions (DOT) microsoft.com> wrote in message news:ADEA14D8-1BBE-4CD9-82F7-A2D5AD865C47 (AT) microsoft (DOT) com... I am running MS SQL 2000. There are some agent jobs that I can not delete - Error 14274: Cannot add, update or delete a job that originated from an MSX server. How do I delete these jobs? Tom |
#16
| |||
| |||
|
|
Tom, Did the jobs really originate from an MSX server? If so, then you should read: http://msdn.microsoft.com/en-us/libr...9(SQL.80).aspx Or was msdb restored from another server? (This might have happened, for example, in creating a new server and restoring all of the databases from the old server.) If the latter case, then what you should do is: SELECT job_id, originating_server, name FROM msdb.dbo.sysjobs Is the originating_server column all naming some other, non-MSX, server? If so, then simply: UPDATE msdb.dbo.sysjobs SET originating_server = 'NewServer' WHERE originating_server = 'OldServer' Of course, you need to have enough rights to run this script but that should set the names correctly. In order to work with these jobs through SQL Agent, I believe that you have to stop then restart SQL Agent in order to refresh its cache. RLF "Tom Parke" <Tom Parke (AT) discussions (DOT) microsoft.com> wrote in message news:ADEA14D8-1BBE-4CD9-82F7-A2D5AD865C47 (AT) microsoft (DOT) com... I am running MS SQL 2000. There are some agent jobs that I can not delete - Error 14274: Cannot add, update or delete a job that originated from an MSX server. How do I delete these jobs? Tom |
#17
| |||
| |||
|
|
Tom, Did the jobs really originate from an MSX server? If so, then you should read: http://msdn.microsoft.com/en-us/libr...9(SQL.80).aspx Or was msdb restored from another server? (This might have happened, for example, in creating a new server and restoring all of the databases from the old server.) If the latter case, then what you should do is: SELECT job_id, originating_server, name FROM msdb.dbo.sysjobs Is the originating_server column all naming some other, non-MSX, server? If so, then simply: UPDATE msdb.dbo.sysjobs SET originating_server = 'NewServer' WHERE originating_server = 'OldServer' Of course, you need to have enough rights to run this script but that should set the names correctly. In order to work with these jobs through SQL Agent, I believe that you have to stop then restart SQL Agent in order to refresh its cache. RLF "Tom Parke" <Tom Parke (AT) discussions (DOT) microsoft.com> wrote in message news:ADEA14D8-1BBE-4CD9-82F7-A2D5AD865C47 (AT) microsoft (DOT) com... I am running MS SQL 2000. There are some agent jobs that I can not delete - Error 14274: Cannot add, update or delete a job that originated from an MSX server. How do I delete these jobs? Tom |
#18
| |||
| |||
|
|
Tom, Did the jobs really originate from an MSX server? If so, then you should read: http://msdn.microsoft.com/en-us/libr...9(SQL.80).aspx Or was msdb restored from another server? (This might have happened, for example, in creating a new server and restoring all of the databases from the old server.) If the latter case, then what you should do is: SELECT job_id, originating_server, name FROM msdb.dbo.sysjobs Is the originating_server column all naming some other, non-MSX, server? If so, then simply: UPDATE msdb.dbo.sysjobs SET originating_server = 'NewServer' WHERE originating_server = 'OldServer' Of course, you need to have enough rights to run this script but that should set the names correctly. In order to work with these jobs through SQL Agent, I believe that you have to stop then restart SQL Agent in order to refresh its cache. RLF "Tom Parke" <Tom Parke (AT) discussions (DOT) microsoft.com> wrote in message news:ADEA14D8-1BBE-4CD9-82F7-A2D5AD865C47 (AT) microsoft (DOT) com... I am running MS SQL 2000. There are some agent jobs that I can not delete - Error 14274: Cannot add, update or delete a job that originated from an MSX server. How do I delete these jobs? Tom |
#19
| |||
| |||
|
|
Tom, Did the jobs really originate from an MSX server? If so, then you should read: http://msdn.microsoft.com/en-us/libr...9(SQL.80).aspx Or was msdb restored from another server? (This might have happened, for example, in creating a new server and restoring all of the databases from the old server.) If the latter case, then what you should do is: SELECT job_id, originating_server, name FROM msdb.dbo.sysjobs Is the originating_server column all naming some other, non-MSX, server? If so, then simply: UPDATE msdb.dbo.sysjobs SET originating_server = 'NewServer' WHERE originating_server = 'OldServer' Of course, you need to have enough rights to run this script but that should set the names correctly. In order to work with these jobs through SQL Agent, I believe that you have to stop then restart SQL Agent in order to refresh its cache. RLF "Tom Parke" <Tom Parke (AT) discussions (DOT) microsoft.com> wrote in message news:ADEA14D8-1BBE-4CD9-82F7-A2D5AD865C47 (AT) microsoft (DOT) com... I am running MS SQL 2000. There are some agent jobs that I can not delete - Error 14274: Cannot add, update or delete a job that originated from an MSX server. How do I delete these jobs? Tom |
![]() |
| Thread Tools | |
| Display Modes | |
| |