Merge Replication Subscription Detail Window: Initialization phase periodically takes orders of magnitude longer to run



merge replication between 2 geographically dispersed sites. 
single table publication.
active monitoring of replication status checking last time merge agent completed
periodically (typically once or twice day) encounter monitor alerts indicating subscriber has not been updated.
checking merge subscription detail window shows synchronisation, takes less 10 seconds process 100-200 dml actions has taken 10-12 minutes, initialization phase accounting 100% of total.
research (see http://www.yaldex.com/sql_server_tutorial_3/ch12lev1sec4.html) suggests initialization phase involves startup of merge agent , establishes connection publisher , subscriber. 
there no indication of connection failures or bottlenecks between publisher , subscriber. 

welcome troubleshooting guidance determine causing significant drop in synchronisation performance. although short-lived can result in false alarms our on call support team @ 3:00 am.

query msmerge_history see detailed information each synschrnization, can session_id msmerge_sessions.  these tables in publisher


convert dts ssis | document ssis | 30+ ssis tasks | real-time ssis monitoring | quick starts | bi blitz



SQL Server  >  SQL Server Replication



Comments

Popular posts from this blog

Conditional formatting a graph vertical axis in SSRS 2012 charts

Register with Power BI failed

SQL server replication error Cannot find the dbo or user defined function........