On Wed, Mar 21, 2007 at 04:42:55PM +0200, Jonathan Ben Avraham wrote: > Hi Geoffrey, > I beg to disagree. A simple redesign should do the trick. The problem IMHO > is that the query in question has to go through the whole database each > time. Busting the table up into smaller tables ordered by date keys and > categories or whatever with keys to the articles should do the trick with > MySQL and modest hardware.
Bear in mind that the original question was about a database three times the size with 30 million records. Obviously good design and programing is essential, but it may still be too big. My experience is that whenever you design a system, you start with what you think will be the maximum demands and make sure you can scale up, not start with something near its limits and hope you don't have to. This then leads to a related question, if MySQL on a PC is too small, and Oracle/DB2 is too much, is there something in between? While I've seen the ads in the business magazines that claim SQL/Server on Windows Server 2003 would do the job perfectly, I would not bet the price of the magazine they would. Geoff. -- Geoffrey S. Mendelson, Jerusalem, Israel [EMAIL PROTECTED] N3OWJ/4X1GM IL Voice: (07)-7424-1667 Fax ONLY: 972-2-648-1443 U.S. Voice: 1-215-821-1838 Visit my 'blog at http://geoffstechno.livejournal.com/ ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
