Select the tab
ESET PROTECT On-Prem – Table of Contents

Supported database servers and database connectors

Specify the database server and connector you want to use when installing the ESET PROTECT Server. You can use an existing database server running in your environment; however, it must meet the requirements below.

ESET PROTECT On-Prem 13.1 supports three types of database servers: Microsoft SQL Server, MySQL, and MariaDB.

Database server

Supported database versions

Supported database connectors

Microsoft SQL Server

Express and non-Express editions

2016, 2017, 2019, 2022*, 2025

SQL Server

SQL Server Native Client 10.0

ODBC Driver for SQL Server 11, 13, 17, 18

MySQL

8.0, 8.1, 8.4

9.0–9.4

The later 9.x versions are supported as long as they maintain backward compatibility with the listed versions.

MySQL ODBC Connector versions:

8.0.x, 8.1.x

9.2–9.6

MariaDB

11.8

The later versions are supported as long as they maintain backward compatibility with the listed versions.

MariaDB ODBC 3.1.22 Connector

* The ESET PROTECT On-Prem 13.1 All-in-one installer installs Microsoft SQL Server Express 2022 by default.

oUpgrading checks for previous SQL installations and offers an upgrade to SQL 2022.

oThe installer generates a random password for database authentication and stores it in %PROGRAMDATA%\ESET\RemoteAdministrator\Server\EraServerApplicationData\Configuration\startupconfiguration.ini.


Warning

Microsoft SQL Server Express (the free edition) has a 10 GB size limit for each relational database. We recommend using other Microsoft SQL Server editions than Microsoft SQL Server Express:

In enterprise environments or large networks.

If you want to use ESET PROTECT On-Prem with ESET Inspect On-Prem.

Database installation recommendations


Warning

ESET PROTECT Server does not use an integrated backup. We strongly recommend that you back up your database server to prevent data loss.

Do not install SQL Server on a Domain Controller. Install ESET PROTECT On-Prem on a different server or deselect the SQL Server Express component during installation. Use your existing SQL or MySQL Server to run the ESET PROTECT database.

If you intend to use a dedicated database user account that will only have access to the ESET PROTECT database, you must create a user account with specific privileges before installation. For more information, see the dedicated database user account. Additionally, you will need to create an empty database that will be used by ESET PROTECT On-Prem.

See the instructions to install and configure MySQL on Windows, MySQL on Linux, MariaDB on Windows and MariaDB on Linux to work properly with ESET PROTECT On-Prem.

Microsoft SQL Server on Linux is not supported. However, you can connect the ESET PROTECT Server on Linux to Microsoft SQL Server on Windows.

If you install the ESET PROTECT Server and Microsoft SQL Server on separate computers, you can enable encrypted connection to the database.

The cluster setup of the database on Windows environments is supported only for the Microsoft SQL Server, not for MySQL/MariaDB.

Database server hardware requirements

See the hardware and sizing instructions.

Performance recommendations

We recommend using the latest supported Microsoft SQL Server as your ESET PROTECT database for the best performance. While ESET PROTECT On-Prem is compatible with MySQL, using MySQL can negatively impact system performance when working with large amounts of data, including dashboards, detections, and clients. The same hardware with Microsoft SQL Server can handle significantly more clients than with MySQL.

You can decide whether to install an SQL database server on:

The same machine as the ESET PROTECT Server.

The same machine, but on a separate disk.

A dedicated server for the installation of an SQL database server.

We recommend that you use a dedicated machine(s) with reserved resources if you want to manage more than 10,000 clients.

Database

SMB customer

Enterprise customer

Clients limit

Windows

Linux

Microsoft SQL Express

(optional)

5,000

 

Microsoft SQL Server

None

 

MySQL

10,000

MariaDB

10,000