Subject | Re: Firebird improvement suggestion |
---|---|
Author | t_j_haynes |
Post date | 2005-06-22T15:48:16Z |
--- In Firebird-Architect@yahoogroups.com, "Dimitry Sibiryakov"
<SD@t...> wrote:
around triggers or table comparison. These generally cost money and
have lots of complex set-up options, which would be fine if I wanted
to replicate a subset of data or feed multiple databases into one.
Hoever, I just want to duplicate the entire database to another
machine and keep it up to date for reasons of resilience. Surely a
mechanism which works at the database file block update level
(working within the database core engine) has to be a LOT faster and
simpler than any bolt-on!
Cheers,
Tim
<SD@t...> wrote:
> On 22 Jun 2005 at 9:15, t_j_haynes wrote:in
>
> >On the ideas of taking regular hourly backups, I was thinking more
> >terms of a standby database which would perhaps be a minute or twowould
> >behind, not an hour! Taking an incremental backup every minute
> >have to be a big drain on performance and rather unmanageable.True, there are bolt-on replication solutions out there, mostly built
>
> If I were you, I would think about multi-tier application with
> automated crash recovery or replication...
> --
> SY, Dimitry Sibiryakov.
around triggers or table comparison. These generally cost money and
have lots of complex set-up options, which would be fine if I wanted
to replicate a subset of data or feed multiple databases into one.
Hoever, I just want to duplicate the entire database to another
machine and keep it up to date for reasons of resilience. Surely a
mechanism which works at the database file block update level
(working within the database core engine) has to be a LOT faster and
simpler than any bolt-on!
Cheers,
Tim