|Subject||Re: [firebird-support] Use all space or not on large restore?|
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.
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). Most tables also have (several) other indices that are not
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.
I suspect "use all space" would be good for the PK:s but not for the
Is there any way to achieve this?
What would you recommend?
I'd prefer to get it right the first time, because the complete process
takes 12-24 hours...
Telefon: 08-761 06 55
Mobil: 0733-44 24 64