The migration process for MS SQL Server

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. A downgrade is not supported!

Using command prompt

1.Stop the ESET ESET Inspect Server service.

2.Run the Command Prompt application and use this command:


example

SQLCMD -U sa -S localhost -Q "BACKUP DATABASE enterpriseinspectordb TO DISK = N'C:\USERS\public\BACKUPFILE.bak'"

3.Copy created backup file to the designated MSSQL machine and run this command to restore the backup of the database on the designated machine:


example

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.Make sure that 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 ESET Inspect Server service in case the target MSSQL Server machine keeps the same IP address as the Source one.

7.When you migrate the database to another server (MS SQL IP or port will be changed), you have to re-setup the ESET Inspect Server by using the "Repair/Change" option in the Installer. Leave all the settings as they are, but change the database settings like MS SQL IP port.

For attribute meaning, please visit https://docs.microsoft.com/en-us/sql/tools/sqlcmd-utility?view=sql-server-2017.

The enterpriseinspectordb in the example is the default DB name created during the ESET Inspect Server installation process. If you used a different name for the DB, replace the one used in the example above.