Business Central AL Developers Gain Code-Driven Database Index Management in 2026 Wave 2

The important distinction is application-aware control, not a promise that switching off indexes will automatically make Business Central faster. Developers gain another performance-management lever—but a lever still needs someone who understands what it moves.

What the release information establishes​

The roadmap record lists the feature as Launched, with an October 2026 general-availability date. Its stated scope is Business Central on the Web platform, in the Worldwide standard multi-tenant cloud, through the General Availability release ring.

Those fields do not establish the exact day a particular tenant receives the capability. Microsoft’s roadmap describes its release dates as estimates and says information can change. As of October 1, 2026, the listed availability month has begun; that is not equivalent to confirmation that every environment has been updated.

There is also a documentation boundary worth keeping straight. Microsoft’s update 29.0 article remains framed as a public-preview overview for Business Central online sandbox environments, excluding production and on-premises environments from that preview scope. It anticipates general availability in October 2026. That older preview framing should not override the roadmap’s launched status, but neither source proves on-premises availability for this specific feature.

Why index control matters​

Microsoft’s index-management documentation explains the tradeoff: indexes accelerate finding, filtering, sorting and aggregating data, but consume storage and add maintenance work to creates, updates and deletes. AL-defined table and table-extension keys underpin database indexes. Removing a useful index can therefore exchange lower write overhead for slower reads.

The practical opportunity is to align index management with an application’s needs. A publisher could evaluate whether an optional feature warrants its associated index—but that is a design possibility, not a documented implementation example or guaranteed performance improvement.

Our recommendation is to measure representative reads and writes before making changes, then validate the result in a sandbox. This follows from Microsoft’s documented tradeoff; it is not a prescribed procedure for the new AL interface.

Existing admin tools provide a useful starting point​

Microsoft already documents administrative index management for Business Central 2026 release wave 1 and later. To inspect indexes:

1. Press Alt+Q and search for Table Information.
2. Select the table’s ID in Table No.
3. In Table Data Management, choose Company Name.
4. Review Indexes for storage, usage and index type.

In that documented interface, administrators can disable eligible nonunique indexes for one company or all companies. Disabling is immediate; re-enabling is queued for the next scheduled midnight process. Unique indexes, primary keys, SIFT and $systemid indexes are protected there. These are UI rules, not verified rules for the new AL capability.

What developers still need before writing code​

The inspected feature listing does not specify an AL method, syntax, permission requirement, company scope or execution timing. It also does not establish whether code-driven control inherits the administrative interface’s protected-index rules. Providing a copy-and-paste example now would mean guessing at precisely the details developers need to trust.

The takeaway is straightforward: Business Central publishers are gaining programmatic index control, but implementation details remain essential. Use the existing metrics to identify candidates, test workload consequences, and avoid treating “index off” as a universal performance button. Database tuning rewards evidence, not enthusiasm.