Server name and srv name in sysjobsdefers | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Server name and srv name in sysjobsdefers

Hi !
I notice that @@servername returns different name than
sysjobs .Originatingserver have. But jobs are runing fine.
I also looked in host file: nothing maped in there
How it possible??
Thank you
Hi, Your servername might have been renamed. If you encounter errors in the future, refer to this:
http://support.microsoft.com/?kbid=281642 This happened to me already but I just updated/renamed the originating_server field on msdb..sysjobs. So far, my jobs are still running fine. Jon M
Server defenately was renamed.But jobs are runing smothly
How come?
We do have deadlocs though
Well i guessed because msdb..sysjobs uses job_id as the primary key and not the originating_server that’s why your jobs are still running.<br /><br />Jon M [<img src=’/community/emoticons/emotion-2.gif’ alt=’:D‘ />]
IF the jobs are running fine then why to worry as far as SQL error log doesn’t return AV and dump. _________
Satya SKJ
Moderator
SQL-Server-Performance.Com

I am preparing an other server : absolute copy on this one but different name.
so i wondering should i rename originatin server in sysjobs or not
Its better to not to touch system tables when the jobs/process are working fine without any issue. _________
Satya SKJ
Moderator
SQL-Server-Performance.Com

Sorry i get it now : I just was trying to disable one of those successfully running job
using Enterprise manager and
Sql notify me that cannot do it as i have strange originating server .
As soon as i change it it went smothly.
So i made a conclusion :
If you have standby server with different name than original.
When at some point of time you decide to swich to standby (production server down)
After restoring all dbs it compulsory to run this: update sysjobs set originating_server=’StandByServerName’
On all my servers & network I never had such issue, as a rule if we create a job or dts package on Live then the same will be created on Standby server but in disabled mode. _________
Satya SKJ
Moderator
SQL-Server-Performance.Com

Well our standby is hot backup from production server so we cannot "create"
anything on it : third party sofware taking care of everything. I mean when i create job on production in few minutes that job will exist on standby without human help .But it going to be exact copy (including originatin server) of production job.
How its possible?
Are you restoring MSDB too on the standby server? _________
Satya SKJ
Moderator
SQL-Server-Performance.Com

Yes and master Double-Take software
Then in that case I agree with you, as at our end we only restore user database but any job/package will be created twice with one disabled. _________
Satya SKJ
Moderator
SQL-Server-Performance.Com

]]>