(Republishing, or using this info in a commercial product/website, is prohibited without permission. All other uses are permitted. If in doubt, please ask.)
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 403 in 2008 and 2008 R2, 451 in 2012, and 467 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.
I’ve heard of this wait being an issue when using linked servers and the provider’s driver is not properly installed. For example:
- Install the Oracle driver but do not reboot as instructed (this is where the mistake was made)
- Modify the OraOLEDB.Oracle Provider to Allow In Process and do not restart the SQL instance
- Create a linked server using the Oracle driver
- Query the linked server and the query hangs with a wait type of PREEMPTIVE_COM_QUERYINTERFACE
Note that when a thread calls out to Windows, the thread changes from non-preemptive (SQL Server controls the thread) to preemptive (Windows controls the thread) mode. The thread’s state will be listed as RUNNING, as SQL Server doesn’t know what Windows is doing with the thread.
Known occurrences in SQL Server (list number matches call stack list):
Abbreviated call stacks (list number matches known occurrences list):