Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Transactional Replication Sloooow


Transactional Replication Sloooow

Author
Message
imran.adam
imran.adam
SSC Rookie
SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)

Group: General Forum Members
Points: 26 Visits: 115
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
katukuri.sqldba
katukuri.sqldba
Grasshopper
Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)

Group: General Forum Members
Points: 13 Visits: 111
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)
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

vultar
vultar
Old Hand
Old Hand (310 reputation)Old Hand (310 reputation)Old Hand (310 reputation)Old Hand (310 reputation)Old Hand (310 reputation)Old Hand (310 reputation)Old Hand (310 reputation)Old Hand (310 reputation)

Group: General Forum Members
Points: 310 Visits: 1213
Worth adding a tracer token to find where the latency is.. From there you can look into areas needing the attention.

Cheers

Vultar
EdVassie
EdVassie
Hall of Fame
Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)Hall of Fame (3.2K reputation)

Group: General Forum Members
Points: 3154 Visits: 3821
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: SQL Server FineBuild 1-click install and best practice configuration of SQL Server 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005. 1 Dec 2016: now over 39,000 downloads.
Disclaimer: All information provided is a personal opinion that may not match reality.
Quote: "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
imran.adam
imran.adam
SSC Rookie
SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)SSC Rookie (26 reputation)

Group: General Forum Members
Points: 26 Visits: 115
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

http://social.msdn.microsoft.com/Forums/sqlserver/en-US/2c8549dd-a35f-4ccb-8e54-2de45fa06687/transactional-replication-performance-critical-publisher-to-distributor-very-slow
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search