For evaluation purpose, you can use an online database we provide.
Play SQL is not affiliated with Heroku and it doesn't guarantee their services suit your needs. However, we recommend them because they're internationally recognized as the best platform for software development.
If your Confluence instance uses MS SQL, Oracle or MySQL, it may not be easy for you to install PostgreSQL, which is required to store Play SQL's data. That's why we're happy to give you a temporary online database hosted by:
Heroku may be a trademark, it's not clear from their docs, but if it's true, well,
it's a trademark. Or maybe a registred trademark or ... well, do inform yourself and respect the trademark please.
The online database is only provided for your evaluation, because it costs us $9 per month. If you want to keep it, you can always take ownership of the Heroku database (and of the billing) or follow the instructions below to install it on your own servers.
You can click manually on the Synchronize button, or it will check every 12hrs whether the online database's credentials have changed.
Request the SQL back-up from us.
The name and owner is up to you.
Play SQL requires a full database for the data, because it uses 1 schema per Confluence space.
On Linux/Mac OS X, the command is:
psql databasename < the-backup.sql
It will import the data with your current user as the default owner. It will show errors because it tries to set the table ownership to the original user of the Heroku database, but you can safely ignore those errors.
Go to Confluence Administration > Play SQL > Databases (manual configuration) > General connection > Edit:
You can check that you can edit an existing table or create a new one in Confluence.
JNDI is recommended: Play SQL will be faster and you'll be able to control more details about the connection. It requires changing the server.xml file on the server and restarting. There explanations are provided on this page: Declaring a JNDI datasource for Confluence.
If you want to perform this process once for test, then you can reimport the data again to be in sync with the latest version from Heroku:
dropdb databasename createdb databasename psql databasename < the-latest-backup.sql