Monitoring Replication (SQL Server Compact)
You can monitor Subscribers on the computer that is running Microsoft SQL Server by using the Replication Monitor. You can also use the SQL Server Compact 3.5 Server Agent statistics page to provide detailed information about the agent. For more information, see "Monitoring Replication with Replication Monitor" in the SQL Server Books Online.
Using Replication Monitor
You use Replication Monitor to examine the status of subscriptions. In SQL Server 2005 and later versions, the Replication Monitor is a separate tool. It can be accessed through SQL Server Management Studio.
Note
Any time an automatic resynchronization occurs, it is considered a separate synchronization to SQL Server. Therefore, SQL Replication Monitor will have a unique entry for each synchronization. On the SQL Server Compact 3.5 subscriber, the values of the PublisherChanges, SubscriberChanges, PublisherConflicts, and SubscriberConflicts properties of the SqlCeReplication class is summed up and the total of all synchronizations is provided on the return of the last synchronization.
For more information about opening Replication Monitor, see How to: Start the Replication Monitor.
Naming of SQL Server Compact 3.5 Clients in Replication Monitor
Unlike SQL Server Subscribers on a network, there is no guarantee that SQL Server Compact 3.5 Subscribers will have unique names. Therefore, to display individual clients in the Replication Monitor, a unique name is created based on the subscriber GUID of each device.
- Publisher is SQL Server 2005 or SQL Server 2008
For SQL Server Compact 3.5 Subscribers listed in the Replication Monitor, the subscription column is formatted as subscriber – replnickname:db_name. The replnickname can be used to find the subscriber row in the sysmergesubscriptions system table in the Publisher database.
See Also
Tasks
Using SQL Server Compact Server Agent Statistics to Troubleshoot Connectivity
Using SQL Server Compact Server 3.5 Agent Diagnostics to Troubleshoot Connectivity