- Overview
- Requirements
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite on EKS/AKS
- Migration options
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone product database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the migrated product connection strings
- Step 6: Migrating standalone Insights
- Step 7: Deleting the default tenant
- B) Single tenant migration
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Cleaning up the Task Mining database
- Troubleshooting
Cleaning up the Task Mining database
This page describes the necessary maintenance tasks for the Task Mining databases.
[AutomationSuite_Task_Mining]
, uses a single schema [tddiscovery]
for data storage. Primarily, Task Mining stores data in the object store, reducing the need of frequent database maintenance.
If required, you can use the Remove_Active_History.sql
database maintenance script to periodically clean up the following database table:
-
[AutomationSuite_Task_Mining].[tddiscovery].[ActivityHistory]
[AutomationSuite_Task_Mining]
before executing any scripts.
The following prerequisites are assumed:
-
You have access to the
[AutomationSuite_Task_Mining]
database with the required permissions.
CREATE PROCEDURE [tddiscovery].[Delete_TaskMining_ActivityHistory]
@CutoffTimeStamp datetime2,
@BatchSize INT = 10000
AS
BEGIN
DECLARE @total_deleted_items BIGINT = 0;
SET NOCOUNT ON;
-- delete ActivityHistoryItems
DECLARE @Deleted_Rows_ActivityHistoryItems INT = @BatchSize;
WHILE(@Deleted_Rows_ActivityHistoryItems = @BatchSize)
BEGIN
DELETE TOP(@BatchSize) FROM [tddiscovery].[ActivityHistory] WHERE At <= @CutoffTimeStamp;
SET @Deleted_Rows_ActivityHistoryItems = @@ROWCOUNT;
SET @total_deleted_items = @Deleted_Rows_ActivityHistoryItems + @total_deleted_items;
END;
PRINT('The script executed successfully!');
PRINT('Total deleted rows from [tddiscovery].[ActivityHistory]: ' + CONVERT(NVARCHAR, @total_deleted_items));
END;
GO
CREATE PROCEDURE [tddiscovery].[Delete_TaskMining_ActivityHistory]
@CutoffTimeStamp datetime2,
@BatchSize INT = 10000
AS
BEGIN
DECLARE @total_deleted_items BIGINT = 0;
SET NOCOUNT ON;
-- delete ActivityHistoryItems
DECLARE @Deleted_Rows_ActivityHistoryItems INT = @BatchSize;
WHILE(@Deleted_Rows_ActivityHistoryItems = @BatchSize)
BEGIN
DELETE TOP(@BatchSize) FROM [tddiscovery].[ActivityHistory] WHERE At <= @CutoffTimeStamp;
SET @Deleted_Rows_ActivityHistoryItems = @@ROWCOUNT;
SET @total_deleted_items = @Deleted_Rows_ActivityHistoryItems + @total_deleted_items;
END;
PRINT('The script executed successfully!');
PRINT('Total deleted rows from [tddiscovery].[ActivityHistory]: ' + CONVERT(NVARCHAR, @total_deleted_items));
END;
GO
-
Run the
Remove_Active_History.sql
database maintenance script to create theDelete_TaskMining_ActivityHistory
Stored Procedure.Note:Always use the most recent version of the Stored Procedure.
It is strongly recommended to archive previously executed SQL Stored Procedures by renaming the Stored Procedures. This provides an opportunity to detect and address any potential issues or anomalies within that particular version of the SQL Stored Procedure. The following code provides an example on how to rename a SQL Stored Procedure for archiving purposes.
EXEC sp_rename '[tddiscovery].[Delete_TaskMining_ActivityHistory]', '[Delete_TaskMining_ActivityHistory_2024-10-10_001]';
EXEC sp_rename '[tddiscovery].[Delete_TaskMining_ActivityHistory]', '[Delete_TaskMining_ActivityHistory_2024-10-10_001]'; -
Execute the
Delete_TaskMining_ActivityHistory
Stored Procedure. This deletes all data related to Activity History for a cut-off timestamp from the[AutomationSuite_Task_Mining].[tddiscovery].[ActivityHistory]
table.
PROCEDURE [tddiscovery].[Delete_TaskMining_ActivityHistory]
script, ensure that Task Mining usage is suspended.
Although there is no restriction on deleting data using a SQL Stored Procedure, it would be a good practice to retain the activity history in the system for a minimum period, for example, 30 days, to preserve recent activity records. This also provides an opportunity to detect and address any potential issues or anomalies within the SQL Stored Procedure before it is permanently deleted.
Delete_TaskMining_ActivityHistory
SQL Stored Procedure.
Parameter |
Description |
Mandatory Y/N |
@CutoffTimeStamp |
Delete all data before a specified timestamp (e.g., 2021-01-01 01:00:05). Note:
Do not provide a timestamp that leads to an empty table. |
Y |
@BatchSize INT = 10000 |
The number of rows to be deleted at a time. This enables you to delete the data batch by batch. The default is set to 10000. |
N |
DECLARE @ProcessTime datetime2;
SET @ProcessTime = '2024-07-11 13:44:42.7856026';
EXEC [tddiscovery].[Delete_TaskMining_ActivityHistory] @CutoffTimeStamp = @ProcessTime;
DECLARE @ProcessTime datetime2;
SET @ProcessTime = '2024-07-11 13:44:42.7856026';
EXEC [tddiscovery].[Delete_TaskMining_ActivityHistory] @CutoffTimeStamp = @ProcessTime;
For more information, see the official Microsoft documentation on Stored procedures.