CODEWITHSUNDEEP
mysqlsql-serverpostgresql
eflles
eflles

Reputation: 6846

Where to find a good reference when choosing a database?

I and two others are working on a project at the university.

In the project we are making a prototype of a MMORPG.

We have decided to use PostgreSQL as our database. The other databases we considered were MS SQL-server and MySQL. Does somebody have a good reference which will justify our choice? (preferably written during the last year)

Upvotes: 4

Views: 550

Answers (5)

Neall
Neall

Reputation: 27134

Postgresql has a page of case studies that you can quote and link to.

Really, any of the above would have worked for you. I personally like PostgreSQL. One solid advantage it has over MSSQL (even assuming you can get it for "free") is that PostgreSQL is non-proprietary. If you're going to introduce a dependency into your project (and re-inventing an RDBMS would be crazy), you don't want it to be a black box.

Upvotes: 0

conny
conny

Reputation: 10145

Someone recently recommended me wikivs.com: MySQL vs. PostgreSQL - it is a quite detailed comparison of those two, and might be of help to you.

Upvotes: 4

alexmac
alexmac

Reputation: 4201

All of these databases have their advantages and disadvantages. Which is better is dependent on:

Your teams experience
Your exact requirements
Your current environemnt e.g. whats your app written in and going to be hosted on?

SQL servers main problem is the cost unless you use express edition which has performance limitations however its very easy to use and has a number of good tools.

There is a comparison of the different sql versions at: http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx

You could then compare these with MySQL and PostGre.

If the purpose of this comparison is a theoretical one for your essay then you can reference web pages such as the microsoft link and compare performance, cost etc.

Upvotes: 1

Javier
Javier

Reputation: 62603

the most mentioned difference between MySQL and PostgreSQL is about your reading/writing ratios. If you read a lot more than you write, MySQL is usually faster; but if you do a lot of heavy updates to a table, as often as other threads have to read, then the default locking in MySQL is not the best, and PostgreSQL can be a better choice, performance-wise.

IOW, PostgreSQL scales better regarding to DB writes.

that's why it's usually said that MySQL is best for webapps, while PostgreSQL is more 'enterprisey'.

Of course, the picture is not so simple:

  • InnoDB tables on MySQL have a very different performance behaviour
  • At the load levels where PostgreSQL's better locks overtake MySQL's, other parts of your platform could be the bottlenecks.
  • PostgreSQL does comply better with standards, so it can be easier to replace later.

in the end, the choice has so many variables that no matter which way you go, you'll find some important issue that makes it the right choice.

Upvotes: 3

MarkR
MarkR

Reputation: 63548

Go with something that someone in your team has actual experience of using in production. All databases have issues which frequent users are aware of.

I cannot stress enough that someone in the team needs PRODUCTION experience of using it. Not using it for their homework, or to keep their list of CDs in.

Upvotes: 1

Related Questions