Selecting a DBMS for Administration Server

When selecting the database management system (DBMS) to be used by an Administration Server, you must take into account the number of devices covered by the Administration Server.

The following table lists the valid DBMS options, as well as the recommendations and restrictions on their use.

Recommendations and restrictions on DBMS

DBMS

Recommendations and restrictions

SQL Server Express Edition 2016 or later

Use this DBMS if you intend to run a single Administration Server for less than 10,000 devices, and if you are not going to use the Application Control component for managed devices.

Concurrent use of the SQL Server Express Edition DBMS by Administration Server and another application is strictly forbidden.

Local SQL Server edition, other than Express, 2016 or later

No limitations.

Remote SQL Server edition, other than Express, 2016 or later

Only valid if both devices are in the same Windows® domain; if the domains differ, a two-way trust relationship must be established between them.

Local or remote MySQL 5.5, 5.6, or 5.7 (MySQL versions 5.5.1, 5.5.2, 5.5.3, 5.5.4, and 5.5.5 are no longer supported)

Use this DBMS if you intend to run a single Administration Server for less than 10,000 devices, and if you are not going to use the Application Control component for managed devices.

Local or remote MySQL 8.0.20 or later

Use this DBMS if you intend to run a single Administration Server for less than 50,000 devices, and if you are not going to use the Application Control component for managed devices.

Local or remote MariaDB (see supported versions)

Use this DBMS if you intend to run a single Administration Server for less than 20,000 devices, and if you are not going to use the Application Control component for managed devices.

PostgreSQL, Postgres Pro (see supported versions)

Use one of these DBMS if you intend to run a single Administration Server for less than 50,000 devices, and if you are not going to use the Application Control component for managed devices.

If you are using SQL Server 2019 as a DBMS and you do not have cumulative patch CU12 or later, you have to perform the following after installing Kaspersky Security Center:

  1. Connect to SQL Server using SQL Management Studio.
  2. Run the following commands (if you chose a different name for the database, use that name instead of KAV):

    USE KAV

    GO

    ALTER DATABASE SCOPED CONFIGURATION SET TSQL_SCALAR_UDF_INLINING = OFF

    GO

  3. Restart the SQL Server 2019 service.

Otherwise, using SQL Server 2019 may result in errors, such as "There is insufficient system memory in resource pool 'internal' to run this query."

See also:

Hardware requirements for the DBMS and the Administration Server

Selecting a DBMS

Page top