CPU consumption related to Indexes in Timextender Classic Repository Database¶
Symptoms¶
High CPU consumption by the Timextender repository database. Error Message received:
Error
High CPU consumption by repository database.
Cause¶
High CPU consumption is can be caused by indexing on the repository tables.
Resolution¶
To address the high CPU consumption, you can add or modify indexes in the repository tables. However, there are a few considerations to keep in mind:
- Adding or modifying indexes may improve execution and reduce CPU consumption.
- The changes might be overwritten every time the table is deployed.
- There is a risk that the changes could cause errors when using or running the table or project.
Warning
Always backup your Timextender Classic repository before making these types of changes. We do not recommend altering the Timextender Classic repository database manually, as it can lead to unforeseen issues.
Steps to add a non-clustered index:
- Backup your databases before making any changes to avoid issues if the changes do not work as expected.
- Execute the following SQL script to create a non-clustered index:
USE [timextender_repository]
GO
CREATE NONCLUSTERED INDEX IX_ExecutionPagageLogDetails_Idx
ON [dbo].[ExecutionPackageLogDetails] ([ObjectId],[Start],[End])
INCLUDE ([StepId])
GO
Reference Ticket¶
32241
Reference Links¶
Discussed in the community
Looking for related questions…
Didn't find your answer? Ask the community about this page — questions are answered by Timextender experts, partners and other users.