Yesterday I was trying to drop some hypothetical indexes in production against a fairly active table. I started causing blocking so I had the bright idea of disabling the indexes first, then dropping. Well, that didn't help, even when setting DEADLOCK_PRIORITY to LOW. I ended up waiting until early morning to remove those indexes to prevent from blocking other users.
Finding no info on the web about the locks taken during the process of dropping or disabling an index, I set about doing this small bit of research.
The queries I used:
In Window 1 (Execute first)
BEGIN TRAN SELECT TOP 100 * FROM myTable WITH (TABLOCKX)
* I use TABLOCKX to simulate many updates going to this table.
In Window 2
DROP INDEX [ix_myTable_testIndex] ON myTable
sp_whoisactive @get_locks = 1
When you disable an index, you end up trying to acquire a Sch-M or Schema Modification lock.
Then the next select query comes along and trys to grab an IS or Intent Shared lock
So at this point yesterday, I was thinking, maybe I can disable the index and then drop it. Well, ALTER INDEX ... DISABLE also waits on a Sch-M lock before it can proceed. I'm not any better off. Even after the disabling the index, SQL Server still tries to grab a Sch-M lock to drop the disabled index. All these rules also seem to apply to hypothetical indexes. I'm sure there's some internals reason why it does this, but why worry about locks when dropping a disabled or hypothetical index since neither are used by active queries?
Lesson learned, drop indexes when the table usage is low.