may suite your needs.
I have seen three legged dogs run pretty fast.
- Original Message -
From: "Andy Ford" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, August 22, 2006 7:56 AM
Subject: limitations of mySQL i.e. number of rows
Hi everyone
I have a requirement to store in
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
Hi everyone
I have a requirement to store in the region of 3 million entries per month (30
ish days) of data in a mySQL database totalling a maximum of 2 months (6
Million entries).
The database will be 'probably' reside on a Sun V240. I have a similar size
database running on an old Sun E450