Tim,

I upgraded tables from dbIsam 3.3. I looked at the table(disk)size and the
index(disk)size. Then I did a repair (all in edbmngr). After the repair the
indexsize is bigger.  I tried it with several tables. It only happens if I
do it after the upgrade. Repairing once the tables are EDB doesnot effect
the index(disk) size.

What's the reason for this?
Is repairing also optimizing?

Regards, Harry

Tim,

It happens also when adding an index! After that, repairing increases the
size (after adding it looked like nothing happend to the size). Should one
always repair a table after such actions or is it a flaw (or caused by
something obvious that I don't see).

Harry

"Harry de Boer" <harry@staaf.nl> schreef in bericht
news:587D8A35-E400-41DE-9516-ACF20A4A79D3@news.elevatesoft.com...
> Tim,
>
> I upgraded tables from dbIsam 3.3. I looked at the table(disk)size and the
> index(disk)size. Then I did a repair (all in edbmngr). After the repair
the
> indexsize is bigger.  I tried it with several tables. It only happens if I
> do it after the upgrade. Repairing once the tables are EDB doesnot effect
> the index(disk) size.
>
> What's the reason for this?
> Is repairing also optimizing?
>
> Regards, Harry
>
>

Harry,

<< It happens also when adding an index! After that, repairing increases the
size (after adding it looked like nothing happend to the size). Should one
always repair a table after such actions or is it a flaw (or caused by
something obvious that I don't see). >>

Repairing a table in EDB will increase the index size slightly.  EDB has to
add a special internal index for the purpose of trapping/repairing duplicate
row IDs.  It's nothing to worry about, and you can safely ignore it.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

Thanks, that explains it. Could I have read this in the manual? If so, sorry
for bothering.

Regards, Harry



"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> schreef in bericht
news:5970BF21-3E49-4FC6-B15E-35C7F922F723@news.elevatesoft.com...
> Harry,
>
> << It happens also when adding an index! After that, repairing increases
the
> size (after adding it looked like nothing happend to the size). Should one
> always repair a table after such actions or is it a flaw (or caused by
> something obvious that I don't see). >>
>
> Repairing a table in EDB will increase the index size slightly.  EDB has
to
> add a special internal index for the purpose of trapping/repairing
duplicate
> row IDs.  It's nothing to worry about, and you can safely ignore it.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>

Harry,

<< Thanks, that explains it. Could I have read this in the manual? If so,
sorry for bothering. >>

No, it's not mentioned, but I will make a point to add a Note about it for
the REPAIR TABLE statement.

--
Tim Young
Elevate Software
www.elevatesoft.com