Configuring a Metadata Database for On-Premise Bold BI Deployments

Overview

When deploying Bold BI in an on-premise environment, a metadata database must be configured during the application startup process. This database serves as the repository for Bold BI application information and is required for the successful operation of the platform.

This article explains the purpose of the metadata database, supported database platforms, configuration recommendations, and key considerations for on-premise Bold BI deployments.

What is a Metadata Database?

A metadata database is the backend repository used by Bold BI to store application-level information required to manage and operate the platform. During installation and startup, administrators must configure a supported database that Bold BI can use to maintain this information.

The metadata database stores information such as:

• User and group information
• Dashboard definitions
• Categories and permissions
• Site configuration settings
• Schedule information
• Application management details

As discussed during a customer onboarding session, the metadata database stores information related to the Bold BI environment itself, including users, dashboards, and operations performed within the server.

Why is a Metadata Database Required?

A metadata database is a mandatory requirement for every on-premise Bold BI installation.

During the application startup process, administrators must provide database connection details so Bold BI can create and manage its internal repository. Without a configured metadata database, the startup configuration cannot be completed.

The metadata database enables Bold BI to:

• Manage user authentication and authorization
• Store dashboard and category information
• Maintain permissions and security settings
• Handle schedules and administrative configurations
• Track application-level operations

Supported Database Platforms

Bold BI supports multiple database platforms for metadata storage.

Commonly supported database platforms include:

• Microsoft SQL Server
• PostgreSQL
• MySQL / MariaDB

Administrators can configure any supported platform during the application startup process based on their organization’s infrastructure requirements.

Configuration Recommendations

During deployment, Bold BI requires access to a supported database server for metadata storage.

While an existing database server can be used, it is recommended to create a dedicated database specifically for Bold BI metadata. This helps keep Bold BI application information separate from other application databases and simplifies administration and maintenance.

Recommended Approach

• Use a dedicated database for Bold BI metadata.
• Host the metadata database on a supported database platform.
• Restrict access to only the Bold BI application and authorized administrators.
• Include the metadata database in your regular backup strategy.
• Monitor database availability as part of your Bold BI deployment infrastructure.

Installation Workflow

A typical on-premise deployment involves the following steps:

1. Install Bold BI Server.
2. Launch the application startup wizard.
3. Create the System Administrator account.
4. Configure the metadata database connection.
5. Complete the remaining startup configuration.
6. Access the Bold BI portal and begin creating dashboards and data connections.

Example Deployment Scenario

Consider an organization deploying Bold BI on its own infrastructure:

• Bold BI Server installed on a Linux or Windows server.
• PostgreSQL configured as the metadata database.
• Users and administrators managed through the Bold BI portal.

In this deployment, Bold BI uses the PostgreSQL database to store application metadata such as users, permissions, dashboards, schedules, and configuration settings required for platform operation.

Best Practices

To ensure a reliable deployment:

• Create a separate database exclusively for Bold BI metadata.
• Perform regular backups of the metadata database.
• Follow your organization’s database security standards.
• Verify database connectivity before starting the application setup.
• Use supported database versions recommended by Bold BI documentation.
• Monitor database health and storage utilization as part of routine maintenance.

Conclusion

A metadata database is a required component of every on-premise Bold BI installation. It stores the application-level information needed to manage users, dashboards, permissions, schedules, and system configuration. Configuring a dedicated metadata database during installation helps ensure a clean, maintainable, and scalable Bold BI deployment.