Good Friday Morning to you all! Some of our MySQL databases are approaching the extrememly large size (10's of millions of records) and while we do regularly scheduled maintenance via CRON, and we do nightly differential back-ups couple with full back-ups on the weekends. Data is added at a fairly brisk pace, we archive data older than 90 days either in seperate tables (AWK script running SELECT ...INTO statements via CRON) or by running queries to get specific information (AWK, CRON) into other tables and deleting records, plus a couple of other ways. We maintain back-ups for a long, long time.
Yesterday I was told that we could expect our incoming data to grow by a factor of 3 in the next 4 months and that incoming data would grow by a factor of 10 over the next year. We're growing! Yippee for us! (he says, while trying to maintain a non-facetious look on his face) I always picture the worst possible scenario, because if something happens to the data my butt will be the one in the sling. Unless I can put if off on our hardware guys. So I am curious, how are you performing maintenance? I have a written maintenance plan which is reviewed periodically so that adjustments can be made if needed, but this plan looks a little thin to me when it comes to maintaining the size and scope of data that seems to be headed down the road towards me. Any suggestions you have would be most appreciated. Thanks! Jay --------------------------------------------------------------------- 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
