How much power do you want? We migrated from Oracle to MySQL because to get enough power from Oracle 8/9i, we had to buy an extremely powerful machine. We had oracle on a sun solaris 9 box, and got X amount of power out of it.
On a similar machine we installed MySQL and we got XX amount of power out of it. We choose MySQL because we can get more power out of it on a simple server than we did with Oracle. And MySQL was more flexible. Additionally, data management is easier for us on MySQL. We house dozens of organizations on MySQL servers. Each org either shares a db server, or they get their own db servers. In fact we are now installing MySQL on xen/linux systems and are able to reallocate memory and CPU to xen servers if they need more, rather than having to upgrade hardware in machines. When CPU amd memory start to top on a machine, we look at the queries and optimize them. That usually fixes anything that slows down the server. Our typical xen linux system is 8GB dual-ranked memory Intel 3GHz 1333FSB Quad-core CPU 4MB-Cache. You want to get memory that matches the CPU FSB, or as close to it as possible. We use the RHEL (Red Hat Enterprise Linux). I think many people find other non-intel systems perform better for Oracle - But that is because those systems are optimized at sale point. If the Intel system hardware is configured well, it will perform just as good with MySQL. And you can always migrate from MySQL to Oracle later if you really find that you need to. Tell your employer, if they want to pad the bottom line, they should use inexpensive MySQL and spend some of the savings optimizing the Web Application. Use Java grid technology, and load balance your read-only SQL queries (look at Free Sequoia - https://forge.continuent.org/projects/sequoia ) -RG Mohammad wrk wrote: > Hi, > > I'm working on a web 2.0 project that targeting small to medium size > companies for providing business services. Companies simply register to the > site and then start their business by loading their data, sharing and > discussing them with others. > > The design/architectural decision now we are facing from database perspective > is how we should store companies' specific data? One way is to put all of > them in a single database and partition them by company-id and the other one > is to create, on the fly, a new database per company . The justification for > the latter is that MySQL is not powerful enough (compare to Oracle or DB2) to > handle large amount of data and concurrent users. > > I'm new to MySQL and don't know that much about it and this is why I'd like > to discuss this concern here. > > Thanks, > > Mohammad > > > > > Ask a question on any topic and get answers from real people. Go to > Yahoo! Answers and share what you know at http://ca.answers.yahoo.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
