OneSight Administrator Guide

Troubleshooting Setup
the OneSight Server and then decide to move the OneSight database
to a remote SQL server, use the steps below.
To move the database, you will be using Enterprise Manager and
Query Analyzer, which are Microsoft SQL Server Client Utilities.
Note: This procedure assumes that the name of the OneSight
administrative user is “OneSightAdmin” in the database section of
the OSServer.properties file. The Onesight administrator’s name is
identified with the property Database.UserName in the
OSServer.properties file. If you changed this name, you must edit the
script file OneSightEmpirix\db\sp_CreateUsers.sql and replace all
occurrences of OneSightAdmin with the name of the OneSight
administrative user as it appears in the OSServer.properties file. You
must then execute this script file in a Query Analyzer window to
modify the stored procedure before executing the procedure in step
5 below.
1. Confirm that the remote SQL Server database you intend to use
has the same character set and sort order. The OneSight
database is configured as US English, dictionary sort-order,
case-insensitive.
2. Stop the Onesight service.
3. Use Enterprise Manager to back up the OneSight database (by
default, named OneSight). Move the database backup device
file, (OneSight_backup.bak, typically located in the mssql7\backup
folder) to the remote SQL server. If you do not see a backup file
with this name, use Enterprise Manager to check the path for
the OneSight_backup device.
4. Restore the database on the new server from the backup file.
Note: Make sure you restore the same version of backup that
you created on the other server. SQL Server supports multiple
backups in the same device file.
908 OneSight Administrator Guide