Search

Please document sys.dm_os_waiting_tasks.resource_description by Adam Machanic

Closed
as Fixed Help for as Fixed

13
0
Sign in
 to vote
Type: Suggestion
ID: 358576
Opened: 7/29/2008 12:49:39 PM
Access Restriction: Public
0
Workaround(s)
The "resource_description" column of the sys.dm_os_waiting_tasks view is documented as "Description of the resource that is being consumed." How about fleshing this out a bit? I would like to know which wait types can populate this column, and the formats I can expect.

This data would be extremely useful even if the descriptions are indicated as possibly changing in future versions of the product, as with the documentation of sys.dm_tran_locks.resource_description. It's very difficult to write intelligent monitoring scripts without knowing what kind of data is available.
Details (expand)
Product Language
English

Category

Documentation

Proposed Solution

Document the resource_description format for every available wait type (only those that populate the column, of course).

Benefits

Improved Reliability
Improved User Interface
Improved Administration
Improved Performance

Other Benefits

 
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 12/10/2010 at 10:51 AM
The developer looked this up and I have added this info to the topic. Here is the list. If it gets cut off (there should be 6 items) then drop me an e-mail directly at rick.byham@microsoft.com. Thank you.
The resource_description column has the following possible values,
Thread-pool resource owner:
•    threadpool id=scheduler<hex-address>

Parallel query resource owner:
•    exchangeEvent id={Port|Pipe}<hex-address> WaitType=<exchange-wait-type> nodeId=<exchange-node-id>

Exchange-wait-type can be one of the following.
•    e_waitNone
•    e_waitPipeNewRow
•    e_waitPipeGetRow
•    e_waitSynchronizeConsumerOpen
•    e_waitPortOpen
•    e_waitPortClose
•    e_waitRange

Lock resource owner:
•    Same as in sys.syslockinfo.

External resource owner:
•    External ExternalResource=<wait-type>

Generic resource owner:
•    TransactionMutex TransactionInfo Workspace=<workspace-id>
•    Mutex
•    CLRTaskJoin
•    CLRMonitorEvent
•    CLRRWLockEvent
•    resourceWait

Latch resource owner:
•    <db-id>:<file-id>:<page-in-file>
•    <GUID>
•    <latch-class> (<latch-address>)
Posted by Adam Machanic on 11/24/2010 at 9:00 AM
Great news!! Thank you so much for sharing. Have a nice holiday, and I'll look for an update in a couple of weeks :-)
Posted by Microsoft on 11/24/2010 at 7:43 AM
I've brought the MVP customer vote count to the attention of dev, and a new owner of this DMV says he will dig up some info for us. Lots of snow in Seattle, plus the Thanksgiving Day holiday, so it might still be two weeks.
Posted by Adam Machanic on 10/19/2010 at 10:52 AM
Hi,

It's been over two years. Any chance that there will be some movement here before the next version of SQL Server ships?


Thanks,
Adam Machanic
Posted by Microsoft on 8/1/2008 at 9:49 AM
Hello,

Thank you very much for reporting this issue. We are aware of this issue and have plans to update the topic in a future update to SQL Server Books Online.

Kind regards,
Tessa Wooley
SQL Server Documentation Team
Sign in to post a workaround.
© 2013 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement