[KB8592] ESET Inspect database migration for Microsoft SQL Server

Issue

• Prerequisites
• Migrate ESET Inspect Server database using command prompt

Solution

Prerequisites 

• Source and target SQL Server instances must be installed
• The target SQL Server instance must have at least the same version as the source instance.
• Downgrading is not supported

Follow the instructions below to migrate the ESET Inspect Server database between different SQL Server instances (this also applies when relocating to a different SQL Server version or when migrating to a SQL Server hosted on a different machine):

1. Stop the ESET Inspect Server service.
   
   
2. Run the Command Prompt application and use the following command:
   
   SQLCMD -U sa -S localhost -Q "BACKUP DATABASE enterpriseinspectordb TO DISK = N'C:\USERS\public\BACKUPFILE.bak'"
   
   
3. Copy the created backup file to the designated MSSQL machine and run the following command to restore the backup of the database on the designated machine:
   
   SQLCMD -U sa -S localhost -Q "RESTORE DATABASE enterpriseinspectordb FROM DISK = N'C:\USERS\public\BACKUPFILE.bak'"
   
   
4. Enable TCP/IP on the target machine.
   
   
5. Ensure the Firewall on the source machine is set up to allow incoming and outgoing communication at port (by default 1433, or changed by the user during ESET Inspect Server installation process).
   
   
6. Run the ESET Inspect Server service if the target MSSQL Server machine keeps the same IP address as the Source one.
   
   
7. When you migrate the database to another server (Microsoft SQL IP or port will be changed), you have to set up the ESET Inspect Server again by using the "Repair/Change" option in the Installer. Leave all the settings, but change the database settings such as Microsoft SQL IP port.