Technical FAQs

Ask a Question

How to identify oversized historical granules in ClearSCADA

Issue

ClearSCADA is designed to support maximum 4 historic updates per minute per point. Exceeding the limit will create historic files larger than 1.3MB and might affect the performance of the system. It is recommended to remove oversized historic files (granules) and to analyze relevant points historic storage rate.  

Product Line

ClearSCADA (EcoStruxure™ Geo SCADA Expert)

Environment

Windows OSes

Resolution

Before making any changes it is highly recommended to make a backup of complete database.

Oversized historic files can be identified using SQL Query (embedded list or in the Query Pad) and command line.
Both ways are suitable, however command-line could be modified to move the identified granules to another location in addition to the search routine.
Code can be copied to any Simple Text Editor and saved with .cmd extension.
1. Check the location of the Historic Data (in the Server Administration tool) and copy the path.

By default ClearSCADA stores Historical Data to C:\ProgramData\Schneider Electric\ClearSCADA\Database\History

2. Create a Folder and create a text file with the following content:

forfiles /P "<Historical Data Location >" /S /C "cmd /c if @fsize gtr 1363149 echo @path @fsize" > "<path to created folder>\listOfOversizedGranules.txt"
PAUSE

3. Replace the text in <> accordingly.
4. Save the file with .cmd extension.
5. Execute the command line file under the Administrator permissions.

For more details about forfiles command please check Microsoft TechNet
Removing granules from the ClearSCADA Database requires servers shutdown. In case of Redundant configuration, historical files can be removed on one machine. This machine has to be started first, Standby will delete oversized granules during the synchronization procedure.
Was this helpful?
What can we do to improve the information ?