About Helix ALM databases

Helix ALM data is stored in Relational Database Management Systems (RDBMS). By default, Helix ALM uses SQLite as the native backend database, which does not require any additional configuration before or after installation. Oracle, PostgreSQL, and SQL Server are also supported, but a qualified database administrator (DBA) must manually install and configure these databases.

The following data is stored in databases. Each component must be stored in a separate database. For example, server data and projects cannot be stored in the same database.

• Helix ALM Server—Each server has a server database, which stores configuration information.
• Helix ALM projects—Project databases contain all project information, including items (e.g., issues, requirements, test cases), local customers and users, filters, test configurations, security groups, and reports. If you use native database format, each project is automatically stored in its own database. If you use another RDBMS, you can store multiple projects in the same database or distribute projects between different RDBMS databases.
• Helix ALM License Server—Each license server has a database, which stores all license server data. See the License Server help for information.

When installing the Helix ALM Server, a SQLite server database file (ttserv.db) is created in the TTServerDb directory in the Helix ALM application directory. After installation, you can use this server database as is or use the server admin utility to convert it to a different RDBMS type, such as SQL Server. You can also store new projects in other RDBMS databases or convert existing native project databases to a different RDBMS type. You must create empty databases and add RDBMS connections before storing data in them. See Setting up RDBMS databases.

Tip:  For information about the differences between native and other RDBMS database formats, see Choosing a Helix ALM database format .