Database strengths & weaknesses


I am required to draw up a spec detailing the relative strengths and weaknesses of possible databases that could be utilised by a web application i am implementing.

The company wish to see details such as scalability, security and cost - along with technical attributes the main db's on the market possess.

Im looking to contrast and find limitations for the adoption of the following databases.  Please read this with a viewpoint that the db will be for small - medium business use.


MS SqlServer



Any help would be greatly appreciated

thanks in advance

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Try reading this, published in 2001 but still current.

Personally I would suggest for small databases (max 10,000 records/10 tables) without too much multi-user connection that MS Access is a good tool becaseu of the ease of development that it has.  The drawback is less functionality and performance issues when networked, especially with multiple users, not enough to cause problems for 2/3 users but will be unusable at 15 (concurrent).

For larger, more complex and wider used databases go with eitehr SQL Server 2000 or Oracles latest RDB offering.  The both offer all the functions you could ever want, decent proffesional support and sustainability in that both will be around for many years yet.

If you have need for a larger database and cannot afford MS SQL Server or Oracle then MySQL is another option, as it is a public open source project the database is free to download, however technical support is non-existant in an official capacity although a number of companies offer good consultancy support privately.  I would only consider this for a serious business application if none of the afformentioned three are possible.

Lastly if you want to implement this system yourself either get an expert in to help you or look at geting some training yourself (not a database fo dummies book).

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Tom KnowltonWeb developerCommented:
No comment has been added lately (217 days), so it's time to clean up this TA.
I will leave a recommendation in the Cleanup topic area for this question:

RECOMMENDATION: Award points to IeuanJ http:#7987647

Please leave any comments here within 7 days.

-- Please DO NOT accept this comment as an answer ! --


EE Cleanup Volunteer
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.