--- id: post/duiliotacconi-com/2001 type: post title: Index Management with Dynamics 365 Business Central 2026 Wave 1 summary: Dynamics 365 Business Central 2026 Wave 1 introduces the ability to disable and enable indexes on demand, allowing organizations to improve write performance by removing unused or unnecessary indexes from their databases. The feature is particularly valuable for online deployments and provides detailed statistics to help administrators make informed decisions about which indexes to retain. tier: community language: en tags: - index management - performance tuning - database optimization - sql server - storage capacity - query optimization - write operations system: platform review: state: reviewed by: opus at: "2026-10-08T01:55:04.426Z" flags: [] generated: at: "2026-10-08T01:26:53.141Z" pipeline: 0.2.0 prompts: extract-post: 1 input_hash: d1cf052e5f58efddab35ae5526c26fec05df337a6652dfa92813ad25886a7764 evidence: - kind: blog url: https://duiliotacconi.com/2026/05/28/index-management-with-dynamics-365-business-central-2026-wave-1/ title: Index Management with Dynamics 365 Business Central 2026 Wave 1 date: "2026-05-28" commit: null t: null quote: null - kind: blog url: https://duiliotacconi.com/2026/05/28/index-management-with-dynamics-365-business-central-2026-wave-1/ title: Index Management with Dynamics 365 Business Central 2026 Wave 1 date: "2026-05-28" commit: null t: null quote: Bad Index = Zero Read and High Updates. Bad Indexes should be disabled. - kind: blog url: https://duiliotacconi.com/2026/05/28/index-management-with-dynamics-365-business-central-2026-wave-1/ title: Index Management with Dynamics 365 Business Central 2026 Wave 1 date: "2026-05-28" commit: null t: null quote: Unused (outdated) Index = Last Read (index seek, scan or lookup) far back in time links: learn: [] objects: - object/table/37 features: [] topics: [] localizations: [] videos: [] posts: [] guidelines: [] post_id: "2001" source_id: duiliotacconi-com source_name: Duilio Tacconi url: https://duiliotacconi.com/2026/05/28/index-management-with-dynamics-365-business-central-2026-wave-1/ published_at: "2026-05-28T13:13:22.000Z" author: Duilio Tacconi full_text: false words: 2001 quotes: - text: Bad Index = Zero Read and High Updates. Bad Indexes should be disabled. why_it_matters: Provides a simple decision rule for identifying indexes that consume resources during writes but provide no query benefits, making them candidates for removal - text: Unused (outdated) Index = Last Read (index seek, scan or lookup) far back in time why_it_matters: Establishes a practical criterion for identifying indexes that are no longer actively used and can be safely disabled to free storage and reduce maintenance overhead code_objects_mentioned: - table Sales Line systems: - platform - development - administration versions_mentioned: - 2026 Wave 1 - version 28 preview: embeddable: true frame_url: https://duiliotacconi.com/2026/05/28/index-management-with-dynamics-365-business-central-2026-wave-1/embed/ image: https://i0.wp.com/duiliotacconi.com/wp-content/uploads/2026/05/biglebowski.jpg?fit=1200%2C685&ssl=1 image_alt: null image_w: 1200 image_h: 685 site_name: Dynamics 365 Business Central tales, myths, legends. And something serious. favicon: https://duiliotacconi.com/wp-content/uploads/2023/07/cropped-wordpress.png?w=32 probed_at: "2026-10-07T11:50:16.148Z" --- # Index Management with Dynamics 365 Business Central 2026 Wave 1 [Read the post](https://duiliotacconi.com/2026/05/28/index-management-with-dynamics-365-business-central-2026-wave-1/) · Duilio Tacconi (Duilio Tacconi, MVP) · 2026-05-28 · 2001 words · tier community · reviewed (checked by Opus) > Dynamics 365 Business Central 2026 Wave 1 introduces the ability to disable and enable indexes on demand, allowing organizations to improve write performance by removing unused or unnecessary indexes from their databases. The feature is particularly valuable for online deployments and provides detailed statistics to help administrators make informed decisions about which indexes to retain. ## Key points - Disabling unused indexes reduces write operation duration and decreases database storage requirements by eliminating unnecessary index maintenance overhead - The page displays detailed metrics including seeks, scans, lookups, updates, fragmentation percentage, and last usage dates to identify candidates for removal - Microsoft's automatic index tuning has added indexes based on workload analysis over time, and administrators can now review and remove relics from past periods that no longer benefit queries - Administrators should wait at least 2 weeks (ideally 30 days) after database restart before making index changes to ensure statistics are representative of actual usage patterns - Index defragmentation can be performed by disabling and re-enabling an index, which reduces fragmentation and updates statistics during off-peak hours ## Quotes - "Bad Index = Zero Read and High Updates. Bad Indexes should be disabled." (Provides a simple decision rule for identifying indexes that consume resources during writes but provide no query benefits, making them candidates for removal) - "Unused (outdated) Index = Last Read (index seek, scan or lookup) far back in time" (Establishes a practical criterion for identifying indexes that are no longer actively used and can be safely disabled to free storage and reduce maintenance overhead) ## AL objects mentioned As named in the post. A name that matches one object page by exact type and name links to it; the others stay as named. - [table 37 "Sales Line"](../../objects/table/37.md) ## Context - Features: Index disable/enable capability, Index usage statistics, Fragmentation analysis, Index size reporting, Database start time tracking, Statistics update monitoring, Combined index size calculation, Per-company index metrics - Versions: 2026 Wave 1, version 28 Source: Duilio Tacconi, community blog. Summary, key points and quotes are derived (CONTENT-NOTICE.md); read the original for the full text.