Database Configuration

Configure an external database for JFrog Artifactory. Supported databases include PostgreSQL, Oracle, MySQL, MariaDB, and Microsoft SQL Server, with PostgreSQL recommended for all new deployments.

JFrog Artifactory supports the following databases, depending on your requirements:

⚠️

Warning

The embedded Derby database has restricted functionality that can impact the performance and resilience of your Artifactory instance. JFrog highly recommends against using Derby for Artifactory production environments.

For more information about the supported versions of the database, see Artifactory Database Requirements.

JFrog Recommends Using PostgreSQL

JFrog recommends using an external PostgreSQL database in your production instances. JFrog also includes a PostgreSQL build with the installers.

All other JFrog products support only PostgreSQL, so using PostgreSQL with Artifactory simplifies your infrastructure.

Starting from Artifactory 7.84.7, new Artifactory installations support only PostgreSQL in the default installation mode. Artifactory does not start unless you configure system.yaml to support a non-PostgreSQL database.

shared:
  database:
    allowNonPostgresql: true
    type: <database type>

Artifactory supports the following modes of operation:

  • Metadata is stored in the database, and the artifacts are stored on the file system (this is the default and recommended configuration).
  • Metadata and artifacts are stored as BLOBs in the database.

Artifactory uniquely stores artifacts using checksum-based storage. For more information, see Checksum-Based Storage.

Accessing a remote database

When using an external database, use a reliable, stable, and low-latency network connection to ensure proper functioning of your system.

When using a full-DB configuration, we strongly recommend high bandwidth to accommodate the transfer of large BLOBs over the network.