>Craig,
>
>>Nope, that's the way it works. REINDEX will simply tacks the new keys at the end of the CDX and not reuse the old space. This is called Index Bloat. You need to DELETE TAG or DELETE TAG ALL before doing and INDEX ON (At this point, REINDEX will not work). There is a KB article on my web site that explains this.
>
>Sorry to be snippy, but did you even read my post?
>
>I am well aware that when properly reindexing, one should use a DELETE TAG ALL and then rebuild.
>
>My posting has nothing to do with that.
>
>As I used SQL INSERTs to build my table, the CDX grew to 113 MB in size. I then simply opened the table exclusively, issued a straight REINDEX, and the size of the CDX file _dropped_ to 67 MB. If I had done a DELETE TAG ALL and rebuilt indexes, it may have gotten even smaller -- I didn't test that. I didn't need to test that, given the fact that a straight REINDEX dropped the CDX size considerably and queries were running in sub-second fashion. I want to know why clean INSERTS resulted in such a sloppy, bloated CDX file, and at what size of a table does this become noticeable?
>
>Any ideas on why the initial build of the table via INSERTs results in such a bloated, slow CDX file?
>
>Thanks,
>JoeK

Sorry about that. I read the posting twice, and it still came out the same ... I guess that's what happens on a Friday afternoon before a holiday weekend. I'll agree with Brad on this one.

Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer