Its a very simple table that will store messages.
Each message would have subject, body,to_user_id, from_user_id,is_deleted,date_sent and
may be one or two more column
There would be frequent read operation and slow write operation.
Thanks
SN
Personally I'm always ready to learn, although I do not always like being taught
----- Forwarded Message ----
From: "sudhir543-nimavat@stripped" <sudhir543-nimavat@stripped>
To: Jay Ess <lists@stripped>
Sent: Mon, 2 November, 2009 3:34:52 PM
Subject: Re: 50M records each year, help me choosing the stretegy
Its a very simple table that will store messages.
Each message would have subject, body,to_user_id, from_user_id,is_deleted,date_sent and
may be one or two more column
There would be frequent read operation and slow write operation.
Thanks
SN
Personally I'm always ready to learn, although I do not always like being taught
________________________________
From: Jay Ess <lists@stripped>
Cc: Mysql <mysql@stripped>
Sent: Mon, 2 November, 2009 3:04:36 PM
Subject: Re: 50M records each year, help me choosing the stretegy
sudhir543-nimavat@stripped wrote:
> I have come across a requirement where I need to store a very large amount of data
in a table. In
> one of our app.. we can have around 50 Million records each year.. Can
> any one guide me in choosing a strategy than can handle this load.
50M records is not that bad if you only store a couple of bytes in every row. So please
describe your tables in more detail.
And also describe the expected access on the data.
-- MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=1
________________________________
Yahoo! India has a new look. Take a sneak peek.
Keep up with people you care about with Yahoo! India Mail. Learn how.
http://in.overview.mail.yahoo.com/connectmore
