| Subject | RE: [firebird-support] Firebird/ASA/Clarion |
|---|---|
| Author | Johan van Zyl |
| Post date | 2004-04-01T16:38:24Z |
From NewsServer: discuss.softvelocity.com
News Group: comp.lang.clarion
On 1 Apr 2004 08:09:57 -0500, "Jack T."
<71045.3122_No_Spam_Here@...> wrote:
After mentioning the IBLogFile "solution" in a post last night I
downloaded it and, after a cursory evaluation, agree that it is
anything but an ideal solution for the scenario(s) you have proposed.
The massive bloat to the main db for complete logging writes it off my
list immediately.
However (and here I'm echoing some of what Bruce has said in his
reply), to me this is not a crucial issue. Sure, if you screw up some
ad hoc maintenance, you could recover from this with a transaction
log. But not without some downtime; and you could also recover from a
backup prior to starting ad hoc maintenance.
The type of clients I see using Firebird are not 24/7 operations and
they definitely would not be performing the type of operation you
described themselves - for the 24/7's perhaps ASA would be a better
solution. But they do consider their applications and data mission
critical, and the combination of ease of installation and use, small
footprint and data security via live backups and shadowing is, to me,
a very convincing argument for using the product. And, of course,
there's the license agreement.
If Bruce or Lesley reads this - I crossgraded to FM3 just this week,
before you posted the possibilty of having it support Firebird - I'm
thrilled that you're attaching a priority to it. - go for it Lesley!
Marshall
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.647 / Virus Database: 414 - Release Date: 2004-03-29
[Non-text portions of this message have been removed]
News Group: comp.lang.clarion
On 1 Apr 2004 08:09:57 -0500, "Jack T."
<71045.3122_No_Spam_Here@...> wrote:
>Before you commit too heavily for something that people might back awayJack,
>from, I think people need to be apprised of a few of my findings that I'm
>sure will come out shortly anyway.
>I've been playing detective and have not found anything that posts SQL
>statements to a file to enable a roll forward even though there is a vendor
>out there that say that he can do that. He relies on you running a command
>line process that moves captured statements to a file.
After mentioning the IBLogFile "solution" in a post last night I
downloaded it and, after a cursory evaluation, agree that it is
anything but an ideal solution for the scenario(s) you have proposed.
The massive bloat to the main db for complete logging writes it off my
list immediately.
However (and here I'm echoing some of what Bruce has said in his
reply), to me this is not a crucial issue. Sure, if you screw up some
ad hoc maintenance, you could recover from this with a transaction
log. But not without some downtime; and you could also recover from a
backup prior to starting ad hoc maintenance.
The type of clients I see using Firebird are not 24/7 operations and
they definitely would not be performing the type of operation you
described themselves - for the 24/7's perhaps ASA would be a better
solution. But they do consider their applications and data mission
critical, and the combination of ease of installation and use, small
footprint and data security via live backups and shadowing is, to me,
a very convincing argument for using the product. And, of course,
there's the license agreement.
If Bruce or Lesley reads this - I crossgraded to FM3 just this week,
before you posted the possibilty of having it support Firebird - I'm
thrilled that you're attaching a priority to it. - go for it Lesley!
Marshall
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.647 / Virus Database: 414 - Release Date: 2004-03-29
[Non-text portions of this message have been removed]