March 27, 2019 at 9:14 am
Hello!
I am getting these messages on replication monitor in certain time of the day (usually at night
Approximately 500000 log records have been scanned in pass # 4, 0 of which were marked for replication. (publisher to distributor history), is this due to blocking?
Does it mean during this time it was not replicated?
What are the troubleshooting steps for this to resolve it?
Thank you.
March 27, 2019 at 10:58 am
PJ_SQL - Wednesday, March 27, 2019 9:14 AMHello!
I am getting these messages on replication monitor in certain time of the day (usually at night
Approximately 500000 log records have been scanned in pass # 4, 0 of which were marked for replication. (publisher to distributor history), is this due to blocking?
Does it mean during this time it was not replicated?What are the troubleshooting steps for this to resolve it?
Thank you.
It's a message from regular processing which indicates that the log reader has to go through a lot of log records of non-replicated transactions. Could be index maintenance or some type of import, update process that doesn't involve tables in the publication. What issues is it causing?
Sue
March 27, 2019 at 11:42 am
We do have couple of jobs that run during that timeframe other than maintenance jobs, it could be because of that.
It is not causing any issues but wanted to get some information on what those were implying.
March 27, 2019 at 11:49 am
PJ_SQL - Wednesday, March 27, 2019 11:41 AMWe do have couple of jobs that run during that timeframe other than maintenance jobs, it could be because of that.
It is not causing any issues but wanted to get some information on what those were implying.
The LogScanThreshold setting defaults to 500000 so the log reader is going to scan that many records at a time. When you have 0 marked for replication, it just means the log reader read 500000 records and none of those records were for replication. That's all.
Sue
March 27, 2019 at 11:53 am
Thank you for the explanation.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply