May 10, 2009 at 8:35 pm
Hi,
I am able to replicate 75 MB of data in 25 min, where as 350 MB of data is taking more than 10 hours in republication scenario. Could you please let me know what the bottleneck is and solution for that?
Thank you,
Kiran
May 10, 2009 at 9:59 pm
You would need to examine how quickly things are being written to the distribution db, as well as then to the subscribed. I'd enable a tracer token and see how long it takes for things to get moved.
May 13, 2009 at 12:14 pm
You are probably having hardware setup issues. I replicate a lot more than that in one hour.
* Noel
May 14, 2009 at 12:38 am
Surely, this is not a H/W issue...
I am using a republisher scenario. From Publisher to republisher the data is moving with in no time. But it never reached from Republisher to Subscribers (For sizes greater than say 300 MB). It is always getting timed out (Query timeout = 1800sec). Not sure which parameter I need to tune for getting the data to subscriber. I appreciate any guidance...
May 15, 2009 at 11:28 am
kiran_thota_kumar (5/14/2009)
Surely, this is not a H/W issue...I am using a republisher scenario. From Publisher to republisher the data is moving with in no time. But it never reached from Republisher to Subscribers (For sizes greater than say 300 MB). It is always getting timed out (Query timeout = 1800sec). Not sure which parameter I need to tune for getting the data to subscriber. I appreciate any guidance...
Look for blocking/locking processes on the "Subscribers" or on the "Republisher".
* Noel
May 19, 2009 at 10:44 am
Yup, Better to check deadlocks in process @ subscriber level.
--> Check uncommited trans on subscriber end using repln monitor
--> I faced same issue but mine was little bit different i will explain the scenario.
One view was not published due to articel which does not have pkey in that table. we are doing DML operations using one sp via view.
that was the case we found transactions are delayed and that we easily got replication monitor.
-
May 20, 2009 at 11:41 am
For time out problems, try changing the Transaction Time-out setting.
In Management Studio connected to the subscriber, go to Tools -> Options -> Designers. Your 'Transaction Time-out After:' setting is probably set at 1800 sec or 30 minutes - your replication transaction needs more time to run and will timeout before completion.
June 1, 2009 at 12:33 am
Thanks every one...
I think I have figured out the issue...
Large data is going in a single transaction to the publisher database. Hence the issue...
-Kiran
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply