Queued updatable subscriber...

can someone explain the proper usage of a queued updatable subscriber in a
transactional replication scheme? in other words, what are the ways in which
you can tell the subscriber to empty the queue of outstanding transactions
that are to be applied back at the publisher (keep in mind, although maybe
not relevent, no inserts occur at the subscriber, only udpates). is it just
as easy as scheduling the job that gets created for the queue reader agent?
thanks all!
Yes - it's just a job. You can also use sp_replqueuemonitor to read the
MSreplication_queue table.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

Queue Reader Agent Failed

Hi,
We have set replication between two servers.In subscriber if i update any
row, the transaction is in Msreplication_queue Table.But when it try to push
to publisher it throws a error called "Invalid cursor state". I don't know
where it is going wrong.
what could be the cause of this error.
Thanks in Advance,
Rajesh
Do you have sp4 installed? There was a bug prior to sp4 which gave this
message (http://support.microsoft.com/kb/831997/EN-US/).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Hi
Thanks, Currently we have installed SP3.We have to install it.
"Paul Ibison" wrote:

> Do you have sp4 installed? There was a bug prior to sp4 which gave this
> message (http://support.microsoft.com/kb/831997/EN-US/).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>

Queue Reader Aborting

I am using transactional replication with queued updating. The publisher is
located in Norway, with a single subscriber in the US. The Queue Reader
Agent starts successfully, and transactions originating on either side are
properly replicated. However, the Queue Reader agent eventually shuts down
with the message "Queue Reader Aborting". When I check the session log, I
find occurrences of the error: "Server does not exist or access denied"
throughout the entire time the agent runs. Right before the agent actually
shuts down, I get the following three errors:
"Communication link failure"
"Error in caching messages from SQL Queue"
"Queue Reader Aborting"
After the queue reader fails, it does not restart automatically - it
requires manual intervention. We are aware that the connection is sporatic,
and can accept the queue building up on both sides. Is the communication
link failure a result of some threshold being reached? Can that threshold be
removed? If not, is there a way to have the queue reader agent automatically
restart?
Hi,
I have a replication scenario similar to yours, and my queue reader also
periodically aborts with those same messages. I don't have any insight yet
as to what causes it, but at least now you know you're not alone!
Ed
"Daniel Inman" <DanielInman@.discussions.microsoft.com> wrote in message
news:914EA9FB-1554-45F7-BC84-47E44D56161C@.microsoft.com...
> I am using transactional replication with queued updating. The publisher
is
> located in Norway, with a single subscriber in the US. The Queue Reader
> Agent starts successfully, and transactions originating on either side are
> properly replicated. However, the Queue Reader agent eventually shuts
down
> with the message "Queue Reader Aborting". When I check the session log, I
> find occurrences of the error: "Server does not exist or access denied"
> throughout the entire time the agent runs. Right before the agent
actually
> shuts down, I get the following three errors:
> "Communication link failure"
> "Error in caching messages from SQL Queue"
> "Queue Reader Aborting"
> After the queue reader fails, it does not restart automatically - it
> requires manual intervention. We are aware that the connection is
sporatic,
> and can accept the queue building up on both sides. Is the communication
> link failure a result of some threshold being reached? Can that threshold
be
> removed? If not, is there a way to have the queue reader agent
automatically
> restart?