If you are going to be storing only 2 months of data at a time, I would suggest using merge tables. Use one table per month. This
makes it very easy to "delete" data, simple redeclare what the union is. Then you can also retain previous months without affecting
performance.
One of the databases I
Thanks for the info Dan.
I'll check the resources you mentioned.
Regards
Andy
From: Dan Buettner [mailto:[EMAIL PROTECTED]
Sent: Tue 8/22/2006 1:38 PM
To: Andy Ford
Cc: mysql@lists.mysql.com
Subject: Re: limitations of mySQL i.e. number of rows
Sorry for the double post - I intended to mention this, but forgot.
For your automatic summary generation you could consider a cron job
piping in SQL, a la
*/3 * * * * mysql -D databaseName -e "insert into summaryTable select
now(), sum(numberColumn) from liveTable where datestamp > date_sub(
now(
Andy, performance will generally depend on several factors:
- size of each record
- amount of RAM
- speed of disks, for when RAM isn't enough
- concurrent inserts/writes (using InnoDB or MyISAM tables?)
At one level, 6 million records is no problem, and really not even
very many. If every recor
