Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Art S. Kagel — — source: Informix-list mailing list archive (1991-1998)
David Williams wrote:
>
> In article <67cdtc$2hk@cssun.mathcs.emory.edu>, sujata_soman_at_omm-
> la2-infotech-001@internet.omm.com writes
> >
> >Hi all,
> > One of our heavily accessed tables is pretty badly fragmented and I need to
> >de-fragment it ( if such a word exists ). Before you ask, ours is an OLTP kind
> >of env, and so fragmenting is not such a good idea.
Expanding on David's suggestion:
In your kind of environment the table is likely to fragment again later.
You should consider making a separate dbspace for each performance
critical table that is likely to become fragmented.
BTW by creating these new dbspaces you could proceed as follows:
1) create new tables (with temporary names) in the new dbspaces
2) copy the data from the original tables to the new ones
3) drop the old table
4) rename the new table to the old name
5) drop the old dbspace to recover the chunks
A table with its own dbspace will only have one fragment per chunk due
to contiguous fragment compression.
Art S. Kagel
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.