August 31, 2009 at 3:22 am
hi,
we are having standard edition of sql server 2005 in our production environment.
after configuring transactional replication one of my colleague changes the name of the replication jobs for better readability.
now when we go to replcaition monitor-click on the desired publication and go to warning agents tab which is on to the right hand side click on view properties for the job in - agents and job related to this publications section we get an error saying that the job does not exist.
this is beacause we have change the name soa s to give a sensible name.
we checked our replication and it seems to be working fine . i would like to know if there will be any repurcussion due to this and is there any way to avoid this error in the replication monitor tab such that it recognises the new job name specified.
thanks for your help.
September 1, 2009 at 2:39 am
To fix your problem I'm guessing you will have to change the name in the relevant tables in the distribution database. There are a number of tables, e.g. mslogreader_agents, msdistribution_agents, which have a "name" column. That "name" column maps to the "name" column in msdb..sysjobs so I'm thinking you have broken the link between the two by only changing the names in msdb..sysjobs. You now need to re-align them.
Having said all that, I'm surprised you felt the need to change the names of the jobs and it's not something that would be recommended as you have found out. There is a convention with the names which SQL Server constructs. Log Reader agents are named as "publisher" - "publisher database" - "agent_id". Distribution Agents are name "publisher" - "publisher database" - "publication" - "subscriber" - "agent_id". In constructing the name SQL Server allows a maximum length for each part so any longs names will get truncated but it should still be decipherable.
Hope that helps,
Mike
September 1, 2009 at 2:42 am
tnaks mike for your reply. i will go through it and check
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply