A 14274 error occurs when you attempt to update or delete a job created before SQL Server2000 after a change to the Windows host name. This error does not occur in SQL 7.0, but in a cluster environment, this error may also occur after you upgrade the SQL 7.0 virtual server to SQL Server2000.
Error Reason:
In msdb.. The name of SQL Server instance is saved in the Sysjobs column originating_server, in the format ' ServerInstance ' (in SQL 7.0 (local), so it is not affected). When the server name changes, the sysjobs originating_server is not updated to the new serverinstance.
Solution:
1. Change the server back to its original name
2. Save all job as script and delete
3. Change the server to a new name
4. Perform the script generated in step 2nd to restore all job
or directly update the sysjobs originating_server
Use msdb
Go
sp_configure ' ALLOW UPDATES ', 1 reconfigure with OVERRIDE
Go
Update sysjobs set originating_server=@ @servername
Go
sp_configure ' ALLOW UPDATES ', 0 reconfigure with OVERRIDE
Go
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.