How to check and stop Event data filling up Building Operation Reports Server

[Product_Support]

Warning

Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance.

Issue

Log data is not being logged into SQL.

The Reports Server indicates that the database is full.  

This view will be shown when logging into the WebReports interface. If this chart is not shown, the PC is not running an Express edition of SQL.

Product Line

EcoStruxure Building Operation

Environment

Reports Server

Cause

In most instances, the data that quickly fills the SQL database are Events. Event data fills the SQL Database and prevents log data from passing to the Reports Server database. If the data has filled within a few days, this would indicate an issue, and contacting your local support is the best option here. The Process below allows the user to stop the reporting agent from passing specific information to the Reports Server.

If the data files are due to the amount of data stored, then an upgrade to the Standard/Full version of SQL is recommended.  

Resolution

To verify that the Events table is the likely cause of the SQL filling up, there are Standard Reports in the later versions of SQL.  The below example uses SQL Server version 13.x and shows the "Disk Usage by Top Tables."  

If the Standards Reports are not available, then use the following article Building Operation Reports SQL Database Full, for instructions on how to show the details for each table.

The Process below allows the user to stop the reporting agent from passing Event information to the SQL Database:

1. Download the latest SBO Reports Agent Config tool from the community.
2. Load the Tool onto the Reports Server PC.
   
3. Stop the Reporting Agent Using the Tool
4. Press F7 to get to the Advanced Agent Configuration Page
   
5. Change the numEventRecordToRead property to 0. This will prevent future event data from being written to the Reports Server database.
   
6. Press Ok
7. Under the Maintenance tab of the tool - there are two options under Events 
   1. Delete future events, alarms, and trends 
   2. Delete events and alarms older than...
      
8. Restart the Reporting Agent

This will stop any further Events from being passed through to the SQL Database.