dear ann,

i m so happy that you are here with your help !

i m sure that it's not connected to the memory probleme (force write is on), because these bug appear just after i update the schema of our database. now i split one table with 12 index in 40 tables with 2000 index (and add 10 times more row in it at the same time). strangely few day after that we start to have database corruption :( our database is very intensive (we have around 500 fb_inet_server.exe open every time for exemple).

also adding or deleting row to these 40 databases is a very low process. do you thing i can pass the pagesize from 4ko to 8ko can help ?

also do you thing that the superserver could be better than the classic server on such bug? or i can wait firebird 2.5 (when it's will be available) ?

thanks by advance
stephane

--- In firebird-support@yahoogroups.com, "Ann W. Harrison" <aharrison@...> wrote:
>
> svanderclock wrote:
> >
> > So what can cause index corruption? what the good rules to folow to not have index corruption ?
> >
>
> Some of the same things that can cause other database corruptions - not
> using forced write, bad memory or disk, and bugs in Firebird. Without
> being able to see the nature of the corruption, it's hard to guess what
> happened. If you're seeing this sort of problem regularly, then I'd
> be suspicious of memory problems.
>
> Best regards,
>
> Ann
>