I recently got an interesting question from a reader about running a CREATE INDEX statement with DROP_EXISTING
Microsoft has just released a new round of cumulative updates for SQL Server 2012, and the release notes indicate that a fix to the sys.dm_db_index_usage_stats dynamic management view has been included in these updates. This is good news for index tuners using SQL Server 2012.
As of SP2 + CU12 and SP3 + CU3, SQL Server 2012 will persist index usage information even when ALTER INDEX REBUILD is run.
Update from Kendra (2018)** - Microsoft Connect has been retired. The current feedback system is here: https://feedback.azure.com/forums/908035-sql-server