use DB2 or MySQL ?

danielle

Hi all.... Need some expert input here. I just started at a new company and am trying to get them some web services. My job is to be web designer/web developer but I will also need to do some support for the web server.

I use php/mysql combo most always but have some dev. experience with asp.net/SQL and cold fusion/SQL.

Since they haven't had a web developer ... ever ... they don't have a database set up at all.

soooo... i need to figure out what should be used.

The choices are DB2 (already installed) or install mysql.

They are running Apache on an AS400 - I5/OS -PHP Version 4.3.3.

here's what i'm thinking.....

db2 -
pro - supported by IBM, company has $ for liscencing

mysql
pro - i can do php/mysql with my eyes shut. i'm no wiz at the added features of DB2 and have so far never needed them.

-the db2 is there but we have no access as far as we can tell so even if we decide to keep the db2, there are config things to sort out. i'm thinking that if we are going to have to sort all that out anyway, why not just put mysql on there? but not being a super server admin wiz, i'm afraid of screwing something up.

needs/concerns
1. longevity - long term solution that can allow for many thousands of records and web apps that will have peak/heavy use at times
2. stability - keep running under heavy use, data is safe
3. low maintenance - geeky part runs itself, not a lot of administration once config is set up
4. plays well with php 😉

questions---
does anyone have any experience with using IBM's i series as a webserver?
if so, anyone out there running mysql on an i5/os?
any input on db2 vs mysql?

i have read several pro/con info and am still undecided....
any info/opinion/help anyone can give would be greatly appreciated!!!!!! 😕

bastien

we use db2/mysql/mssql and found that db2 is very slow and depending on how configured, it can be a real headache to deal with in terms of searches (case sensitivity and the like)

If I were in your shoes I would look at a solution that uses the db2 data to feed the mysql server (cron jobs or something similar) if that data is needed...

The pros

You can select what data to display (more secure) and reduce the load off of the main db2 server (may or may not be a consideration). It also avoids having to learn, sometimes painfully, the tricks and limitations of DB2 and the DB2 version of sql.

Mysql and php play well together and are very web oriented, giving great response times and handles a high load...

Cons

You will need to find out how mysql plays in that environment. May loose some of the flexibility of DB2. My recommended set up may be more complex to manage due more single points of failure in the system.

Some careful analysis of the requirements and architecture is required to come to the best decision. Note that its very easy to setup a mysql testbed platform for very cheap whereas getting a test DB2 set may be more expensive and complex to setup