Last Queued Updating question....I think

When I setup my publication, I selected Queued updating. When I setup my Push, do I also need to select queued updating for the Subscriber as well?
Even though I have no intention of doing any updates on the Subscriber, I am only doing this because it was suggested as being the best option.
Please advise. I think this should be it for questions on this topic then....I hope.
JLS,
yes - this needs to be selected if your aim is a simple failover methodology and it'll only be available if you select the advanced options. If you don't select it then you end up with a non-updatable subscriber, which maybe isn't your main interest, but the implication of this is that you won't have automatic range management of identities on the subscriber and also no simple method of failing back to the publisher if necessary.
HTH,
Paul Ibison

large MSReplication_queue table?

Hi All,
I have a queued update Transactional Replication with a push subscription
from the publisher. The subscriber's database size is nearly double of the
published database on the publisher side. Further investigation found that
the MsReplication_queue has some old data (about last 6 months). Is there any
agent that is supposed to clean the table? Or I have to clean the table
manually? Can someone help me plz?
Thanks in advance,
has the distribution agent run recently? How about the distribution clean up
agent?
"Franky" <Franky@.discussions.microsoft.com> wrote in message
news:BC9B7884-A1CD-4E59-BFB8-9917F35F64E4@.microsoft.com...
> Hi All,
> I have a queued update Transactional Replication with a push subscription
> from the publisher. The subscriber's database size is nearly double of the
> published database on the publisher side. Further investigation found that
> the MsReplication_queue has some old data (about last 6 months). Is there
> any
> agent that is supposed to clean the table? Or I have to clean the table
> manually? Can someone help me plz?
> Thanks in advance,
|||Hilary,
The distribution agent and distribution clean up agent (both on the
Publisher side) are running and the data is being pushed from the Publisher
to the Subscriber. The Subscriber is a DR site and sometimes it runs
production traffic. The MSReplication_queue table is on the Subscriber side.
Does the distribution cleanup agent on the Publisher clean up the
MSReplication_queue table on the Subscriber side? What side effects if I
manually delete entries in the MSReplication_queue since they are old data.
Thanks,
"Hilary Cotter" wrote:

> has the distribution agent run recently? How about the distribution clean up
> agent?
> "Franky" <Franky@.discussions.microsoft.com> wrote in message
> news:BC9B7884-A1CD-4E59-BFB8-9917F35F64E4@.microsoft.com...
>
>