At 10:07 PM 2/04/2009, you wrote:

>Hi Helen,
>
>Is term Cache and Page Buffers interchangeable?
>
>I'm still learning Firebird, so if I understand you correctly, I can leave the page size set to 8192 and change the Page Buffer from 4096 to anywhere from 75 to 125?

Yes.

> Could you explain the benefit of using one page buffer setting over another?

"Benefit" - no - once you are experienced with Firebird you can sometimes tweak the cache size to help the performance of some operations. But the *point* is that each Classic connection gets its own cache. The Superserver version, which creates threads for connection, shares its cache across all connections.

>Is there any formula to use when determining the best page size and page buffers to use?

There's no formula - it's feasible to test the effects of altering the cache size once you have a fully simulated production environment in your test lab. Stick with the recommended defaults until then. Do your sums: multiply the page size by the number of pages (buffers) and you'll arrive at the starting cache size.

>What is the best way to handle fixing my issue with the broken pages? Is as one kind person (Vlad) suggested using ALTER INDEX <INDEX_NAME> ALTER followed by a COMMIT all that is needed, and then follow this with running gfix -v -f again after index rebuild?

Follow Vlad's advice.

./hb