I have a table that's used for logging. We do a ton of SELECTs and INSERTs on this table, but no UPDATEs. In order to keep the SELECT speed high, we archive most items older than 30 days by moving them out from this table to another. This, of course, creates a ton of holes which we optimize away nightly, but the optimization process takes an awfully long time (~200s).
Is there a way to eliminate this optimization by specifying that inserts should /always/ go at the end of the table, regardless of any holes? Is this nightly archive the Right Way To Do It, or is there an alternative I'm unaware of? Would another table type outperform MyISAM under this scenario? ____________________________________________________________ Eamon Daly NextWave Media Group LLC Tel: 1 773 975-1115 Fax: 1 773 913-0970 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
