At 08:11 AM 5/1/2002, you wrote:
>MySQL is great, for example, for the typical web-hosting provider who
>usually needs a small RDBMS which would accomodate a few hundred
>databases with a few thousand records each.
I can see that it is indeed very popular amongst such providers.
And I also agree with what you say below about potential growth in size and
complexity. However I also realize that one can often buy more than what
one really needs - esp. when one talks about those enterprise oriented
commercial RDBMS. One also does see a trend where commercial RDBMS
environments once targeted at large enterprises are now trying to create
niche markets in the small business segment too.
I would say that if one is looking for complexity and scalability of RDBMS
in the open source world, Postgres is a good choice. Though I am not too
confortable with the pace of it's development.
Leo
> Leo> Now why would such an organization go for an over-kill RDBMS
> Leo> like ORACLE for example, if MySQL can do the job?
>
>No reason at all. I agree, MySQL is great for some scenarios.
>However I personally wouldn't use it as far as possible, since any
>application I can think of developing would have growth potential.
>It's basically a question of looking at the future -- if there's any
>chance at all that your database will grow larger and your access to
>the database more complex over time then you should be seriously
>looking at one of the alternatives. If the application and data
>access are static, and the database only growing at (say) 10-20% per
>year, no reason to avoid MySQL at all.
================================================
To subscribe, send email to [EMAIL PROTECTED] with subscribe in subject header
To unsubscribe, send email to [EMAIL PROTECTED] with unsubscribe in subject header
Archives are available at http://www.mail-archive.com/ilugd%40wpaa.org
=================================================
