May 29, 2012 at 3:56 am
We are having some issues with a merge replication at a customer site.
We have 1 database that is published for merge replication and 6 subscribers. All subscribers PULL data every 60seconds but the agent appears to hang intermittently - although Replication Monitor reports it's running correctly.
Anyway, I wish to use tracer tokens to see what the latency is but whenever I execute the above procedure, I get the following error:
Msg 18757, Level 16, State 1, Procedure sp_replshowcmds, Line 21
Unable to execute procedure. The database is not published. Execute the procedure in a database that is published for replication.
Any ideas? I am in the publication database when executing..
June 2, 2012 at 7:19 pm
Tracer tokens only work with transactional replication.
This query is also for transactional replication, but it wouldn't take much to change it to the merge agent instead of the distribution agent:
http://www.sqlsoldier.com/wp/sqlserver/measuringtransactionalreplicationlatencywithouttracertokens
June 6, 2012 at 4:31 am
Ahh, I didn't know that.
Come to mention it, I couldn't find any examples that talked about Merge Replication and Tracer Tokens. That explains it.
Thanks anyway.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply