Table extensions stored on base table
Table extensions stored on base table
Table extension fields are stored on the base table, so no join is needed. Reads are faster and writes up to 30% faster in a benchmark.
Area: Developer tools. Status: GA. Developer relevance: high. Airtime: 2 min across 1 video.
Status evidence
- Nothing said about status; launch event convention: generally available unless stated otherwise.
Where they talk about it
- What's new: Server and Database: 1:46 to 3:47 (called "Optimized data model for table extensions (zero joins)" there)
Quotes
- 2:52 "we are now putting all the table extensions fields back on the base table. There will be no more joints" - Describes the core design decision of the new table extension data model.
- 3:15 "will be up to uh 30% faster. You can see uh the different um numbers here from our benchmark" - Gives the headline performance number for write operations with the new data model.
Caveats mentioned
- Benchmark numbers vary by way of reading data; FindFirst is only one example
Documented features match
- Faster data loading with improved data model for table extensions - high confidence (llm). Docs say: General availability, roadmap id 573332. Extension fields in same table
Docs checked on 2026-10-02: the match is against Microsoft's what's new pages for the wave as they were on that date. Microsoft keeps filling the documentation, so "no documented item" can go stale. The wider product documentation on learn.microsoft.com was searched for this feature on the same date; the feature's data lists an article when one was found.
Tags: database, performance, table-extensions, al
Generated by pipeline step 06. Source: YouTube auto-captions of the launch event videos, see the deep links. Not official.