Skip to main content
Version: 3.3

Database Installation

USP Manager stores its configuration data, runtime state, configuration versioning, and encrypted secrets in a database. Two options are available:

Embedded SQLite Database​

USP Manager ships with a built-in SQLite database. No preparation is required: when the database engine is set to sqlite, USP Manager creates and manages the database file automatically at the configured path.

The embedded SQLite database is intended only for evaluation and development. It is not recommended for production and not supported in high-availability deployments.

External Database​

External databases are required for production and high-availability deployments. USP Manager supports the following database engines:

Preparation Responsibilities​

In production environments, the database is normally provisioned by a database administrator (DBA) according to the organization's policies. The DBA decides the database (or schema) name, the account name and credentials, the storage, character set, backup strategy, and other operational parameters.

Requirements​

Provision a dedicated database (or schema) and a dedicated account for USP Manager. Avoid reusing administrative, superuser, or root accounts.

The account must be able to:

  • Connect to the database.
  • Create, alter, and drop tables, indexes, and sequences within its own schema. These privileges are used during the initial installation and during upgrades, when USP Manager creates or migrates its schema.
  • Read and write data in its tables during normal operation.

The exact grant syntax depends on the database engine, but in every case it is enough to grant the account full privileges on (or ownership of) its dedicated database or schema. This keeps the grant scoped to USP Manager's own objects, without any instance-wide or administrative rights.