July 24, 2005 at 8:32 pm
Hi Group,
We're getting the above error msg when attempting to modify the job details of an existing job.
It seems that originating_server column in the msdb.sysjobs table is set to nvarchar(30) which is very restrictive and our servernames have been truncated. I believe this is the cause of this problem! Our qualified server names are often in excess of 30 characters! I understand the storage constraints of unicode character datatypes (double the required storage space)but 30 seems too low a setting for this field.
What are the implications of updating the field to say (35) apart from space and the dependent stored proc's that relate to this table (I guess we'd have to update these as well)...ok so it's probably not supported but be damned if I'm gonna change our server names or rebuild jobs everytime we face this problem.
Regards
Grant
July 25, 2005 at 8:48 am
Usually altering system tables is not a good idea, but there can be exceptions. Please check out this article describing a similar situation and see if it helps:
http://www.sqlservercentral.com/columnists/sjones/killthattarget.asp
You'd also need to document this somewhere in your Disaster Recovery plan as if you make this change, it obviously won't persist if you ever had to reinstall SQL Server.
My hovercraft is full of eels.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply