About using a different database

Studio uses a relational database to store configuration and state, such as component preferences, user permissions, system settings, and more.

By default, Studio uses Hypersonic (HSQL), which is an embedded database running inside the Java virtual machine. HSQL is useful for standing up a Studio instance very quickly, but must NOT be used in production due to performance issues and its inability to support clustered instances.

When changing to a different database, keep the following details in mind:

Studio ships with a portal-ext.properties file (in the portal distribution's root directory). You can modify this file instead of creating a new one.
Studio has been tested on MySQL and Oracle 11g. Other databases are expected to work but have not been explicitly tested.
When migrating to a new database, make sure that the current data does not conflict with the new database's schema. For example, different databases may have different constraints for column sizes.