1) dbschema -d my_dtb -t my_table -ss > my_script.sql
2) unload to "file.unl" select * from my_table
3) drop my_table
4) modify my_script.sql ( you must modified value first and next extent ).
5) create my_table with clausule first, next extent ( in file
6) load from.... insert into ...
You must calculated value "first extents" from count all extents. Table
contain actual value first and next extent. Attention !! Informix engine
value "next extent" with every next allocate ( when last extent is full ).
You set value "next extent" as 10% first extent.
Cluster's index is used only for static table ( table which is not modified
or table is modified the least ). Sentences are sorted physical by index's
>1) dbschema -d my_dtb -t my_table -ss > my_script.sql
>2) unload to "file.unl" select * from my_table
>3) drop my_table
>4) modify my_script.sql ( you must modified value first and next extent ).
>5) create my_table with clausule first, next extent ( in file
>6) load from.... insert into ...
Hampton Hill, UK
Sent: Tuesday, August 03, 1999 9:19 AM
Subject: alter index to cluster
I had a table which had 22 extents. I altered the unique index to
through isql. Now, oncheck -pT reports that the table has 20
Shouldn't it be just 1? When I do a dbschema on the table the index
listed as 'unique cluster index,' so why are there 20 extents?
There might not be enough contiguous space for just 1 extent. If you
cluster an index there needs to be enough contiguous space for the entire
table for the table to be truly de-fragmented
Is there a way to alter the index to cluster?
To reset the values of the primary key ?
I tried deleting the ID column and then recreating it.
But the order of the records remains the same. It follows some
internal index which is really the one I want changed.
I now have:
3 11 <<<<<<
and would like:
5 11 <<<<<
4. ADO & VB