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. It's 100% free, no registration required.

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

What is the difference between relational(MySql) and unrelational database(MongoDb)

share|improve this question

closed as too broad by RolandoMySQLDBA, Max Vernon, bluefeet, Mark Storey-Smith, Jon Seigel Oct 4 '13 at 3:10

There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question.

Please follow this blog which explains the difference – Peter Venderberghe Oct 3 '13 at 11:49

A relational database (the concept) is a data structure that allows you to link information from different 'tables', or different types of data buckets. A data bucket must contain what is called a key or index (that allows to uniquely identify any atomic chunk of data within the bucket). Other data buckets may refer to that key so as to create a link between their data atoms and the atom pointed to by the key.

A non-relational database just stores data without explicit and structured mechanisms to link data from different buckets to one another.

Check this link to learn more about MongoDb Link 1

Also check this link for more details Link 2

When should you use MySQL?

If your data structure fits nicely into tables and rows, MySQL will offer you robust and easy interaction with your data. If it's performance that is your concern, there is a good chance you don't really need MongoDB. Most likely, you just need to index your data properly. If you require SQL or transactions, you'll have to stick with MySQL.

When should you use MongoDB?

If your data seems complex to model in a relational database system, or if you find yourself de-normalizing your database schema or coding around performance issues you should consider using MongoDB. If you find yourself trying to store serialized arrays or JSON objects, that's a good sign that you are better off MongoDB. If you can't pre-define your schema or you want to store records in the same collection that have different fields, that's another good reason.

share|improve this answer

One follows th relational Theorem as per Coods theorem ('s_theorem).

Obviously Non-Relational databases do not follow this. They mostly store data as documents and have problems with fast extensive query and transformation, as well as not necessarily following ACID conventions.

Now, you want a "explain me databases in one sentence"? Sorry, will not happen.

share|improve this answer

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