- Release Notes
- Getting Started
- Access and Permissions
- Installation and Upgrade
- Interacting with Insights
- Historical data export
- Logs
- Performance and Scalability

Insights
Insights database maintenance
linkOverview
linkdbo
and read
. Both tables store data from Orchestrator databases and pass data between each other. Over time, tables store a large amount
of data that can impact database performance. You can free up space by removing data that is not relevant or outdated.
The estimated threshold for storing historical data is set to
- Up to 100 million jobs
- Up to 1 billion job events
- Up to 100 million queue items
- Up to 500 million queue item events
- Up to 1 billion robot logs
[dbo].Jobs
, [dbo].JobEvents
, [dbo].QueueItems
, [dbo].QueueItemEvents
, [dbo].RobotLogs
tables, or just the [dbo].RobotLogs
.
PROCEDURE
[read].[Delete_Insights_Data_Read]
and PROCEDURE
[read].[Delete_Process_Logs_Read]
scripts, the Insights module needs to be
disabled.
Considerations
link- Scripts with the
_DBO
suffix are used to delete data from DBO schema tables, - Scripts with the
_Read
suffix are used to delete data from Read schema tables. - Large-sized batches might impact the speed of execution. Consider using the default batch size, which is set to 100000.
Prerequisites
linkPROCEDURE [read].[Delete_Insights_Data_Read]
and
PROCEDURE [read].[Delete_Process_Logs_Read]
scripts, the Insights module
needs to be disabled.
- Log in to the VM where Orchestrator is installed.
-
Find the following:
C:\Program Files (x86)\UiPath\Orchestrator\UiPath.Orchestrator.dll.config
Insights.ModuleEnabled
. -
Open the
UiPath.Orchestrator.dll.config
file using Notepad. -
Find the following configuration value:
"codes": [ { "code": "<add key=\"Insights.ModuleEnabled\" value=\"true\" />", "language": "text", "name": "configuration value" } ] }
"codes": [ { "code": "<add key=\"Insights.ModuleEnabled\" value=\"true\" />", "language": "text", "name": "configuration value" } ] } -
Replace
true
withfalse
. - Save the file.
- Go back to the VM where Orchestrator is installed and restart the VM.
- Run the maintenance scripts.
SQL stored procedure 1: delete all data based on cut-off timestamp
linkJobs
, JobEvents
, QueueItems
, QueueItemEvents
, RobotLogs
) for a cut-off timestamp.
SQL Stored Procedures | Parameter | Description |
---|---|---|
Delete_Insights_Data_DBO |
| Delete data from [dbo].[Jobs] ,
[dbo].[JobEvents] , [dbo].[QueueItems] , [dbo].[QueueItemEvents] , [dbo].[RobotLogs] tables based on a cut-off timestamp.
|
Delete_Insights_Data_Read | N/A | Truncate [read].Jobs , [read].JobEvents ,[read].QueueItems , [read].QueueItemEvents , [read].RobotLogs tables.
|
The Insights Dashboard widgets are available again after SQL Stored Procedure 1 has finished, and the data has been backfilled. Keep in mind that the backfill process may take hours to complete given that you have a large amount of data.
Delete_Insights_Data_DBO
SQL Script, it creates a QueueItems.IX_CreationTime
nonclustered index with the purpose of making future executions faster.
SQL stored procedure 2: delete RobotLogs data based on ProcessNames and Tenant ID
linkGenerate and save this SQL Stored Procedure to delete RobotsLogs based on ProcessNames and Tenant ID.
SQL Stored Procedures | Parameter | Description |
---|---|---|
Delete_Process_Logs_DBO |
The Orchestrator process name.
Tenant ID is required as two tenants might run processes with identical names.
Delete data in batches of 100000. See Considerations. | Delete data from [dbo].[RobotLogs] table by ProcessName and Tenant ID.
|
Delete_Process_Logs_Read |
| Truncate [read].RobotLogs table.
|