Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Always i was using MySQL or PostgreSQL for my projects such as Web/Desktop apps. I had data loss few times and thanks to old backup i was always up and running.

But for a recent project for Airport, i have to use something which never ever can lose its data at-least not database until it has power in the circuit..

So i am thinking DB2 should be the best for such risk less missions? Any idea or hints.

Thanks in advance.

share|improve this question
Don't forget vendor support when you are considering HA - who do you trust to help you out 24/7 when the chips are down, and how much can you afford to pay for that comfort. – Jack Douglas Nov 12 '11 at 11:29
PostgreSQL is well known for it's reliability. If you lost some data, it's unlikely it's PostgreSQL fault. PostgreSQL and DB2 are on parr when it comes to reliability. – Frank Heikens Nov 17 '11 at 20:13
up vote 15 down vote accepted

All of the platforms you have mentioned can run close to zero data loss configurations. All of them could be deployed in a configuration that will fail.

Platform choice is one part of the puzzle. It will be your implementation of the platform that determines whether or not your requirements are met.

In reality, high availability and disaster recovery are a trade off between uptime, Recovery Point Objective, Recovery Time Objective and cost.

Zero data loss and zero downtime is expensive, complicated to setup and complicated to maintain. There is no free lunch.

share|improve this answer

I would just add that since the question was answered, Postgres-XC has been released. It is basically an open source fork of Postgres which allows for Teradata-style clustering which offers both high availability and write extensibility. I would expect this to be the preferred approach in very high-reliability, high throughput environments.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.