Studio database requirements

Studio requires a relational database to store configuration and state, including component configuration, user permissions, and system settings. If you install with multiple Studio instances, all of them must be connected to the same database.

BDD supports the following database types:
Note: BDD does not currently support database migration. If you decide to switch to a different type of database later on, you must reinstall BDD with a new database instance.
If you're installing BDD in a production environment, you must create the following:

If you're installing BDD in a non-production environment with the Quickstart option, you must use a MySQL database. For more information, see QuickStart Installation.

You can optionally use a clustered database configuration. For clustering, Oracle 11g uses RAC and MySQL has MySQL Cluster. Refer to the documentation for your database system for details on setting up a clustered configuration.

Additionally:

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

Demo environment database requirements

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

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

Important: If you install in a demo environment with 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.