ARCHIVING UNDER HEAVY LOAD
Hello! There's a need to design a system (something like online forum) that will be storing huge amount of small messages in database. There must be fast access only to messages for the last 3 days (guess this means that main table with indexes on it must be kept small?), while other messages can be stored in rarely accessed archive (different table?). What's the best practice for implementing archiving in MySQL? In Oracle there's an ability to "switch off" part of the table and then move it to archive in background mode. What about MySQL? Thanks in advance, Alex - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
ARCHIVING UNDER HEAVY LOAD
Hello! There's a need to design a system (something like online forum) that will be storing huge amount of small messages in database. There must be fast access only to messages for the last 3 days (guess this means that main table with indexes on it must be kept small?), while other messages can be stored in rarely accessed archive (different table?). What's the best practice for implementing archiving in MySQL? In Oracle there's an ability to "switch off" part of the table and then move it to archive in background mode. What about MySQL? Thanks in advance, Alex - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php