Managing the SQL Server and databases

Changing the SQL Server and database addresses (explained)

When you install a system as a trial, or if you restructure a large installation, you may need to use a different SQL Server and database.

You can change the address of the SQL Server and database used by the management server and by the event server, and the address of the SQL Server and database used by the log server, the XProtect Incident Manager server and the IDP server. The only limitation is that you cannot change the management server and the event server's SQL addresses at the same time as the log server's SQL address. You can do it one after another.

You must change the SQL Server and database addresses locally via the Windows Registry on the computers where you have installed the servers. If your management server and event server are installed on separate computers, you must update the addresses on both computers.

You must copy the SQL databases before you proceed.

Change the log server's SQL Server and database

To change the SQL location for the Log Server, do the following:

Before making any changes to the registry, make a registry backup.

  1. Ensure that the user running the Log Server application pool is the owner (DBO) of the log server database.
  2. Update the connection string in the Windows Registry to include the new location and name of the log server. The value can be found and modified under:

    HKEY_LOCAL_MACHINE\SOFTWARE\VideoOS\Server\ConnectionString:

  3. Restart the Log Server via Windows Services.

The default database name is: SurveillanceLogServerV2.

Change the management server and the event server's SQL Server and database

To change the SQL location for the management server and the event server, do the following:

Before making any changes to the registry, make a registry backup.

  1. Stop the services and ensure that the user running the management server and the event server is the owner (DBO) of the database.

  2. Update the connection string in the Windows Registry to include the new location and name of the servers. The values can be found and modified under:

    HKEY_LOCAL_MACHINE\SOFTWARE\VideoOS\Server\ConnectionString:

  3. Restart the Management Server and the XProtect Event Server via Windows Services or from the tray icons in the notification area.

The default database name is: Surveillance.

The connection strings are: ManagementServer and EventServer.

If the event server is running on a different computer, make the same change there. The event server and the management server use the same database.

Change the XProtect Incident Manager server's SQL Server and database

Before making any changes to the registry, make a registry backup.

  1. Stop the service and ensure that the user running the XProtect Incident Manager server is the owner (DBO) of the database.

  2. Update the connection string in the Windows Registry to include the new location and name of the server. The values can be found and modified under:

    HKEY_LOCAL_MACHINE\SOFTWARE\VideoOS\Server\ConnectionString:

  3. Restart the Incident Manager from the IIS Manager.

The default database name is: Surveillance_IM.

Change the IDP server's SQL Server and database

Before making any changes to the registry, make a registry backup.

  1. Stop the service and ensure that the user running the IDP server is the owner (DBO) of the database.

  2. Update the connection string in the Windows Registry to include the new location and name of the server. The values can be found and modified under:

    HKEY_LOCAL_MACHINE\SOFTWARE\VideoOS\Server\ConnectionString:

  3. Restart the IDP from the IIS Manager.

The default database name is: Surveillance_IDP.