Rekall itself does not contain a database. Rather, it can access SQL databases such as MySQL and PostgreSQL via drivers. Since Rekall is really intended as a general-purpose front-end to these, it does not handle functions such as database creation and access control (although plugin modules to support specific SQL databases may become available).
Because of this, it is neccessary to set up a database which Rekall can use. The Orders database can be run on MySQL and XBase; as mentioned above, this can be installed within the database connection wizard which appears when you run Rekall. If you use the XBase version you do not need access to any shared resources, but to run the MySQL or PostgreSQL versions you will need access to a corresponding server to which you have access.
A few words are needed to avoid confusion over the use of the word database. We will use it in two ways. Firstly, it is used to refer to RDBMSs (Relational Database Management Systems) such as MySQL; the term server database will be used where needed to avoid ambiguity. Secondly, it is used to refer to the thing that a Rekall user will think of as a logically single database; here the term Rekall database will be used. Note that a Rekall database can access more than one server database.