Wednesday, January 7, 2009

What to consider when choosing a database

Gints Plivna at has some great advice on what factors you are needing to consider when choosing a database. I am going to attempt to “Cliff Note” the article for convenience . Click here to view the full article.

How robust is the system needing to be?

A Geo Metro cant perform as a Power Stroke Ford F-350 can with how much it can carry and how fast it can move. If you are expecting the system to not to be strained or have to carry to much data then go with something that will perform like the Geo, but if you are expecting high volume and a lot of strain then go with the F-350.

Will it work with the existing system?

Lets continue to think of the database as a car and now your system as the garage. Can your new car fit in your old garage? Or are you going to have to build a new garage for your new car? You need to make sure that what you already have in place is compatible with what you are going to implement.

What will the cost benefit be?

If its going to cost to much to keep the system up and hire someone to maintain the system then it may not be in your best interest to upgrade to a new system. However if you are able to do most of the work yourself, find forums, and other useful tools that are free then it could be beneficial to you to implement the system.

Keep these three questions in mind when you are thinking about upgrading or starting out with a new database.


Kevin said...

Who is this guy and why is he qualified to comment on databases.

Gints Plivna said...

On the one hand see this:

On the other hand why does it matter and isn't better just to make reasonable pros and/or cons about the subject?

Kevin said...

Experts carry more weight than a novice; a senior Oracle admin with 20 years of experience has more experience to draw on. This is why a senior DBA will make $100 k and novice $20 k.

Gints Plivna said...

Kevin, in order not to make any other irrelevant comment here I wrote a post in my blog.