Post reply

Queue Reader Agent

  • March 18, 2009 at 8:18 am

    #202436

    All, i have a few questions about the SQL queue reader agent and am try to research as if this is a better option for replication then what we are running now. I have two SQL server 2005 running 700 replication jobs and am running into issues were job are failing or the subscriptions are becoming inactive, so am trying to research other options for replication and am not finding much detail on the queue reader agent.

    our replication is a peer to peer transactional publication

    So my question is will going to a Queue Reader Agent eliminate the 700 SQL server agent jobs and roll this into one queue reader agent job or am i miss understanding what i have been reading so far in what they are saying is Only one instance of this agent exists to serve all the Publishers?

    Any help or better detail on this subject would be appreciated.

  • March 18, 2009 at 8:52 am

    #961969

    700 replication jobs ?

    Is all of that in just one server ?


    * Noel

  • March 18, 2009 at 4:47 pm

    #962339

    Well let me correct we have 350 publications and that shows up as 700 sql server agent jobs one for the log-reader and one for the distrubtion job if i am correct.

    And yes this is all on one server which replicates to another server across the WAN.

    Thanks

    John

  • March 19, 2009 at 10:11 am

    #962860

    Well there is only one Queue Reader but you won't get rid of the distribution agents.

    Queue reader are to propagate changes FROM Subscriber to Publishers.

    Distributors go From Publisher to subscribers!

    You definitely need to run your log-Readers on schedule instead of continuously.

    And the same goes for your distribution agents.

    This sounds like a heck of a lot for one server unless the Publications/Dbs are tiny.

    Can you consolidate ?


    * Noel

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

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