Hi all:
It is possible to activate and to deactivate the one
indexes tablaA without lowering the instance.
As serious the syntax and
the risks
ThanksThe freedom of Linux ... The power of Informix
_________________________________________________________________
Descubre Live.com - tu propia página de inicio, personalizada para ver rápidamente todo lo que te interesa en un mismo sitio.
http://www.live.com/getstarted
↪ replying to Juan Pablo
On May 9, 5:58 pm, Juan Pablo <in4mixp...@hotmail.com> wrote:
> Hi all:
>
> It is possible to activate and to deactivate the one
> indexes tablaA without lowering the instance.
> As serious the syntax and
> the risks
>
> ThanksThe freedom of Linux ... The power of Informix
> _________________________________________________________________
> Descubre Live.com - tu propia página de inicio, personalizada para ver rápidamente todo lo que te interesa en un mismo sitio.http://www.live.com/getstarted
I'm not sure I understand what you mean, but a single index or all the
indexes for a table can be disabled using the "SET INDEXES ..."
command - see the SQL manual for syntax. (at least in 10.0). If the
index is needed for a referential integrity constraint, one cannot
disable it unless the constraint is disabled as well.
As for risks: if you are disabling a unique index (or a referential
integrity constraint), you are risking creating rows in your table
that do not fit your model (i.e. bad data). Another potential problem
is access times may suffer if the indexes disabled are the best ones
for the queries. When the indexes are finally enabled, they need to be
rebuilt, which may take a substantial amount of time and have other
effects. You may also encounter the notorious -710 bug: stored
procedures and prepared statements that expect to use an index
suddenly find that it is not valid anymore.
hope this helps,
Zachi