Den 2013-09-07 15:35 skrev fabianoas...@gmail.com 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
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).
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.ri...@datadia.se escreveu:
**
Hi,
I intend to upgrade my ~100 Gbyte
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
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.
On Sat, Sep 7, 2013 at 8:15 AM, Kjell Rilbe kjell.ri...@datadia.se 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
