Logging and SQL Server databases
SQL Server databases and storage of data
XProtect Incident Manager has its own SQL Server database named Surveillance_IM. The Surveillance_IM SQL Server database stores information about all your incident projects, data added to the incident projects, and log entries with some of the user activities related to XProtect Incident Manager. All sequences–added to incident projects or not–are as always stored in your cameras' media databases on your recording servers' storages.
System log file for XProtect Incident Manager
To troubleshoot system errors, you can find the log file on the computer where you have installed the Management Server system component, in this location: C:\ProgramData\Milestone\XProtect Incident Manager\Logs.
When the system log file for XProtect Incident Manager becomes larger than 10 MB, the VMS copies and archives the file into an Archive subfolder. The VMS writes new log entries into a new system log file. If you have the necessary user permissions, you can change when the VMS archives the system log file. Change the value for the archive maxsize value in the C:\Program Files\Milestone\XProtect Management Server\IIS\IncidentManager\Web.config file.
Logging of user activity in Management Client and XProtect Smart Client
XProtect Incident Manager stores detailed records of user activity in SQL Server databases.
When administrators in Management Client create, enable, and edit incident properties, these activities are written to the log server's SQL Server database SurveillanceLogServerV2.
When operators of XProtect Smart Client create and edit incident projects, the activities are written to XProtect Incident Manager's own SQL Server database named Surveillance_IM, to the log server's SQL database SurveillanceLogServerV2, or to both SQL Server databases.
Where the activities are logged depends on the specific activity.
Who and where | Activity | Activity logged in | |
---|---|---|---|
Surveillance_IM | SurveillanceLogServerV2 | ||
Administrators in Management Client |
Define, edit, and delete all incident properties and settings related to XProtect Incident Manager. |
No | Yes |
Operators in XProtect Smart Client | Create and delete incident projects. Generate and print incident reports. | Yes | Yes |
Open and export incident projects. | Yes | No | |
Edit incident projects. For example, apply or change incident types, statuses, categories, and data, and add comments or information about calls. | Yes | No | |
Create and remove sequences. Add and remove sequences to/from incident projects. | Yes | No |
The Surveillance_IM database is located on the same SQL Server installation as the SQL Server database for the Management Server service. If you move the SQL Server database for the Management Server service, you must move the Surveillance_IM database to the same location. You can move and back up the Surveillance_IM database the same way as you do with other SQL Server databases.
See also Moving the management server and Change the location and name of a SQL Server database.