Which dynamic management view helps identify long-running report requests in a Fabric warehouse?

• A. sys.dm_exec_requests
• B. sys.dm_exec_sessions
• C. sys.dm_exec_connections
• D. sys.dm_pdw_exec_requests

Answer: (A)

To identify long-running report requests, you need a view that shows what is actively executing and for how long. The dynamic management view that provides a row for each active request, including its status and total_elapsed_time, is the best fit. This lets you spot queries that have been running for a long time (for example, by filtering on status = 'running' and total_elapsed_time above a threshold) and see if they’re blocked or waiting on resources. You can also join to the SQL text to understand what the report is running.

Other options focus on sessions or connections rather than the specific active requests they’re executing, so they don’t directly reveal how long a particular running query has been in progress. The PDW-specific view targets a particular data-warehouse engine and isn’t the general tool for identifying long-running reports in the Fabric warehouse.