Iindex rebuild's impact on transaction replication
During an index rebuilds with full recovery mode, transaction log entries will be created (normal).
If I switch to bulk logged recovery, will:
- less data be replicated ?
- less mining of the transaction log occur ?
What I'm seeing after an index maintenance where some large table indexes are rebuild, replication will report "Approximately 5000000 records have been scanned in pass #4, 0 of which were marked for replication".
This concerns me in that "real" data changes are being slowed down in getting to the subscriber.
Thank You
Bruno
Who is Participating?
Experts Exchange Solution brought to you by
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
Yes, Starting from SQL Server 2008 Index Rebuild activities are completely logged either it is rebuild WITH ONLINE = ON/OFF when Recovery model is set to FULL. This will cause slowness to Replication.
>> If I switch to bulk logged recovery, will: - less data be replicated ?- less mining of the transaction log occur ?
Yes, it will definitely help reduce the log file size increase and will help reduce the Replication latency.
FYI, we have implemented several years ago after SQL Server 2008 came..
More info with respect to this FYI..
https://support.microsoft.com/en-my/help/2407439/you-may-notice-an-increased-transaction-log-sizes-in-sql-server-2008-a
Experts Exchange Solution brought to you by
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trialIt's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
From novice to tech pro — start learning today.
Experts Exchange Solution brought to you by
Is there an actual proof that this is happening while indexes are rebuilt? Do you have enterprise Edition so you can rebuild indexes with ONLINE=ON? If yes then I believe only the Log reader agent does more work and as long as you don't see any queue in the Distribution agent because of this there should be not a delay in delivering transactions to the subscriber. You can check that under the "Undistributed Commands" tab in the Replication Monitor on the particular Subscription(s) where your concern is.