Appendix B. The Description of the DBMS Settings. The Parameters of the DBMS Driver

You can get the structure of Dr.Web Server DB via the init.sql script, located in the etc subfolder of Dr.Web Server installation folder.

As a database for Dr.Web Server you can use the following variants:

•embedded DBMS;

•external DBMS.

Embedded DBMS

When setting access to DBMS for storage and processing of data, use the parameters described in the table below for embedded DBMS.

Embedded DBMS (IntDB) parameters

Name

Default value

Description

DBFILE

database.sqlite

Path to the database file

CACHESIZE

2000

Database cache size in pages

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 following DBMS are provided as embedded:

•IntDB—modified version of SQLite 2.

•SQLite3—DBMS that is supported by the Server starting from version 10. SQLite3 has several advantages over the previous SQLite2 version, particularly:

▫more compact format for database file;

▫data bit capacity is increased: 64-bit rows identifiers are supported, text data is supported in both UTF-8 and UTF-16 formats;

▫BLOB data type is supported;

▫concurrent requests to the database are improved;

▫etc.

It is recommended to use SQLite3 if you select embedded database.

External DBMS

The following database management systems may be used to arrange the external database for Dr.Web Server:

•Oracle. The settings are given in Appendix B2. Setting Up the Database Driver for Oracle.

•PostgreSQL. The settings necessary for PostgreSQL are given in Appendix В4. Using the PostgreSQL DBMS.

•Microsoft SQL Server/Microsoft SQL Server Express. To access these DBMS, an ODBC driver may be used (setting up the parameters of the ODBC driver for Windows is given in Appendix B1. Setting Up the ODBC Driver).

With Microsoft SQL Server 2005 it is necessary to use the ODBC driver supplied with this DBMS.

Using of Microsoft SQL Server 2005 (SP4) and later is supported.

Microsoft SQL Server Express DB is not recommended for anti-virus network with a large number of stations (from 100 and more).

If the Microsoft SQL Server is used as an external DB for the Server under UNIX system-based OS, the proper operation via the ODBC with FreeTDS is not guaranteed.

If the Microsoft SQL Server is used as an external DB, it is necessary to use collation corresponding to Dr.Web Server language.

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.

How to determine updates level, you can find on the following page of Microsoft corporation: https://support.microsoft.com/en-us/kb/321185.

Comparison Characteristics

An embedded DB can be used, if at most 200-300 stations are connected to the Server. If the hardware configuration of the computer with Dr.Web Server and the load level of other executing tasks are permissible, up to 1000 stations can be connected.

Otherwise, you must use an external DB.

If you use an external DB and more than 10 000 stations are connected to the Server, it is recommended to perform the following minimal requirements:

•3 GHz processor CPU,

•RAM at least 4 GB for Dr.Web Server and at least 8 GB for the DB server,

•UNIX system-based OS.

When choosing between an embedded and external database, take into account the following peculiar parameters of DMBS:

•In large anti-virus networks (of over 200-300 stations), it is recommended to use an external DB, which is more fault-resistant than embedded DBs.

•The embedded DBMS is considerably faster than the external analogs and is recommended mainly for the typical use of databases.

•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.