|
Dr.Web Server database structure is available in the form of a separate manual of the same name. The document can be opened from the Support section in Dr.Web Security Control Center. |
As a database for Dr.Web Server you can use the following variants:
•embedded DB;
•external DBMS.
Embedded DB
When setting up access to the embedded DB for storage and processing of data, use the parameters described in the table below.
Embedded DB
Name |
Default value |
Description |
DBFILE |
database.sqlite |
Path to the database file |
CACHESIZE |
2048 |
Database cache size in pages |
PRECOMPILEDCACHE |
1048576 |
Cache size of precompiled SQL operators (in bytes) |
MMAPSIZE |
•10485760—for UNIX, •0—for Windows |
Maximum size of the database file (in bytes) that is allowed to be mapped into process address space at a time. |
CHECKINTEGRITY |
QUICK |
Verify integrity of the database image at Dr.Web Server startup: •FULL—full check for any errors concerning UNIQUE, CHECK, and NOT NULL constraints, malformed records, missing pages or index inconsistencies; •QUICK—fast check option, with no regards to constraint errors or index inconsistencies; •NO—integrity check is disabled. |
AUTOREPAIR |
NO |
Automatically restore corrupted database image at Dr.Web Server startup: •YES—the database image restoration is initiated every time Dr.Web Server starts, •NO—automatic restoration is disabled. |
WAL |
YES |
Use Write-Ahead Logging: •YES—true, •NO—false. |
WAL-MAX-PAGES |
1000 |
Max number of “dirty” pages. When reached, the pages will been written to disk. |
WAL-MAX-SECONDS |
30 |
Max time in seconds that the page writing to disk is delayed for. |
SYNCHRONOUS |
FULL |
Mode of synchronous logging of changes in the database to the disk: •FULL—fully synchronous logging to the disk, •NORMAL—synchronous logging of critical data, •OFF—asynchronous logging. |
The SQLite3 DB is provided as the embedded DB.
External DBMS
The following database management systems may be used to manage the external database for Dr.Web Server:
•MySQL, MariaDB. The settings are given in A4. Using the MySQL DBMS.
•Oracle. The settings are given in A2. Setting Up the Database Driver for Oracle.
•PostgreSQL. The settings are given in A3. Using the PostgreSQL DBMS.
|
DBMS based on PostgreSQL (PostgreSQL Pro, Jatoba, and others) are supported. |
•Microsoft SQL Server/Microsoft SQL Server Express. To access these DBMSs, an ODBC driver may be used (setup of the parameters of the ODBC driver for Windows is given in A1. Setting Up the ODBC driver).
|
Microsoft SQL Server 2008 and later is supported. Microsoft SQL Server 2014 and later is recommended to use.
Microsoft SQL Server Express DB is not recommended for an anti-virus network with a large number of stations (100 and more).
If the Microsoft SQL Server is used as an external DB for Dr.Web Server under a Unix-like OS, the proper operation via the ODBC with FreeTDS is not guaranteed.
If warnings or errors occur in Dr.Web Server interaction with Microsoft SQL Server DBMS via the ODBC, please make sure that you are using the latest available DBMS version for this edition. Learn how to determine the update level on the following Microsoft Corporation page: https://learn.microsoft.com/en-US/troubleshoot/sql/releases/download-and-install-latest-updates. |
|
To reduce the number of deadlocks when using Microsoft SQL Server DBMS with the default transaction isolation level (READ COMMITTED), it is recommended that you enable the READ_COMMITTED_SNAPSHOT option by running the following SQL command: ALTER DATABASE <database_name> The command above must be run in implicit transaction mode and with a single existing connection to the database. |
Comparison Characteristics of Embedded DB and External DBMS
|
The embedded DB is intended for use in networks where about 400–600 stations are connected to Dr.Web Server. If the hardware configuration of the computer on which Dr.Web Server is installed and the load level of other executing tasks permit, between 1000 and 1500 stations can be connected. Otherwise, you must use an external DB. Depending on the configuration and the load level of the computer running Dr.Web Server, the external DB may be used on the same or on a dedicated computer. If you use an external DB in an anti-virus network with more than 10 000 stations, it is recommended to follow these minimal system and hardware requirements: •3 GHz processor CPU, •at least 6 CPU cores, •at least 4 GB RAM for Dr.Web Server and at least 8 GB RAM for the DB server, •Unix-like OS. |
When choosing between the embedded and external database, take into account the following parameters of the database types:
•In large anti-virus networks (of over 400–600 stations), it is recommended to use an external DB, which is more fault-resistant than the embedded DB.
•When using the embedded DB, you do not need to install third party software components. It is recommended mainly for the typical use of databases.
•The embedded database does not require DBMS administration skills and is a good choice for anti-virus networks of small and medium sizes.
•You may use an external database in case it will be necessary to work through a DBMS and access the DB directly. To facilitate access, standard APIs may be used, such as OLE DB, ADO.NET or ODBC.