On Thu, May 2, 2013 at 11:23 AM, W O <sistemas2000profesional@...>wrote:

>
> And a cycle backup/restore doesn't force each row to keep in a single page?
>

Gbak backup makes a copy of the current version of all data in its backup
file. Gbak
restore creates a new database and populates it with that data. Records
all get new
home pages.

If having a row in several pages causes bad performance it has sense trying

> to keep that rows as grouped as possible. Or not?
>

You have little or no control over that. Yes, Firebird tries to keep all
versions of
a record on the same page, but there's almost nothing, other than reserving
space
on pages, that you can control to influence the location of record versions.

Good luck,

Ann


[Non-text portions of this message have been removed]