Found that the database was wrongly set to AUTO_CLOSE ON. Reset it to OFF seems fixed the problem.

Changed the log reader agent profile to PollingInterval = 1 and ReadBatchSize = 5000.

Restarted log reader agent.

But seems that does not help.

Delivery rate is still always 1.

From replication monitor, the...

Distribution is running at same server as Publisher.

The result of EXEC sp_MSenum_logreader @name = '%',@show_distdb =0 shows

comments: 500 transaction(s) with 599 command(s) were delivered.

delivery time: 82228516

delivered transactions: 116917

delivered commands: 132850

average_commands:...

Both MAIN-DB and REP-DB are in the same LAN. Network latency should not be the problem.

I have set the subscriber synchronization schedule to be "run continuously".

I checked at the subscriber (REP-DB). When I click "View synchronization status" at the subscription, it shows "Synchronization in progress".

I also checked one table where the data is continuously growing.

At...

Found my situation is exactly the same as described here: http://www.sqlservercentral.com/Forums/Topic348837-291-1.aspx

This one is driving me crazy...

We are using Transactional Replication with the subscribers initialized from a backup (no snapshot). ...

How to add the new article to the existing subscription?

I am using pull subscriptions, I tried to run sp_refreshsubscriptions at the publisher, but it does not help.

Running the snapshot agent...

Strange.

I added a RETURN at the top of all triggers to prevent them from running. Then I reinitialized the subscription, but the same error still happens.

I even tried to delete...