FIX: DISCOVER_TABLE_STORAGE_COLUMN_SEGMENTS DMV returns an incorrect result of memory usage in SQL Server 2016

Applies to: SQL Server 2016 DeveloperSQL Server 2016 EnterpriseSQL Server 2016 Enterprise Core


Assume that you create a tabular database at the compatibility level 1200 in Microsoft SQL Server 2016. When you use the DISCOVER_TABLE_STORAGE_COLUMN_SEGMENTS DMV to query the memory usage of each column, the DMV incorrectly returns a value of 0 for the ALLOCATED_SIZE and USED_SIZE columns.


This problem was fixed in the following cumulative updates for SQL Server:


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


Learn about the terminology  that Microsoft uses to describe software updates.