Re: Can MySQL handle 120 million records?

[Gerald Jensen]

Joe is right ... we switched from another SQL server to MySQL in 1999, and
have never looked back.

MySQL has been rock solid for our applications, the MySQL development team
is great to work with, and our customers like it.

Gerald Jensen

----- Original Message -----
From: "Joe Stump" <jstump@stripped>
To: <mysql@stripped>; "Michael She" <michael.she@stripped>
Cc: "Qunfeng Dong" <dongqunfeng@stripped>; <bg.mahesh@stripped>
Sent: Wednesday, December 18, 2002 1:55 PM
Subject: RE: Can MySQL handle 120 million records?


> Without trying to sound like a troll or a rant I'd like to chime in on the
> side of Jeremy.
>
> I've worked with MySQL on sites that serve up over a million hits a day.
We
> hit the 2gb file limit in Linux (NOT a MySQL problem) and moved to Solaris
> without incident.
>
> A friend of mine had over a billion rows in a few of this tables
> (statistical data mostly).
>
> As Jeremy points out all DB's have their problems, shortcomings, etc. If
you
> have specific complaints fill out a feature request, if you've got
problems
> fill out a bug report, but don't knock MySQL as
> not-worthy-of-enterprise-status because it doesn't *work* like Oracle,
etc.
>
> Overall, in my many experiences, it is more than sufficient for web apps.
>
> --Joe
>
>
> --
> Joe Stump <joe@stripped>
> http://www.joestump.net
>
>
> -----Original Message-----
> From: Jeremy Zawodny [mailto:Jeremy@stripped]
> Sent: Wednesday, December 18, 2002 8:09 AM
> To: Michael She
> Cc: Qunfeng Dong; bg.mahesh@stripped; mysql@stripped
> Subject: Re: Can MySQL handle 120 million records?
>
>
> On Wed, Dec 18, 2002 at 02:37:07AM -0500, Michael She wrote:
> >
> > I agree.  MySQL is a great database, but I wouldn't call it
> > enterprise grade.
>
> Since you haven't told us what "enterprise grade" means to you, that
> doesn't tell us much.  What is it lacking to become "enterprise grade"
> in your mind?
>
> > Considering that the database is used to store billing
> > information... one has to be weary about losing all the records due
> > to a bug or deficiency in MySQL.
>
> That's true of any database server, right?  It's not really a
> MySQL-specific complaint.
>
> > I was searching through some of the MySQL help documentation, and
> > there have been more than a few examples in the comments where
> > people have lost data due to wacky functions on databases greater
> > than a couple of GBs...
>
> Imagine what you'd read it Oracle was open enough to allow comments in
> their on-line docs.  Seriously.  I've heard pretty nasty stories about
> Oracle, Microsoft SQL Server, and so on.
>
> Jeremy
> --
> Jeremy D. Zawodny     |  Perl, Web, MySQL, Linux Magazine, Yahoo!
> <Jeremy@stripped>  |  http://jeremy.zawodny.com/
>
> MySQL 3.23.51: up 3 days, processed 136,618,914 queries (457/sec. avg)
>
> ---------------------------------------------------------------------
> Before posting, please check:
>    http://www.mysql.com/manual.php   (the manual)
>    http://lists.mysql.com/           (the list archive)
>
> To request this thread, e-mail <mysql-thread127817@stripped>
> To unsubscribe, e-mail
> <mysql-unsubscribe-jstump=aa.acinc.com@stripped>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>
>
>
> ---------------------------------------------------------------------
> Before posting, please check:
>    http://www.mysql.com/manual.php   (the manual)
>    http://lists.mysql.com/           (the list archive)
>
> To request this thread, e-mail <mysql-thread127826@stripped>
> To unsubscribe, e-mail
<mysql-unsubscribe-autodata=execpc.com@stripped>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>
>
>