On Fri, 28 Jan 2005 11:47:47 +0000, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Jacob Friis Larsen <[EMAIL PROTECTED]> wrote on 28/01/2005 11:23:46:
We have a table that grow by 200MB each day.
Should we put data in different tables or is one big table just as fast? We will for new data do select, update and insert and for old data only select.
It is not possible to answer in the general case - you would need to explain more about your table and usage patterns.
The table contains data from RSS and Atom feeds. Most users only need to see the newest items. A select could look like this: "SELECT title, desc FROM items WHERE feedid = 25 LIMIT 10"
Jacob:
The above query should be very fast as long as you have a key on feedid even if the table is very large. I see one problem with it, though - in this form it is not guaranteed to give you the most recent items. You need to add an ORDER BY some timestamp DESC for it to work right.
I would, however, be seriously concerned about diskspace if a table is adding 200 MB a day with no archiving/compression/purges.
-- Sasha Pachev AskSasha Linux Consulting http://www.asksasha.com
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
