Sign in with Microsoft
Sign in or create an account.


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:

Cumulative Update 2 for SQL Server 2016

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:

Latest cumulative update for SQL Server 2016


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.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!