What are DPA's capabilities for monitoring and troubleshooting when [tempdb] runs out of space?
Can DPA...
- Identify SPIDs/transactions consuming the most space in [tempdb]?
- Identify related SQL statements of SPIDs/transactions?
- Identify [tempdb] file space usage (size, allocated size, unallocated size, version store size, user objects size, internal object size, mixed extent size, etc.)
- Identify SPIDs with open transactions?
The above information is readily available in various DMVs and I could roll my own solution to get it, if necessary. But I don't want to reinvent the wheel if DPA can get some or all of the above information.
I would kindly ask: DPA solutions only, please.
-Dave