Subject Re: [firebird-support] Use all space or not on large restore?
Author Kjell Rilbe
Den 2013-09-07 15:35 skrev fabianoaspro@... såhär:
> 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" <kjell.rilbe@...
> <mailto:kjell.rilbe@...>> escreveu:
> 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). Most tables also have (several) other indices that are not
> incremental.
> 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
> other indices?
> 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...

Replying here to both Fabiano(?), Ann and Doug. Thank you for clearing
up my misunderstanding re. index vs. data pages. I understand now that
"use all space" is not useful in my situation.

Doug: I'm not trying to "solve" or "improve" something. I am going to
upgrade the ODS from the one for FB 2.1 to the one for FB 2.5, since
I've now finally upgraded the FB installation. And, since that's an
operation that takes ~12-24 hours, I want to get it right the first
time, and hopefully with the "best" options for my database, i.e. the
options that will give best performance when using the resulting database.


Kjell Rilbe
E-post: kjell@...
Telefon: 08-761 06 55
Mobil: 0733-44 24 64