INSERT #MSrepl_commands(article_id,publisher_database_id,xact_seqno) The following script (adapted from the MSDistribution_status view) might be helpful - note that it will take a long time depending on the amount of data in the MSrepl_commands and the MSDistribution_History tables:ĬREATE TABLE #MSrepl_commands(article_id int NOT NULL,publisher_database_id int NOT NULL,ĬREATE TABLE #MSSubscriptions(agent_id int NOT NULL, article_id int NOT NULL, publisher_database_id int NOT NULL,ĬREATE TABLE #MSDistHistory(agent_id int NOT NULL, maxseq varbinary(16) NOT NULL) The information and scripts provided there might be helpful in figuring out where the data is. This link has some good info on how to troubleshoot distribution agent performance (scroll to the section "Distribution Agent reader latency" and "Distribution agent writer latency"). This will provide the # of rows that have come into the distribution DB from the publisher. SELECT SUM(rows) FROM sys.partitions WHERE object_id = OBJECT_ID('msrepl_commands') What is the result of this on the distribution DB: What happens when you open replication monitory, double click on your subscription and click on the "Undistributed Commands" tab? This tab will take some time to populate if there is a lot of data getting replicated - do you see any values here? So - there's no errors in replication monitor or in the distribution agent job history but the data doesn't seem to be flowing into the subscriber. delivery_latency columns over time to see how the distribution agent is processing dataĪre there any errors in replication monitor or in the distributor/log reader jobs? check on the comments, delivered_transactions, delivered_commands, delivery_rate and average_commands, delivery_rate and delivery_latency over time to see how the check on the comments, delivered_transactions, delivered_commands, Run the following queries in your distribution server in the context of the distribution DB to check on what is happening in the log reader and distributor agents: What kind of replication do you have setup? Transactional or snapshot or merge or P2P?Īssuming this is transactional replication:Īre you seeing the "No replicated transactions are available" for the log reader agent or the distribution agent? Upload screen captures by build-in FTP engine.Ĭurrently, it is available for free download.: Realized after just posting this that this is the SQL 7,2000 forum - the queries below run in my SQL 2008 environemnt and I don't know if they will work in 7 or 2000.Send screen captures by build-in e-mail (supports Exchange Server). Send screen captures to image editing program.Automatically save screen captures and filename generation.Supports multiple monitors and Dualview.Include mouse pointer and play sound on capture.Run minimized or minimize to System Tray area. Save in BMP, GIF, JPEG, PCX, PNG, PSD, and TIFF formats.Global hotkeys to instantly activate screen capturing.Options to specify output destination (file, editor, clipboard, printer, e-mail).Capture screen, window, rectangular area.Other features of SnapShot include global hotkeys, automatically save screen captures, auto filename generated and support external editors. Apart of that, it also allows the users to send the screen shot as attachment to email or upload via FTP. SnapShot is a lightweight, yet powerful, full-featured screen capture tool that allows the users to grab desktop, windows or any part of the screen and save it as image format such as JPG or PNG or send it directly to the users favorite editor for further editing.
0 Comments
Leave a Reply. |