Skip to main content
Open

index optimizer

Related products:Deployment Center
  • February 25, 2026
  • 3 replies
  • 62 views

Forum|alt.badge.img+4

When upgrading the platform to 2026.1, we waited for around two hours in total (SF and IAM on DEV) for the TSF optimizer to finish rebuilding the indexes. This was even after old branches/applications were removed in SF and IAM the day before to speed up the upgrade. At one point, we saw the slow_query_log index being rebuilt, where fragmentation was only 0.1%, containing over 5 million records. Our idea is twofold:

  1. Parameterize or hardcode the index optimization so that only indexes with a fragmentation percentage above a given threshold are rebuilt.
  2. Allow configuration in the Deployer to specify whether indexes need to be optimized. We already have a nightly job that performs this, so we would prefer to let that run outside office hours.

3 replies

Forum|alt.badge.img+8
  • Captain
  • February 25, 2026

Totally agree.

I assume most companies don’t have the process of upgrading SF/IAM automated outside of business hours, so that means the whole development team cannot work in the SF while this process is being executed. Considering there are new releases every 4 weeks now, it really brings value if the upgrade time could be reduced.


Arie V
Community Manager
Forum|alt.badge.img+12
  • Community Manager
  • March 20, 2026
NewOpen

AndreKemmeren
Captain
Forum|alt.badge.img+3

Recently Microsoft announced a new feature for SQL (starting in Azure as they usually do) that potentially removed the entire need of index maintenance. We are currently doing a trial of this feature to evaluate it's effectiveness.

Stop defragmenting and start living: introducing auto index compaction | Microsoft Community Hub

 

This increases the value of this idea.