[Other doc versions]
[Doc downloads (PDF, HTML, XML)]
This page provides information about using Stash with an external database.
Stash ships with an embedded database that it uses straight out-of-the-box, with no configuration required. This is great for evaluation purposes, but for production installations we recommend that you use one of theexternal databases.
Stash supports the following external databases:
Please refer to Supported platforms for the versions of external databases supported by Stash.
You can configure Stash to use an external database using:
On this page:
Stash ships with an embedded database that is great for evaluation purposes, but for production installations we recommend that you make use of one of the supported external databases, for the following reasons:
You can connect Stash to an external database when you run the Setup Wizard, immediately after starting Stash for the first time. See Installing Stash on Windows or Installing Stash on Linux and Mac for more information.
If you have been using Stash for a while using the embedded database, you can migrate to an external database, as described below.
You can use the Database Migration Wizard to migrate Stash from the embedded database to an external database, or from an external database to another external database. You need to have created the DBMS (such as MySQL) that you wish to migrate the Stash data to before running the Migration Wizard.
To run the Database Migration Wizard:
exportdirectory. This is used during the migration and is kept for diagnostic purposes in the case of an error. You may remove this after migration but it may reduce Atlassian Support's ability to help you in the case of migration issues.
You can edit the database password if needed after migration.