Here are a few examples of my tables. Table name, # of records, type, and size. The database currently has 898 million records in it and it's right over 100 gigs.
Phrase 49,769,178 MyISAM 5.3 GB Volume 9,671,996 MyISAM 1.1 GB Word 7,790,076 MyISAM 942.2 MB WordMagic 128,881,167 MyISAM 6.0 GB WordMagicScores 111,060,572 MyISAM 7.4 GB WordWatcher 44,270,528 MyISAM 4.3 GB WordPhrases 11,154,414 MyISAM 450.9 MB WordRelated 13,685,867 MyISAM 2.7 GB WordRelated2 13,194,313 MyISAM 2.6 GB WordScore 68,437,613 MyISAM 12.7 GB WordScoreTemp 118,723,375 MyISAM 25.3 GB WordSearch 188,769,835 MyISAM 11.5 GB WordStem 15,623,221 MyISAM 417.3 MB Donny > -----Original Message----- > From: Brent Baisley [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 11, 2004 10:09 AM > To: Ronan Lucio > Cc: [EMAIL PROTECTED] > Subject: Re: Database structure > > Where did you read that 25 million records would be a problem? I've > heard of people with billions of records in one table. The only > question would be performance, but indexes would largely take care of > that. You may run into issues with the physical size of the table and > the underlying OS not being able to create a large enough file (i.e. > 4GB). This is a problem with the OS, not MySQL. InnoDB would allow you > to work around file size limitation in the OS by splitting the database > into separate files. > > > On May 11, 2004, at 10:10 AM, Ronan Lucio wrote: > > > Hi, > > > > I´m working in a project of a database that should be grow > > to more than 25,000,000 of clients. > > > > For all I´ve read in MySQL manual pages it´s too much records > > to place in only one table. > > So, my main doubt is how to divide it. > > > > I divide the client table in few tables according with the different > > kinds of clients. > > Even getting some duplicated records and getting some difficulties > > importing and exporting clients from one table to another it should > > take the database load cooler. > > > > But, I think I´ll need to place all logins and access levels in the > > same > > table. > > > > Would it be a problem? > > Any idea how can I deal with it? > > > > I´m thinking to use InnoDB tables. > > > > Thanks, > > Ronan > > > > > > > > > > -- > > MySQL General Mailing List > > For list archives: http://lists.mysql.com/mysql > > To unsubscribe: > > http://lists.mysql.com/[EMAIL PROTECTED] > > > > > -- > Brent Baisley > Systems Architect > Landover Associates, Inc. > Search & Advisory Services for Advanced Technology Environments > p: 212.759.6400/800.759.0577 > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/[EMAIL PROTECTED] > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
