Maintaining Atomic Scope

Tracking Data Purging

In Atomic Scope, Purging is done by SQL Server Stored Procedures. Purging will happen every 4 minutes once and It will delete 5000 data (configurable count upto 5000) each time.

General data purging

Monitoring and diagnostics logs will come under general settings. This purging will happen every 1 hours once and it will delete 10000 data each time. It is not configurable

The following stored procedures are used for purging.

1. Purge Tracking Data - Purge_TrackingData
Each run the Purge_TrackingData stored procedure deletes the top 5000 records of your tracked data from the tables Tracking_MainActivity, Tracking_StageActivity, Tracking_MessageArchive, Tracking_Exception and the dynamic tracking properties table.

2. Purge Monitoring Alert History -Purge_Monitoring_AlertHistory
The Purge_Monitoring_AlertHistory stored procedure deletes the top 10000 records of your tracked data from Monitoring_AlertHistory table each run.

3. Purge History - Purge_PurgeHistory
The Purge_PurgeHistory stored procedure deletes the top 10000 records of your Purge_History data each time.

4. Purge Log - Purge_Log
The Purge_Log stored procedure deletethe top 10000 records of your purge log data each time, and insert purging execution details in Purge_History table.

Configure Purging settings

The settings can be configured in the purging settings section. User can configure data count upto 5000 in each cycle for tracking data.

Purge by business process configuration enables purging to be done in accordance with the business process and transaction level purging configuration.

The user can plan out the duration they would like to purge for. Therefore, it will happen during those specific hours.It must be at least three hours.

Purging alerts enabled will send the alerts specified in system alerts in application settings. It will help the user in understanding the errors and warnings that occur during the purging process.

Purging Health Check Status Info

Health Check status information shows up in the top bar of Atomic Scope. It shows database configuration size limit status and purging executed status details information.

• The Database size limit is configured by default as 20GB in Config_AppSettings table. The value can be found under the ApplicationKey column name as DBSizeLimit. The Atomic Scope Windows NT service runs every 5 minutes once and if the database is ached to the configured size limit, the database size limit exceed status is updated.

• Purging runs once every 4minutes. If data purging is not running in last 4 minutes due to any issue we will notify purging execution failed status as shown in the below image.

Below is the update query statement for Database size limit

UPDATE [dbo].[Config_AppSettings] SET [ApplicationValue]='20' WHERE [ApplicationKey]='DBSizeLimit'

Service health check status info

Service health check status information shows up in the top bar of Atomic Scope. It shows the server details like server status, name of the server and last execution time.