January 20, 2014 at 9:07 am
Hi.
We have recently set up a replicated database that uses Transaction Replication with 2 identical Subscribers. The main bulk of data is added/updated in the Publisher overnight. There appears to be more transactions in the log than we were expecting.
Is it possible to report on or capture the transactions that the log reader detects and passes to the Distributor. This will help us understand which tables are receiving the bulk of the Insert, Updates and Deletes and help us determine if there is an error in our code that generates these transactions.
There are at lease 1500 Insert, Update and Delete stored procedures, so to caputure the data at that level is not really realistic.
Thanks, Tim.
January 21, 2014 at 8:52 am
As you have probably found out already, the transactions to be sent to a subscriber in the distribution database are kept in a binary format. It may be possible to decode them, but I don't know how to do that offhand. a better way would be to set up a profiler trace to monitor what activity is going on on the publisher that is generating the unexpected traffic. There are a number of articles on how to set up a server side trace.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply