On 6/13/16 9:59 AM, Davis, Daniel (NIH/NLM) [C] wrote:
> I figured out how I could make it work, anyway. Such "replication on a
> schedule" is not usually the way that database replication works, and I'm not
> sure I should try to make it work this way.
When using Replication (be it Single-S
> via scripts. I should probably rewack my stored procedures and systems
> architecture so that my update jobs run efficiently with transaction
> isolation.
>
> From: Davis, Daniel (NIH/NLM) [C]
> Sent: Friday, June 10, 2016 10:55 AM
> To: virtuoso-users
> Subject: [V
s. I should probably rewack my stored procedures and systems
> architecture so that my update jobs run efficiently with transaction
> isolation.
>
> From: Davis, Daniel (NIH/NLM) [C]
> Sent: Friday, June 10, 2016 10:55 AM
> To: virtuoso-users
> Subject: [Virtuoso-users] Replicat
I should probably rewack my stored procedures and systems
architecture so that my update jobs run efficiently with transaction isolation.
From: Davis, Daniel (NIH/NLM) [C]
Sent: Friday, June 10, 2016 10:55 AM
To: virtuoso-users
Subject: [Virtuoso-users] Replication on a schedule
Hi, does anyone out
Hi, does anyone out there with the Cluster edition of Virtuoso replicate on a
schedule rather than as deltas are flushed? Is this desirable?
The issue is that in a star topology, replication represents an increased risk
of the replicant failing. It may therefore be better to replicate only dur
