Server Fault is a question and answer site for system and network administrators. 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

MySQL versus SQLite, for example? I understand that MySQL is harder to setup and configure... Would SQLite or another db be better suited in this regard?

share|improve this question
The question seems a bit more, ah, StackOverflow-ish. Have you looked there? – Avery Payne Jul 14 '10 at 22:50
up vote 0 down vote accepted

One key element to keep in mind: the license.

If you're going the commercial route with your application, bear in mind that either you need to distribute it under GPL2 (in which case you need to make the source available, among other things) or you need to get a license from Oracle (presumable against hard-earned, cold cash).

On the contrary SQLite is in the public domain so you're free to do whatever you want with it.

That being said sqlite is very easy to embed so it's likely to be the easiest route assuming its feature set and performance profile works for you.

share|improve this answer

If you want high portability, SQLite is the best. However, for operating with large data amounts, MySQL wins.

MySQL - needs setup - needs creating the schema while installing - very fast - many storage engines - has many useful things that are missing in SQLite

SQLite - only library needed (and language bindings in some cases, sqlite3-ruby for ex.) - portability - you can redistribute the database along with application - needs regular optimisation (VACUUM) - not too fast - almost unusable with many (100.000.000+) records

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.