Up until SQL Server 2008 R2, using index usage stats entries in sys.dm_db_index_usage_stats to make some assumptions over index design and workload patterns was common.
However, in SQL Server 2012 and higher versions, entries in this DMV were reset with every index rebuild, so this was no longer a viable way of tracking index usage patterns. This was clearly voiced out in Connect items, such as 739566 and direct customer feedback.
In SQL Server 2016 (starting with RC0), we are restoring the expected behavior with usage stats tracking in sys.dm_db_index_usage_stats, where entries will not be removed. This was documented in What's New in Database Engine.
We are also addressing this in an upcoming SQL Server 2014 Service Pack, and as usual deliver added value to in-market versions.
Pedro Lopes (@sqlpto) – Senior Program Manager
Changes in two sections to remove unreferenced error codes from a table, add a missing code - 0x8007000D ERROR_INVALID_DATA – and revise the description of error code ERROR_INVALID_DATA: https://msdn.microsoft.com/en-us/library/mt242418.aspx
Two changes at https://msdn.microsoft.com/en-us/library/mt242401.aspx
In Section 220.127.116.11.18, ICertAdminD::BackupPrepare (Opnum 20), revised the description for pwszBackupAnnotation.
In Section 2.2.5, Common Error Codes, obsolete errors codes, 0x80004003 and 0xc800020D, were removed from the error code table.
Changed the title to reflect that the registry keys described in the table in Section 18.104.22.168.4 apply to both Internet Explorer 10 and Internet Explorer 11: https://msdn.microsoft.com/en-us/library/mt691557.aspx