{"title":"Missing indexes in Business Central databases","url":"https://jonas-paprotka.de/docs/dev-itpro/administration/database-missing-indexes/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/database-missing-indexes, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/database-missing-indexes","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"Learn about missing indexes and the database missing indexes page.","date":"2025-03-21","meta":{"topic":"concept-article"},"outline":[{"level":1,"title":"Missing indexes in Business Central databases","slug":"missing-indexes-in-business-central-databases","at":0,"chars":4980},{"level":2,"title":"Indexes overview","slug":"indexes-overview","at":245,"chars":961},{"level":2,"title":"Missing indexes","slug":"missing-indexes","at":1206,"chars":3485},{"level":3,"title":"View missing indexes in Business Central","slug":"view-missing-indexes-in-business-central","at":2449,"chars":2242},{"level":2,"title":"Related information","slug":"related-information","at":4691,"chars":289}],"text":"# Missing indexes in Business Central databases\nThis article gives an insight about missing indexes for administrators and developers. Database Missing Indexes help administrators and developers to enhance the performance of their applications.\n## Indexes overview\nIndexes are an effective feature in relational databases, like SQL, to speed up the process of finding data. By indexing your frequently needed data, the overall performance of your application is optimized. For example, when you need to see some information in your application, a database query will run behind the scene to complete your request and it will look up every record until it finds the required information. This process of finding information is time consuming and slows down the application performance. However, if you index the data, like those columns that are referred more often, the database will go directly to that column instead of looking up all records in the table. This action significantly increases the efficiency and overall performance of your application.\nLearn more about indexes and their types in https://learn.microsoft.com/sql/relational-databases/indexes/clustered-and-nonclustered-indexes-described.\n## Missing indexes\nWhen you run a database query, the query optimizer, which is an important database component, analyzes and chooses the best possible plan to complete the instruction. In doing so, it provides additional information about the ongoing operation that the operation might perform well if the particular column (or columns) is indexed. The SQL server's Query optimizer gets this information from Dynamic Management Views (DMV), in our case, https://learn.microsoft.com/sql/relational-databases/system-dynamic-management-views/sys-dm-db-missing-index-details-transact-sql. sys.dm_db_missing_index_details returns details about missing indexes, which help you in creating right indexes.\nLearn how to use missing index suggestions to tune indexes and improve query performance in https://learn.microsoft.com/sql/relational-databases/indexes/tune-nonclustered-missing-index-suggestions.\nLearn about Dynamic Management Views (DMV) in System Dynamic Management Views (Transact-SQL)<https://learn.microsoft.com/sql/relational-databases/system-dynamic-management-views/system-dynamic-management-views>.\nLearn how AL plays a part in efficient data access with SQL components in ../performance/performance-developer#efficient-data-access.\n### View missing indexes in Business Central\nTo get information on missing indexes, open the Database Missing Indexes page in Business Central and view the data in the following columns:\nColumn|Description\nTable Name|The name of the table on which the suggested columns are based.\nExtension Id|The ID of your application to which this data is related.\nIndex Equality Columns|The data in these columns is based on equality queries. For example, \"Select * from customer where id = 021\"\nIndex Inequality Columns|The data in these columns comes from queries, which aren't based on equality operations. For example, `Select * from customer where id < 200`\nIndex Include Columns|These columns have a copy of associated data for fast retrieval of information, which is based on the columns suggested in `Index Equality Columns` and `Index Inequality Columns`. Include columns aren't indexed columns themselves but point to the additional information linked to the indexed columns. For example, they include the fields in the Select part.\nSeeks`*|Number of seeks caused by queries that could have used the suggested index.\nScans*|Number of scans caused by queries that could have used the suggested index.\nAverage Total Costs*|Average cost of the queries that would be reduced if the suggested index was added.\nAverage Impact*|Average percentage benefit for queries if the suggested index was added. The value means that the cost would drop on average by this percentage if the suggested index was added.\nEstimated Benefit*|The estimated benefit of adding the suggested index is calculated as: (seeks + scans) x (average total costs) x (average impact). For example, consider a query that seeks 5 times, scans 10 times, and currently costs 10. If the impact drops 50% by adding the suggested index, then the benefit is (5 + 10) x 10 x 50.\n*Applies to 2025 release wave 1 (version 26.0) and later\n> IMPORTANT\n> The information provided on the Database Missing Indexes page is a suggestion and isn't mandatory. Analyze where and how many indexes are best suited for optimal performance of your application. Indexes take storage space, can affect updates for tables with frequent insertions and deletions, and can be an expensive operation if overused.\n## Related information\nPerformance Article For Developers<../performance/performance-developer>\nOptimizing SQL Server Performance with Business Central<optimize-sql-server-performance>\nhttps://learn.microsoft.com/sql/relational-databases/indexes/tune-nonclustered-missing-index-suggestions"}