Choosing an SQL Server ====================== Since Evennia uses `Django `_, most of our notes are based off of what we know from the community and their documentation. While the information below may be useful, you can always find the most up-to-date and "correct" information at Django's `Notes about supported Databases `_ page. SQLite ------ This is the default database used, and for the vast majority of Evennia installs it will probably be more than adequate. No server process is needed, the administrative overhead is tiny (as is resource consumption). The database will appear as a simple file (``game/evennia.db3``). It is not tested how well Evennia performs with SQLite under a heavier load, but it should probably be fine for most normal mud-related usage. **Note:** If you run Windows and for some reason need to use a third-party web server like Apache rather than Evennia's internal web server, sqlite is probably not be the best choice. This is due to the possibility of clashes with file-locking of the database file under Windows. Postgres -------- This is Django's recommended database engine, usable for all sites aspiring to grow to a larger size. While not as fast as SQLite for simple purposes, it will scale infinitely better than SQLite, especially if your game has an extensive web presence. MySQL ----- MySQL **may** be slightly faster than Postgres depending on your setup and software versions involved. Older versions had some peculiarities though, so check out Django's `Notes about supported Databases `_ to make sure you use the correct version. Others ------ No testing has been performed with Oracle, but it is also supported. There are community maintained drivers for `MS SQL `_ and possibly a few others (found via our friend, Google).