> Hi all,
>
> I have a growing concern with regards to our choice to go with Fire Bird
> as a production database.
>
> Recently there have been a growing number of request for help relating
> to corrupted databases.
>
> My concern is that the FB database may not be as stable as one would hope.
>
> Is this correct or is it just a coincidence that these issues are
> coming up.
>
> Are there any plans to make the FB source code more bullet proof so as
> to help prevent these corrupted databases ?
>
> --
> Regards,
> Grant Brown

I am but a very light user. I have only about 80 server years experience
with high use production databases which started with Interbase 4.0 and have
been administered continuously by me only. (both client/server based and web
based) I have just released an application to 3000 users Australia wide
using both embedded and server based setups.
I can count my corruptions on one hand.
I had one corruption very early on with version 4 - I couldn't restore a
backup. I had to pump the data (no data loss). Fault? I suspect myself and
very little experience and it was during the development phase.
Since that time I have had 3 corruptions and they were definitely due to
hardware (harddisk) failure. I replicate all my production databases -
result - absolutely no loss of data (the failure was overnight in each
case - perhaps even thunderstorm on one occasion before UPS/conditioner was
installed) and downtime was about 20 minutes from awareness of problem.
I stand by IB/FB with all my support in this regard.
Alan

(PS the recent release above is planned for a 2 year life initially and will
increase my experience to about 6000 server years of version 1.5)