Re: Transactional Publication with updatable subscriptions

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: "Paul Ibison" <Paul.Ibison@xxxxxxxxxxxxx>
Date: Fri, 27 Oct 2006 14:41:13 +0100

To add to the previous comments, if you want to have offline access
(autonomy) then the choice is between queued updating subscribers (QUS) and
merge replication. QUS will be generally more efficient, but won't work for
BLOB datatypes and have a more restricted set of conflict resolvers than
merge.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

.

Prev by Date: Re: The merge process failed
Next by Date: Re: Not for Replication in merge replication - help needed
Previous by thread: Re: Transactional Publication with updatable subscriptions
Next by thread: log scan number
Index(es):
- Date
- Thread

Relevant Pages

Re: Warm standby FUBAR
... I have previously used queued updating subscribers for this type of ... scenario, so had not seen your issue before. ... DBCC CHECKIDENT doesn't reseed ... Suggest you move towards QUS which will prevent this ...
(microsoft.public.sqlserver.replication)
Re: Warm standby FUBAR
... I have used the Wizard to create these, ... seen an option for queued updating subscribers, ... >I have previously used queued updating subscribers (QUS) ... >with the NOT FOR REPLICATION clause (in either the CREATE ...
(microsoft.public.sqlserver.replication)