Monday, March 26, 2012
Rename SQL Agent Jobs for Replication
The names that are assigned to these jobs are vague and cryptic at best. I
went ahead and renamed them to something a little more telling. I noe get the
following error:
TITLE: Replication Monitor
Replication Monitor could not start the job
'100602-DB4-NavigatorSuiteReplicate-NavigatorSuiteReplicate_TPA3-28'.
The specified @.job_name
('100602-DB4-NavigatorSuiteReplicate-NavigatorSuiteReplicate_TPA3-28') does
not exist. (Microsoft SQL Server, Error: 14262)
Is there some other place I need to update the names of these jobs? Or do I
just need to go back and name them what they were before?
Thanks!
have a look at MSsnapshot_agents
MSlogreader_agents
MSdistribution_agents
MSmerge_agents
MSqreader_agents
in the distribution database,
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
news:D4EE3A17-FEE2-40C4-809F-9AD799E52E27@.microsoft.com...
>I have SEVERAL replication publications/subscriptions on a server.
> The names that are assigned to these jobs are vague and cryptic at best. I
> went ahead and renamed them to something a little more telling. I noe get
> the
> following error:
>
> TITLE: Replication Monitor
> --
> Replication Monitor could not start the job
> '100602-DB4-NavigatorSuiteReplicate-NavigatorSuiteReplicate_TPA3-28'.
> The specified @.job_name
> ('100602-DB4-NavigatorSuiteReplicate-NavigatorSuiteReplicate_TPA3-28')
> does
> not exist. (Microsoft SQL Server, Error: 14262)
> Is there some other place I need to update the names of these jobs? Or do
> I
> just need to go back and name them what they were before?
> Thanks!
>
sql
Saturday, February 25, 2012
removing deactivated subscriptions
Hi
We are using merge replication - how do we remove deactivated subscriptions from the replication monitor at the publisher. These are anonymous HTTPS subscribers....
Thanks
Bruce
I use this stored procedure which runs against the distribution database:
CREATE PROCEDURE [dbo].[usp_DeleteMergeAgentSessions]
@.Publication [nvarchar](50),
@.Subscriber [nvarchar](50),
@.Database [nvarchar](50) = NULL
AS
SET NOCOUNT ON
DELETE FROM [msmerge_sessions] WHERE [agent_id] IN (SELECT [id] FROM [msmerge_agents] WHERE [publication] = @.Publication AND [subscriber_name] = @.Subscriber AND (@.Database IS NULL OR @.Database = [subscriber_db]))
DELETE FROM [msmerge_agents] WHERE [publication] = @.Publication AND [subscriber_name] = @.Subscriber AND (@.Database IS NULL OR @.Database = [subscriber_db])