Hallo!
Are deferred updates possible in MSSQL2k?
I don't found anything in BOL.
Thanks Thomas
Would need some more info as to what you require, but outside of SQL Server
you can use message queuing to defer the update. In SQL Server replication
we have queued updatable subscribers, where the queue can be a sql table or
a MSMQ system. At a more simplistic level, all replication involves deferred
updates to the subscriber, as there is no zero latency technique. The degree
of deferral can be controlled by editing the agent's profile and by altering
the agent schedule.
Regards,
Paul Ibison
|||On Thu, 13 May 2004 09:08:53 +0100, "Paul Ibison"
<Paul.Ibison@.Pygmalion.Com> wrote:
>Would need some more info as to what you require, but outside of SQL Server
>you can use message queuing to defer the update. In SQL Server replication
>we have queued updatable subscribers, where the queue can be a sql table or
>a MSMQ system. At a more simplistic level, all replication involves deferred
>updates to the subscriber, as there is no zero latency technique. The degree
>of deferral can be controlled by editing the agent's profile and by altering
>the agent schedule.
>Regards,
>Paul Ibison
>
In some circumstances in MSSQL 6.5 an UPDATE will changed in
DELETE/INSERT-pair. In a bidirectional replication scenario with
vertical partitions and a special application the need of custom sp
triggers was required.
After 5 years of successful bidirectional replication I will change to
MSSQL2k.
I would know, if this in MSSQL2k similar?
If there are no deferred updates, then I needn't custom triggers or
dynamic filters (new feature in 2k).
thanks in advance
|||Thomas,
the same problem still exists in SQL 2000, although for singleton updates
you can use a trace flag to apply an update on the subscriber
(http://support.microsoft.com/default...microsoft.com
:80/support/kb/articles/q302/3/41.ASP&NoWebContent=1)
HTH,
Paul Ibison
No comments:
Post a Comment