1. Support Center
  2. Documentation
  3. Enterprise Edition
  4. Getting started
  5. Setting up the external DB

Setting up the external database

Note: This process is only relevant if you plan to use an external database rather than the embedded one provided with Burp Suite Enterprise Edition. If this is your first time setting up Burp Suite Enterprise Edition, remember you can always start with the bundled database and migrate to an external database later.

If using an external database, you will need to create a database schema for Burp Suite Enterprise Edition to use. Please follow the instructions below for your database type.

The set-up script will create two users, called beserver and beagent. You should replace the passwords specified in the script with your own strong passwords. Keep a record of the connection details for the external database ready to provide during installation.

MariaDB / MySQL

Setup script: CREATE DATABASE burpenterprise;
CREATE USER 'beserver'@'%' IDENTIFIED BY '********';
CREATE USER 'beagent'@'%' IDENTIFIED BY '********';
GRANT ALL PRIVILEGES ON burpenterprise.* TO 'beserver'@'%' WITH GRANT OPTION;
JDBC URL format: jdbc:mysql://{server address}:3306/burpenterprise

PostgreSQL

Setup script: CREATE DATABASE burpenterprise;
CREATE USER beserver PASSWORD '********';
CREATE USER beagent PASSWORD '********';
GRANT ALL ON DATABASE burpenterprise TO beserver;
JDBC URL format: jdbc:postgresql://{Server address}:5432/burpenterprise

Microsoft SQL Server

Setup script: sp_configure 'contained database authentication', 1;
RECONFIGURE;
create database burpenterprise containment=PARTIAL;
use burpenterprise;
create user beserver with password='********';
create user beagent with password='********';
alter role db_owner add member beserver;
JDBC URL format: jdbc:sqlserver://[serverName]:1433;databaseName=burpenterprise

To support password-based logins, you need to ensure that the "Windows Authentication and SQL Server Authentication" option is enabled for the installation. This option is sometimes referred to as "Mixed Mode Authentication".

Oracle

Setup script: CREATE TABLESPACE burpenterprise_tabspace DATAFILE 'burpenterprise_tabspace.dat' SIZE 100M
  AUTOEXTEND ON;
CREATE USER beserver DEFAULT TABLESPACE burpenterprise_tabspace QUOTA UNLIMITED ON
  burpenterprise_tabspace IDENTIFIED BY ********;
GRANT CREATE PROCEDURE, CREATE SEQUENCE, CREATE SESSION, CREATE TABLE, CREATE TRIGGER,
  CREATE SYNONYM, CREATE PUBLIC SYNONYM TO beserver;
CREATE USER beagent IDENTIFIED BY ********;
GRANT CREATE SESSION to beagent;
JDBC URL format: jdbc:oracle:thin:@//[serverName]:1521/[instanceId]