Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Transactional Replication Sloooow Expand / Collapse
Author
Message
Posted Monday, July 29, 2013 2:50 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, June 5, 2014 2:13 AM
Points: 25, Visits: 105
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
Post #1478483
Posted Monday, July 29, 2013 3:22 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, July 18, 2014 3:52 AM
Points: 9, Visits: 89
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
Post #1478494
Posted Tuesday, July 30, 2013 3:09 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: 2 days ago @ 9:21 AM
Points: 234, Visits: 1,085
Worth adding a tracer token to find where the latency is.. From there you can look into areas needing the attention.

Cheers

Vultar
Post #1479179
Posted Tuesday, August 6, 2013 9:51 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 10:28 AM
Points: 2,859, Visits: 3,188
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 2014, 2012, 2008 R2, 2008 and 2005. 28 July 2014: now over 30,000 downloads.
Disclaimer: All information provided is a personal opinion that may not match reality.
Concept: "Pizza Apartheid" - the discrimination that separates those who earn enough in one day to buy a pizza if they want one, from those who can not.
Post #1481415
Posted Wednesday, August 7, 2013 2:44 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, June 5, 2014 2:13 AM
Points: 25, Visits: 105
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
Post #1481728
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse