Milestone XProtect Express 2014 - Manual (Page 182)

Milestone XProtect ® Express 2014 Administrator's Manual
www.milestonesys.com 182 System maintenance
You can now begin to configure your system through its Management Application. For more
information, see Get your system up and running (on page 33).
Step 4: Restore alarms data in SQL Server Express database
Luckily, most users never need to restore their backed-up alarm data, but if you ever need to, do the
following:
1. In the Windows Start menu, open Microsoft SQL Server Management Studio Express.
2. Connect to a server. Specify the name of the required SQL Server, and connect using the user
account the database was created with.
3. In the Object Explorer on the left, expand SQL Server < Databases, right-click the
VIDEOOSDB database, and then select Tasks > Restore > Database...
4. In the Restore Database dialog, on the General page, under Source for restore, select
From device and click <Browse for more...>, to the right of the field. In the Specify Backup
dialog, make sure that File is selected in the Backup media list. Click Add.
5. In the Locate Backup File dialog, locate and select your backup file VIDEOOSDB.bak. Then
click OK. The path to your backup file is now listed in the Specify Backup dialog.
6. Back on the Restore Database dialog's General page, your backup is now listed under Select
the backup sets to restore. Make sure you select the backup by selecting the check box in
the Restore column.
7. Now go to the Restore Database dialog's Options page, and select Overwrite the existing
database. Leave the other options as they are, and then click OK to begin the restoration.
When the restore is finished, you see a confirmation.
8. Exit Microsoft SQL Server Management Studio Express.
Note: If you get an error message telling you that the database is in use, try exiting Microsoft SQL
Server Management Studio Express completely, then repeat steps 1-8.
Step 5: Restart the Event Server service
During the restore process, the Event Server service is stopped to prevent configuration changes
being made until you are done. Remember to start the service again:
1. On your surveillance system server, click Start > Control Panel > Administrative Tools >
Services.
2. Right-click the Event Server, click Start.
About the SQL Server Express transaction log and reasons for flushing it
Each time a change in the system's alarm data take place, the SQL Server logs the change in its
transaction log. The transaction log is essentially a security feature that makes it possible to roll back
and undo changes to the SQL Server Express database. The SQL Server by default stores its
transaction log indefinitely, and, therefore, the transaction log builds up more and more entries over
time.
The SQL Server's transaction log is by default located on the system drive, and if the transaction log
just keeps growing, it may in the end prevent Windows from running properly. Flushing the SQL