Bosch Appliances 3.5 manual 12: Database tab

Praesideo 3.5 Installation and User Instructions 11 Optional Software

en 452

56.7.4 Database

56.7.4.1Overview

On the Database tab (see figure 56.12), the properties of the logging database can be defined.

figure 56.12: Database tab

56.7.4.2 Recent events

Use the Recent events block to define the number of recent events that is displayed in the Logging Viewer (see section 57.6.2.3).

56.7.4.3 Database file

Use the controls in the Database file block to define:

•The location of the logging database. This can be entered in the upper text box.

Note

For experts only: the logging database is a Microsoft® Access file, which also can be opened with Microsoft® Access. If for any reason the database becomes corrupted and the Logging Server is not able to access the database, the database can be repaired with Microsoft® Access.

Close the Logging Server application. Open the database with Microsoft® Access. Select: Tools > Database utilities > Compact and Repair database.

•The critical size of the logging database. When the critical size is reached, the Logging Server displays the following message (see section 56.5.2): The Logging

Server database has reached its critical size. Please decrease the logging expiration periods.

It is possible to make a back-up of the logging database (even if the Logging Server is running). When a back-up is made of a running Logging Server, it is advised to wait for a moment at which a low number of events is expected (i.e. when there are almost no running calls). Events that occur while the back-up is made will not be copied to the logging database. However, events that occurred during the back-up process can be viewed with the standard Windows Event Viewer (Start > Settings > Control Panel > Administrative Tools > Event Viewer).

56.7.4.4 Flush events

Use the controls in the Flush events block to flush events from the logging database. Proceed as follows:

1 If the fault events must be flushed from the logging database, put a check mark in the Fault events check box.

2If the general events must be flushed from the logging database, put a check mark in the General

events check box.

3 If the call events must be flushed from the logging database, put a check mark in the Call events check box.

4Click the Flush now button to flush the selected types of events from the logging database.

•If the Move expired events to overflow file field of the selected type of events on the Logging Expiration tab (see section 56.7.3) contains a check mark, the selected type of events are flushed to an overflow file.

•If the Move expired events to overflow file field of the selected type of events on the Logging Expiration tab (see section 56.7.3) does not contain a check mark, the selected type of events are deleted from the database.

Note

When the database is flushed and the Logging Server is started again, the database is filled with the events that are retrieved from the enabled network controllers. Each enabled network controller keeps an internal list of up to 200 events of each type. Use the File Transfer application to clear the internal list (see section 36.6).

Bosch Security Systems 2011-02