Replication - one subscriber up to date, the other hours behind

  • Hi have a server acting as publisher/distrubutor.

    One subscriber ( actually hosted in AWS and low spec ) is up to date no problems

    Another subscriber ( actually hosted in same building as publisher and very high spec is well behind )

    I've ran profiler against both servers and looked at execution time of various sp_ins and sp_upd routines and both seem to execute straight away so can't understand why the second server is so behind?

  • Check the definition of the Distibution agent for each of the subscribers - perhaps one is continuous and the other is based on a schedule

Viewing 2 posts - 1 through 1 (of 1 total)

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