i think it's a crazy operation... those index are forenkey and primary key
live..

gbak backup data, not index data. when it's restore, restore data and
re-create all index. even if all index are inactive.



2010/8/16 paulfirebird@... <paul.vanderlinden@...>

>
>
> Does anyone have an idea/solution for this?
>
> --- In firebird-support@yahoogroups.com<firebird-support%40yahoogroups.com>,
> "paulfirebird@..." <paul.vanderlinden@...> wrote:
> >
> >
> >
> > --- In firebird-support@yahoogroups.com<firebird-support%40yahoogroups.com>,
> Stefan Heymann <lists@> wrote:
> > >
> > > > To summarize:
> > > > Fill database
> > > > Set index (takes about 6 hours)
> > > > Create backup (which removes index)
> > > > Create database from backup (which adds the index, again 6 hours)
> > >
> > > > So the index is created twice.
> > > > Is there a way to improve this? F.e. by putting a inactive index in
> > > > the database that gets activated at the create database from backup?
> > >
> > > You can use GBAK -i and all indexes will be restored as INACTIVE. So
> > > you can start to work with the application and activate the indexes in
> > > parallel.
> > >
> > > You can also use the GFIX -mo[de] read_only switch to set an existing
> > > database to read-only-mode.
> > >
> > > Regards
> > >
> > > Stefan
> > >
> >
> > I want exactly the opposite, because I want to make ready-to-use
> databases. F.e. an option that activates inactive indexes
> >
> > Greetings,
> > Paul
> >
>
>
>

--
Ricardo...


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