Database requirements

Studio requires a relational database to store configuration and state, including component configuration, user permissions, and system settings. All Studio instances must be able to connect and write to the same database.

Studio supports the following types of databases:

Oracle 11g or 12c
MySQL 5.5.3 or higher (this includes CDH's default MySQL database)

Note: BDD does not currently support database migration. If you decide to switch to a different type of database later on, you must uninstall the software and reinstall with a new database instance.

If you are installing BDD in a production environment, you must create the following prior to installation:

A database of one of the types listed above
A database username and password
An empty schema

When creating the database, be aware of the following:

MySQL databases must use UTF-8 as the default character set.
The name of the schema is arbitrary, but by default it is studio.

Sample commands for creating Oracle and MySQL database users and schemas are available in Sample commands for a production database.

Demo environment database requirements

If you are deploying to a demo environment, you can use one of the databases listed above or a Hypersonic (HSQL) database.

Hypersonic is an embedded database running inside of the JVM. It is useful for getting Studio up and running quickly, but cannot be used in a production environment due to performance issues and its inability to support multiple Studio nodes.

Important: If you deploy to a demo environment using a Hypersonic database and later decide to scale up to a production environment, you must reinstall BDD with one of the supported MySQL or Oracle databases listed above.