Re: Problem creating indices, autoincrement id's on HEAP engine.

[Michael Paik]

That would be pretty odd... It's not even an index, it's an autoincrement.

I did place an index on a certain column as a test, and space used for 50K rows was 513KB or so, so about 10B per row. By extrapolation, 500K rows should take 5MB, (granted I'm guessing O(n) growth).

There are 900 megs between the current table size and the max table size. If the autoincrement column cannot fit, that means that each element is 1.8K. 1.8K per 4 byte integer (45000% overhead, roughly) is a bit much I think.