Dear Alex,

yes, i agree with you, when our database was not very large (<10go), everything work without lot of problem (except time to time for exemple 100% CPU usage for infinite time that we resolve ourself by increasing the selectivity of one of one our index.. i thing this was also after resolved in next release of firebird)

but now that our database become to be in medium state (> 30 GO, + 10 000 000 queries every days), it's a disaster :( a nightmare ...

Thanks to vlad, he discovered that using the monitoring table is one raison of one bug (lock error), but unfortunatly it's seam not answer all the other bug (index corrupted for exemple) ... so it's seam that we are facing now not only one single bug but more ... we was thinking the head is just under the water but finally we discover that we are more deeply under the water :(

thanks for you support alex
stephane

--- In firebird-support@yahoogroups.com, "Carrell Alex" <Alex.Carrell@...> wrote:
>
> Stephane
>
> As some one impartial. who just watches this list, here is a point of view in regard:
> >> also this what i don't like,
>
> ..Most the questions you posted on this list at the start, were definite RTM questions, posted on to this list to save the time of RTM. This does suggest to me that the software on your part may suffer the same issues. This is not defence of FB though.
> For me switching from IB, MSSQL to Oracle, MySql, PostgreSql to FB a lot of knowledge is transferrable. The special tricks may not be. From the questions asked I would gauge your knowledge was not high of databases. This would affect how you design your software. I have not seen any major FB issues in 5 years, but the system I have is small. The main database issues I have seen are software related, entering extra information, not clearing transactions. Last summer we lost one of our main servers due to an age old bug that crept up in the sotware posting bad data, leading to index failure. Well, I am sure of it, change of software fixed issue. Though I did take the downtime to move to a new release of Database.
> I would also add that the longer in software writing, the more likely to RTM before posting. This again points to Software knowhow.
> By the way, your questions have become more interesting and I have learnt more recently from the answers. Keep posting.
>
> alex.
>
> -----Original Message-----
> From: firebird-support@yahoogroups.com [mailto:firebird-support@yahoogroups.com] On Behalf Of svanderclock
> Sent: 28 April 2010 08:08
> To: firebird-support@yahoogroups.com
> Subject: [firebird-support] Re: is Firebird the good or wrong choice ?
>
> > You thought that your application is full of errors and because of
> > this database is corrupt?
> > Just a hint!
>
>
> not sure to understand what yu mean, but if you mean that our application is buggy and this why the database is corrupt i answer what this @#&% ! ( sorry helene, but at less now i have encoded the bad word ;) ? even if our application was full of errors, why index can be corrupted? why the database himself can be corrupted ? why the firebird server can Crash ? why the Firebird server can freeze ? as you know probably application not discuss directly with firebird but with fbclient.dll API ! so no application full of errors can crash an server...
>
> also this what i don't like, i soon as we say something is wrong in the engine, most of the time the simple answer we receive is that it's because of us (your application is buggy, you do something wrong, your misunderstanding, etc..) ... even philipe in some past time suggest us to go in some NoSQL database ! cold in the back when we know who is phillipe :(
>
>
> just a hint
> stephane
>
>
>
> ------------------------------------
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://www.firebirdsql.org and click the Resources item on the main (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Yahoo! Groups Links
>
>
>
> This message and any attachments (the message) are intended solely for the addressees and are
> confidential. If you receive this message in error, please delete it and immediately notify
> the sender. Any use not in accordance with its purpose, any dissemination, copying or disclosure,
> either whole or partial is prohibited without prior formal approval. The internet cannot
> guarantee the integrity of the message. The companies of Bobst Group do not accept any liability
> for data corruption, delay, interception or any modification in relation with this message.
>