On Sat, Sep 7, 2013 at 11:07 AM, wrote:
>
> The page isze is 16KB.
>
> I'm not run gstat. I will try do it.
>
At the same time, you should get some monitoring statistics -
reads/writes/marks/fetches.
And some system stats as well - memory, page faults, disk writes, etc.
Good luck,
Ann
>
>
On Sat, Sep 7, 2013 at 8:15 AM, Kjell Rilbe wrote:
>
> I'm considering if "use all space" would be a good idea or not. I think
> I understand its effect on indices: fill index pages completely vs.
> leave 25% free space on each index page for new entries.
>
> Unh, no. Use All Space affects only
Thank you very much Paul for answering.
In your document "Firebird 2.5 - Language Reference Update" the database
owner, BOB, writes:
*grant digger to frank with admin option granted by fritz*
*
*
but, what if fritz doesnt agree with to be the grantor?
It can take him a long time for know that he
You seem to not be solving a problem but only looking to improve something.
What are you trying to improve?
I say you are just looking for trouble by changing something that is not a
problem.
Hi,
I intend to upgrade my ~Gbyte database to new ODS (for FB 2.5) using
backup/restore cycle. For this database, each table has a PK that's
strictly incremental, but not contiguous (the same contiguous sequence
is used for all tables due to a framework I use = not my personal
choice). Most ta
Do not use this in production databases.
It is intended to be used in read only databases, when no writes is allowed
and space is critical, like shipping a catalog product in a cdrom.
Em 07/09/2013 09:18, "Kjell Rilbe" escreveu:
> **
>
>
> Hi,
>
> I intend to upgrade my ~100 Gbyte database to new
Hi,
I intend to upgrade my ~100 Gbyte database to new ODS (for FB 2.5) using
backup/restore cycle. For this database, each table has a PK that's
strictly incremental, but not contiguous (the same contiguous sequence
is used for all tables due to a framework I use = not my personal
choice). Mos
