Skip to main content

Manage Database Index Usage in Business Central.

Hi Readers, 

Microsoft continues to improve the administrative capabilities of Dynamics 365 Business Central. One of the most interesting additions in Business Central 2026 Release Wave 1 is the ability to manage database indexes directly from the Business Central client.

For administrators managing large environments, this feature provides greater control over storage consumption and database performance without requiring direct SQL access.

What are Database Indexes?

A database index is a structure that helps SQL Server or Azure SQL locate records much faster.

Instead of scanning an entire table, SQL can quickly seek to the required rows using an index.

Indexes improve:

  • Searching
  • Filtering
  • Sorting
  • Aggregations
  • Report performance

However, indexes are not free.

Every INSERT, MODIFY, or DELETE operation must also update the indexes, which means:

  • Higher storage usage
  • Slower write operations
  • Additional maintenance overhead

Finding the right balance is important.


What's New in Business Central 2026 Wave 1?

Business Central now exposes index information directly inside the application.

Administrators can:

  • View every index on a table
  • See index size
  • Monitor index usage
  • Enable indexes
  • Disable unused indexes
  • Manage indexes per company
  • Manage indexes across all companies

Previously, this level of visibility typically required SQL tools or Azure SQL diagnostics.


Where Can You Find It?

Navigate to:

Search → Table Information

Open a table and choose its Table Number.

This opens the Table Data Management page.

Here you'll find an Indexes section displaying detailed information.


Information Available for Every Index

The page displays useful metrics including:

  • Index Name
  • Key Fields
  • Index Type
  • Index Size
  • User Seeks
  • User Scans
  • Last User Seek
  • Last User Scan
  • Whether the index is enabled

These statistics help identify indexes that consume space but provide little value.


Company-Level Index Management

One of the most powerful improvements is company-specific index control.

Many Business Central tables are company specific.

That means:

Company A can have an index enabled.

Company B can have the same index disabled.

This is particularly useful when only certain companies use specific modules or business processes.

Instead of maintaining indexes everywhere, administrators can optimize each company independently.


Which Indexes Can Be Disabled?

Business Central protects critical indexes.

You cannot disable:

  • Primary Key
  • Unique Indexes
  • SIFT Indexes
  • SystemId Indexes

Only eligible secondary indexes can be turned off.

This prevents accidental performance or data integrity issues.


Benefits of Disabling Unused Indexes

Removing unnecessary indexes offers several advantages:

Reduced Storage

Indexes can consume significant database space.

Disabling unused ones reduces storage requirements.


Faster Write Performance

Every insert, update, and delete operation must update indexes.

Fewer indexes mean:

  • Faster posting
  • Faster imports
  • Better data synchronization
  • Improved batch processing

Better Environment Optimization

Different companies often have different workloads.

Company-specific index management lets administrators optimize each company independently.


Important Considerations

Before disabling an index:

  • Review usage statistics.
  • Monitor reports and searches that rely on the index.
  • Test changes in a sandbox.
  • Disable only indexes with consistently low usage.
  • Monitor performance after making changes.

Indexes that appear unused during a short observation period may still support monthly or annual processes.


Enabling an Index

Disabling takes effect immediately.

Enabling is queued and processed during the scheduled midnight maintenance process.

Plan accordingly if immediate availability is required.


Best Practices

✔ Monitor index usage over time.

✔ Test in a sandbox first.

✔ Disable only low-usage secondary indexes.

✔ Never assume an index is unnecessary based on a single day of activity.

✔ Document any changes made to production environments.


Final Thoughts

The new Database Index Management feature gives Business Central administrators much greater visibility into database performance.

Instead of relying solely on SQL tools, administrators can now make informed optimization decisions directly from the Business Central client.

For organizations with multiple companies and large datasets, this feature can help reduce storage costs, improve write performance, and simplify ongoing database maintenance.


Frequently Asked Questions

Can I disable every index?

No. Primary keys, unique indexes, SIFT indexes, and SystemId indexes are protected.

Does disabling an index affect all companies?

No. You can disable it for a single company or for all companies.

Does enabling an index to happen immediately?

No. Enabling is scheduled during the next midnight maintenance process.

Why would I disable an index?

To reduce storage usage and improve insert, update, and delete performance when the index is rarely used.

Is this feature available in earlier versions?

No. It is available starting with Business Central 2026 Release Wave 1.


Regards,

Saurav Dhyani

Comments

Popular posts from this blog

Microsoft Dynamics NAV 2016 - How to Configure Phone Client.

Hi All, In this article we will discuss how we can connect Microsoft Dynamics NAV 2016 with New Client Launched i.e. Phone Client. This Article Contain Steps for a Android Phone as I have Only Android Phone. I am doing it having all tiers on my windows 8 machine, steps remain same for multiple servers but issues might be different. What we Need (Other what we discuss in this article) -  The Service Tier should be on Public IP . Some of the Data-card does not Provide you Public IP. check it for sure.

How to Set Up NavUserPassword Authentication in Business Central.

Hi Readers, In this article we will discuss steps to Setup NAVUserPassword in Business Central on-prem. NavUserPassword is an authentication method that's handled by Business Central Server, but isn't based on Windows users or Active Directory. Each user is set up with a username and password that's configured inside Business Central only. The user is prompted for username/password credentials when they start the client. #msdyn365bc, #credentialtype

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.