February 16, 2009 at 7:48 am
We have configured transactional replication between our Databases running in two different SQL servers. But the publisher and distributor is running in same SQL server where the slowness is noticed. Publisher is getting queued up around 30000+ records and distributor is receiving it very slowly. please let us know what could be the problem.
February 16, 2009 at 8:52 am
Not very much information provided, so I'll talk in some generalities...if your server is acting as both the publisher and the distributor you are likely to run into IO contention issues. When a write occurs on your published database it's recorded in the transaction log. The log reader agent (an out of process executable) then needs to read the log and write each transaction that applies to replication to the distribution database. The distribution agent (another out of process executable) reads it from the distribution database and sends the change to the subscriber. Meanwhile more writes are taking place back in your published database. It's pretty clear to see how this can cause your system to slow down, especially as the volume of data that changes on the published database gets larger.
Best practices dictate that (especially for high volume replication) you use a separate, dedicated distributor.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply