(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 is exactly as described by the Books Online entry (although the second sentence should say ‘This is *also* used to detect…’).
(Books Online description: “Occurs when a task is waiting for a distributed query operation to finish. This is used to detect potential Multiple Active Result Set (MARS) application deadlocks. The wait ends when the distributed query call finishes.”)
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 201 in 2008 and 2008 R2, 208 in 2012, and 215 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.
If this wait type becomes prevalent on your server, identify the queries causing it, and do performance analysis on the portions of the query that run on the remote SQL Server or other OLE DB data provider. For more information, see the Books Online topic Optimizing Distributed Queries.
Known occurrences in SQL Server (list number matches call stack list):
- Waiting for a remote data provider to respond, in this case while retrieving a remote rowset as input into a local sort
- Waiting for a remote data provider to respond, in this case while running the sp_testlinkedserver procedure
- Waiting for a remote data provider to respond, in this case while retrieving remote statistics while compiling a query plan
And other similar call stacks.
Abbreviated call stacks (list number matches known occurrences list):