You can't do efficient ranging on a HASH indexed column without a table scan...
Select * from heap_table where indx_col between 247 and 258 This would table scan your 200meg table even if "indx_col" is a PRIMARY KEY, using the default hash key. Hash key was the only choice prior to 4.1, but now you can use BTREE for HEAP tables. Again, it depends on how you use your tables. If your server blinks, scheduled or otherwise, you loose all of your table contents...forcing you to reload your data. Make sure you place a practical MAX_ROWS= on your create table to prevent your table from accidentally eating all of you're available memory. Ed -----Original Message----- From: Daniel Cummings [mailto:[EMAIL PROTECTED] Subject: Heap table limitations We want to convert a 200+ meg table to a heap table. We've gotten pretty good performance converting from InnoDb to MyIsam table but converting to a heap table would give an even bigger performance boost. Does making a heap file this large make any sense? Are there size limitations to heap tables? TIA Dan -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
