(Republishing, or using this info in a commercial product/website, is prohibited without permission. All other uses are permitted. If in doubt, please ask.)
This wait type occurs after a deadlock happens while trying to drop a temporary table. The code waits before trying again, and the wait times increase exponentially (like in an exponential back-off for a spinlock or network packet collision).
(Books Online description: “Occurs between attempts to drop a temporary object if the previous attempt failed. The wait duration grows exponentially with each failed drop attempt.”)
Questions/comments on this wait type? Click here to send Paul an email, especially if you have any information to add to this topic.
Added in SQL Server version:
Removed in SQL Server version:
Extended Events wait_type value:
The map_key value in sys.dm_xe_map_values is 237 in 2008 and 2008 R2, 244 in 2012, and 251 in 2014 RTM. After 2014 RTM, you must check the DMV to get the latest value as some map_key values have changed in later builds.
When this wait type occurs, you will see a message in the error log that begins “Drop Temp Obj:” and possibly a deadlock graph too. There was a bug in SQL Server 2005 that could lead to this happening, but I haven’t seen an occurrence of this in recent versions.
Known occurrences in SQL Server (list number matches call stack list):
Abbreviated call stacks (list number matches known occurrences list):