Renaming replication jobs
In SQL 2005 I am renaming the jobs listed under SQL server agent that launch all of the replication tasks. Problem I'm running into is when I do this I am not able to access these jobs from the Replication Monitor. I right click the subscription and select View Details. Then select Action -> Merge Agent Job Properties and get an error stating that the job does not exist on the server. However if I rename the job back to what it was originally and repeat this process it can find the job just fine.
Is there a table somewhere in the master database that I need to change some entries for? Is there a prefered method for renaming the replication jobs??
From http://www.developmentnow.com/g/114_2005_3_0_0_0/sqlserver-replication.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com
.
Relevant Pages
- Re: Replication maintenance jobs
... Looking for a SQL Server replication book? ... other jobs will show up in the jobs folder in SQL 2005. ... Log Reader agent and the distribution agent jobs. ...
(microsoft.public.sqlserver.replication) - Re: Replication maintenance jobs
... Looking for a SQL Server replication book?http://www.nwsu.com/0974973602.html ... other jobs will show up in the jobs folder in SQL 2005. ... agent, Log Reader agent and the distribution agent jobs. ...
(microsoft.public.sqlserver.replication) - Re: Copied database, no longer can retrieve new entries
... replication and my only involvement was on a project where one of the three ... new jobs, modify pending jobs, modify running jobs. ... The form opens without the information. ...
(microsoft.public.access.forms) - Generated Replication Script creates duplicate merge jobs
... I have a running SQL Server 2000 merge replication with 40 push subscribers. ... running two times a day with every subscriber. ... I have generated a script for the replication including the scripting the ... I have done many changes to the merge jobs (dialing out and hanging up the ...
(microsoft.public.sqlserver.replication) - Re: Synchronization of Primary Sites not working
... it seems one of the jobs already finished. ... However, I'm still facing replication issues and a backlog of more than 5,000 ... "Kim Oppalfens" wrote: ... > that would obviously mean that the package won't get replicated. ...
(microsoft.public.sms.admin) |
|
