Link to home
Start Free TrialLog in
Avatar of Darkylove
Darkylove

asked on

what are the strengths and weakness of different databases?

what are the strengths and weakness of different databases? the differences between MySQL, Access, Oracle
ASKER CERTIFIED SOLUTION
Avatar of halejr1
halejr1
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Avatar of Patrick Matthews
Patrick Matthews
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I am laughing a little at some of the responses.. whatever you do, be it building a house, buying a boat, or choosing a database, don't let your needs assessment or evaluation get clouded with "BIASed" input from others. First and foremost -- define your need!!!! When defining you need, also define -- where will I go with this, and when I get there, am I willing to Forklift / Retrofit to a new environment / solution or do I want it to seamlessly scale, etc. etc. Plan - Plan - Plan. All solutions will work, if you apply them appropriately to the PLAN.

One thing I will say is that all tools have a purpose ... it's up to you to determine what your requirements are and from that standpoint --- determine the best possible solution for your needs.

What I should have pointed out in my original post, is that databases could be broken up into different "classes" for the purpose of this discussion. Some of the experts in this thread can elaborate a little better than me, but you could clearly define where an application would best be utilized in different scenarios. I'll take a stab at posting a few examples from my prospective -- Oh and one last note, I worked with a National Bank a few years back and they developed an ACCESS Database for the purpose of a paperless loan processing system. We turned over 130 applications a day, and generated over 50 home equity loans on a daily basis. The application was eventually replaced with a 1.2 million dollar application. The home grown application sustained us for over 12 months untile we completed the deployment of the "Enterprise" class database application. My point is that the lower realm application served it's purpose and effectively until we were prepared to move to the higher-end enterprise class application -- with a price tag of course.

Desktop Class: (run on local machine.. share files, reports, etc. yes it's true, some people do this!)
access
excel
datapoint
etc. etc.

local / workgroup class : (single standalone servers)
access (very limited capability)
mysql (maybe? more web/enterprise class?)
filemaker(pro)
advantage
others

enterprise class : (large applications, not all web enabled, clustering, server farms)
oracle
db2
sql
mysql (yes no? -- experts please?)
Others' I am sure....