Issue
- Install Microsoft SQL server
- TCP/IP communication
- Create a custom user with MSSQL Server Management Studio
- Move the database to a separate partition/machine
Solution
Install Microsoft SQL server
-
Start the MSSQL installer. Click Custom.
-
You can keep the default installation path or choose a different one. Click Install.
-
In the left-side menu, click Installation.
-
Click New SQL Server standalone installation or add features to an existing installation.
-
Accept the License terms and click Next.
-
Select the check box next to Use Microsoft Update to check for updates. Log into ESET Inspect On-Prem. To access ESET Inspect On-Prem from a different device, type the IP Address or hostname of the ESET Inspect Server in the browser.
-
In the Install Rules window, click Next.
-
In the Feature Selection window, select the check box next to Database Engine Services and SQL Client connectivity SDK (not valid for 2022). Click Next.
-
Click Next.
-
In the Server Configuration window, change the Startup Type for SQL Server Agent to Automatic and click Next.
-
In the Database Engine Configuration window, select Mixed Mode.
-
Type and confirm the password for the default sa user. You can use this user during the ESET Inspect Server installation process or create a custom user with sufficient privileges.
-
Click Add Current User.
-
Click Next.
-
Click Install.
TCP/IP communication
-
Open SQL Server Configuration Manager.
-
In the left-side menu, click SQL Server Network Configuration.
-
Click Protocols for MSSQLSERVER.
-
Ensure that the TCP/IP protocol is enabled.
-
In the left-side menu, click SQL Server Services.
-
In the right-side menu, right-click the SQL Server (MSSQLSERVER) service. From the context menu, select Restart.
-
In the right-side menu, right-click the SQL Server Agent (MSSQLSERVER) service. From the context menu, select Restart.
-
Verify in Windows Services that the SQL Server service is running, otherwise, the ESET Inspect Server will not work.
Create a custom user MSSQL Server Management Studio
-
Download MSSQL Server Management Studio and install it on the MSSQL Server machine.
-
Log in to the server.
-
In the Server type drop-down, select Database Engine. In the Server name drop-down, select the server name used on that server. In the Authentication drop-down, select Windows Authentication.
-
Click Connect.
-
In the left-side menu, right-click the Security folder. From the context menu, click New → Login.
-
Type the login name. Select SQL Server Authentication. Type and confirm the password.
-
Deselect Enforce password expiration.
-
In the left-side menu, click User Mapping. From the list of users mapped to this login, select a master login. In the Database role membership list verify public role is selected.
-
Click Securables. Click Search and select The server. Scroll down the Permission for list and select the check box next to Grant for View Server State.
-
In the left-side menu, click Server Roles. From the server roles list, select dbcreator and verify public is selected.
-
Click OK.
-
Install ESET Inspect Server with the new custom SQL user.
Move the database to a separate partition/machine
MySQL is the most crucial ESET Inspect Server component and can consume a lot of disk space. Due to operating system stability, we recommend moving the MySQL data and a temporary folder to the dedicated partition or a separate server machine.
-
Run SQL Server Management Center.
-
In Object Explorer, right-click the name of the server.
-
In the context menu, click Properties.
-
In the left-side menu, select Database Settings.
-
In the Database Default Location, change the Data path.
When calculating the required disk space, we track three folders:
- Database folder—The folder where MySql or SQL Server stores ESET Inspect Database
- Temporary database—The folder where MySql or SQL Server stores temporary tables
- The ESET Inspect Server data folder—
C:\ProgramData\ESET\Inspect Server\Serverfolder
If the database is installed on the same machine as the ESET Inspect Server, ESET Inspect On-Prem stops accepting new events when the following occurs:
- There is less than 3% of free space on the disk with the database folder
- There is less than 3% of free space on the disk with the temporary database folder
- There is less than 5% of free space on the disk with the ESET Inspect Server data folder
If the <%EIS%> data folder and temporary database folder are on the same disk, ESET Inspect On-Prem stops accepting new events if there is less than 10% free space on this disk.
If the database is located on the same machine as ESET Inspect On-Prem, there must be at least 10% free disk space where the temporary folder is for the Purge to work. Any problems with the database purge are displayed as red markers on the Events processed chart on the Events Load Dashboard’s tab.
