Delay In replication

Question

Delay In replication

Patrick Doonan

SSC Enthusiast

Points: 109
More actions
July 4, 2005 at 9:09 am

#90132

I have set up Transactional Replication running contiuously. Every things seems perfect but if I make a change to a table, there is a long delay of 30 mins before it appears in the subscribing db. Does anyone know how I can troubleshoot this ?

Cheers Pat

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

G.R.Prithiviraj Kulasingham SSCarpal Tunnel Points: 4105 More actions · Answer 1

basically SQL Server creates a job to run log reader as and when agent starts. If that is created properly you are fine. (Delays are possible when the publisher, distributer and subscriber are physically seperated; delays also occur when transaction volumn is high)

otherwise you can schedule the job to work differently.

Cheers,
Prithiviraj Kulasingham

http://preethiviraj.blogspot.com/

noeld SSC Guru Points: 96590 More actions · Answer 2

in the "agents profile" it is possible to configure how fast do you want the pooling to occur

* Noel

noroz Newbie Points: 9 More actions · Answer 3

What /Where is "agents profile"? I am having similar issue with replication. Thanks.

GVD SSC Rookie Points: 25 More actions · Answer 4

here it takes around 15sec before it appears in the subscriber database. i'm using merge replication.

i was looking at the job scheduler, but i don't see there where the interval is configured.

are you sure it's in the job scheduler? (or isn't that the same as the "agents profile?"), because when i look at its logs, i never see a log when the replication occurred.