Thank you very much Ann for your answer.

And I was talking about gbak's task, not mine, sorry for my bad English.

If having each record in one page is better than having a record in two or
more pages then have sense for me that gbak keep each record in just one
page when rebuilding the database when it is doing a restore.

Greetings.

Walter.

On Thu, May 2, 2013 at 1:59 PM, Ann Harrison <aharrison@...>wrote:

> **
>
>
> 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]
>
>
>


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