July 29, 2013 at 2:50 am
Hi
I have setup transactional replication between two sql 2008 instances and it is very slow in replicating.
We have some jobs that add thousands of records at the publisher and these take a very long time to reach the subscriber. It is not the whole database that is replicated, just a few articles but they are chunky tables. Also one table is consistently added to throughout the day, this is also not replicating well.
Are they any alternatives i could use that will help? (i.e. mirroring?)
Many Thanks
July 29, 2013 at 3:22 am
hi, I got few thoughts which can help you.
1) did you check the latency in the replication monitor.
2) did you check the database properties for auto update indexes and statistics,
3) and Analyse the purpose of the replication over mirroring in your case.
thanks.
imran.adam (7/29/2013)
HiI have setup transactional replication between two sql 2008 instances and it is very slow in replicating.
We have some jobs that add thousands of records at the publisher and these take a very long time to reach the subscriber. It is not the whole database that is replicated, just a few articles but they are chunky tables. Also one table is consistently added to throughout the day, this is also not replicating well.
Are they any alternatives i could use that will help? (i.e. mirroring?)
Many Thanks
July 30, 2013 at 3:09 pm
Worth adding a tracer token to find where the latency is.. From there you can look into areas needing the attention.
Cheers
Vultar
August 6, 2013 at 9:51 am
It sounds like you are fairly new to SQL Server replication. There is a lot to learn, and you never stop learning. We have used replication for many years, but still find new things that cause it to run slow on occasion. However, it is normally very reliable and can keep up with a high rate of change.
My advise is that you raise a case with Microsoft, saying that replication is not meeting your throughput goals. The cost of doing this is trivial compared to the benefits of what you are likely to learn. It might take a few days to get the problems resolved, but during this you should get some good advice from the people assigned to your problem.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
August 7, 2013 at 2:44 am
Thanks for all the replies, there wasnt really an issue, it was just slow as the log reader agent was trawling through the log and skipping any tables not marked for replication. See here
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply