Mssql Replication(step 4)

Bước VI. Giám sát việc xuất bản và đăng ký phần này của bài viết mô tả làm thế nào để sử dụng Replication Monitor theo dõi việc xuất bản và đăng ký bạn tạo ra. 1. Trong SQL Server Management Studio, mở rộng Replication. 2. Mở rộng các ấn phẩm địa phương. 3. Nhấp chuột phải vào thư mục các ấn phẩm địa phương và sau đó nhấp vào Launch Replication Monitor.Click vào đây để xem ảnh nhỏ.
Nội dung trích xuất từ tài liệu:
Mssql Replication(step 4)Step VI. Monitoring the Publication and SubscriptionThis section of the article describes how to use Replication Monitor to monitor thepublication and subscription you created.1. In SQL Server Management Studio, expand Replication.2. Expand Local Publications.3. Right-click the Local Publications folder and then click Launch Replication Monitor. Click this bar to view the small image.Figure 56. Starting Replication MonitorSubscription status is displayed on the All Subscriptions tab in the right pane. Thetime it took for data to replicate from the Oracle Publisher to the Subscriber is listedin the Latency column, and a relative rating of this performance is listed in thePerformance column. Because initial snapshots take more time to generate anddeliver than incremental changes, the initial latency is typically much greater thanthe latency for incremental changes. Click this bar to view the small image.Figure 57. Viewing subscription status in Replication Monitor4.Latency between the Publisher and Subscriber is calculated by measuring twointervals in replication processing:a. The time that is required from when a change is made at the Publisher until theLog Reader Agent delivers the change to the distribution database.b. The time that is required for the Distribution Agent to deliver the change from thedistribution database to the subscription database.5.To view the details of the replication processing involved in these steps, you candouble-click the subscription row in the right pane. The Distributor To SubscriberHistory tab shows the history for the selected Distribution Agent. Click this bar to view the small image.Figure 58. Viewing Distribution Agent history6.The Publisher To Distributor History tab displays the history for the Log ReaderAgent. Click this bar to view the small image.Figure 59. Viewing Log Reader Agent history7.The Undistributed Commands tab displays information about the number ofcommands in the distribution database that have not been delivered to the selectedSubscriber, and the estimated time to deliver those commands.Close the dialog box and return to the main Replication Monitor interface. Click this bar to view the small image.Figure 60. Viewing the number of commands in the distribution database8.Tracer tokens are used to diagnose the current performance of transactionalreplication. A token, which is a small amount of data, is written to the transaction logof the publication database, marked as if it were a typical replicated transaction, andthen sent through the system. The elapsed time is then measured.You can create and monitor tracer tokens by using Replication Monitor.a. In Replication Monitor, click the Tracer Tokens tab.b. Click Insert Tracer. Click this bar to view the small image.Figure 61. Adding a tracer token for a publication9.After a short time, Replication Monitor displays three numbers as indicators oftransactional replication performance: the time to replicate the tracer token from thepublication database to the distribution database; the time to replicate the tracertoken from the distribution database to the subscription database; and the totalelapsed time. If one of the agents is stopped and the tracer cannot be replicated,Replication Monitor displays Pending until the agent is restarted.a. Verify that a value is displayed in the Total Latency column.b. Close Replication Monitor. Click this bar to view the small image.Figure 62. Viewing elapsed time for the tracer token