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