Figure 38, Chronicle server database usage window – Innotech Chronicle User Manual
Page 29
Chronicle Installation Instructions
Page 29
© Mass Electronics Pty Ltd 2012
Edition 3.1 dated 31/03/2014
Modifying the Database Reporting/Trending space allocation
Figure 38: Chronicle Server Database Usage Window
Click Edit in the Usage section of the Server settings Advanced tab to edit the Server Database usage.
You may adjust the amount of storage dedicated to Trending and Reporting. (Reporting is the
Priority) Adjust as required and press OK to save the settings. Keep in mind that Trend data should
only really be kept for as long as a Service contractor/Building Manager may need to view any historic
data to perform any troubleshooting.
Trend Data then works on a “first in, first out” scenario, and once the designated space for Trending
is used, the oldest data will be replaced with the newest to give a “sliding window” effect. With clever
management, this will reserve the majority of the database for Reporting which will then allow the
maximum amount of Historic Data to be saved.
Click Edit to open the
Chronicle Server Database
Usage Window.
Modify the details as required.
Storage Remaining based
on the settings below.
When allocating the database usage, you should note that large Trending allocations will drastically reduce the
performance of applications which use the database (Trends, ATOM etc). In most cases, 90 days (3 months) Trending
allocation should be adequate without degrading performance.
IMPORTANT
The amount of storage allocated to logged data is limited to 4gb if you do not use a Chronicle dongle. The allocated
storage increases to 10GB if a Chronicle dongle is used. The 10GB option is limited to a maximum allocation of 4GB
for reporting. If the database is downgraded, Chronicle will retain Reporting point data up to a maximum of 3.96GB.