Subject | Use all space or not on large restore? |
---|---|
Author | Kjell Rilbe |
Post date | 2013-09-07T12:15:33Z |
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 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...
Regards,
Kjell
--
--------------------------------------
Kjell Rilbe
DataDIA AB
E-post: kjell@...
Telefon: 08-761 06 55
Mobil: 0733-44 24 64
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 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...
Regards,
Kjell
--
--------------------------------------
Kjell Rilbe
DataDIA AB
E-post: kjell@...
Telefon: 08-761 06 55
Mobil: 0733-44 24 64