--- In firebird-support@yahoogroups.com, "Ann W. Harrison"
<aharrison@i...> wrote:

> binaryseti wrote:
> >
> >
> > Is there a way to reorder the rdb$relation_names in rdb$relations.
>
> Relation id's are issued in the order that the tables are defined.
> Changing them is most unwise. Two critical system tables, RDB$FORMATS
> and RDB$PAGES are driven off the relation id. If they don't match
> RDB$RELATIONS, your database won't work. You could try (I guess) (on a
> database you don't care about) changing the relation ids in those three
> places, but I suspect the result will be garbage.
> >
> > I would like the order of tables to be backed up and restored
> >
> Out of curiosity, why?
>
> > and I see that gbak uses the rdb$relation_id to do so.
>
> A better alternative would be to build a custom gbak that does what you
> want.
>
> > If I change the id what other systems tables will need to be updated?
>
> See above. And get a good backup before you start.
>
> Regards,
>
>
> Ann

Hi Ann,

A bit of background:
I have a fdb with payment history tables dating back to 1999
containing between 1.5 and 4 million transactions per year. These
payment tables do not change (At least the ones less than 2005).
I cannot move the payment tables to a second fdb
I have split the fdb into 2GB files on a linux box.

My reasoning:
I want to restore as many of the payment tables to one mount and the
other tables to a second mount. I am trying to have one mount that
does not change and does not need to be defragmented. To do this I
need the payment tables and transaction logs to be restored first,
where by restoring them to the first few fdb's. I can then relocate
them to a separate mount.

I also gzip the fdb's for backing up nightly and if I can exclude the
fdb's that do not change I could speed up the backup process. (This is
only a problem until Firebird 2 comes out with incremental backup).

Leon