Identify Long-Running Query in Fabric Warehouse DMV
You have a Fabric tenant that contains a warehouse. A user discovers that a report that usually takes two minutes to render has been running for 45 minutes and has still not rendered. You need to identify what is preventing the report query from completing. Which dynamic management view (DMV) should you use?
Community Votes
100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests knowledge of specific monitoring tools in Microsoft Fabric. The trap is assuming Azure Synapse-specific DMVs (like sys.dm_pdw_exec_requests) apply to Fabric, whereas Fabric warehouses expose standard SQL Server DMVs.
To diagnose a long-running report query in a Microsoft Fabric warehouse, you must use the sys.dm_exec_requests dynamic management view (DMV). This page clarifies that despite the MPP architecture, Fabric uses standard SQL Server DMVs for monitoring.
Candidates often choose D (sys.dm_pdw_exec_requests) because they associate 'warehouse' with Azure Synapse Analytics (formerly SQL DW), which uses PDW-specific DMVs. However, Fabric is built on a different underlying engine that exposes standard SQL Server views.
Community Discussion (10 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The correct answer is A (sys.dm_exec_requests). Microsoft Fabric warehouses are managed as part of the Fabric platform and utilize standard SQL Server dynamic management views (DMVs) for monitoring and diagnostics. According to Microsoft's official documentation for Fabric data warehouses,sys.dm_exec_requests is the primary DMV used to identify what is preventing a query from completing, including details on wait types, CPU time, and execution status. This aligns with standard T-SQL practices for identifying blocking or long-running queries.Why the Other Options Are Wrong
Option D (sys.dm_pdw_exec_requests) is specific to Azure Synapse Analytics (SQL Data Warehouse) which uses a Massively Parallel Processing (PDW) architecture with distinct system tables. While Fabric shares some conceptual similarities, it does not expose the legacy PDW DMVs. Option B (sys.dm_exec_sessions) provides information about user sessions but lacks the granular request-level execution details needed to diagnose why a specific query is stuck. Option C (sys.dm_exec_connections) monitors network connections and endpoints, not the internal execution state of individual queries.Community Comment Notes
Several community members correctly identified A, citing the official Microsoft Learn documentation link: "https://learn.microsoft.com/en-us/fabric/data-warehouse/monitor-using-dmv". Others argued for D based on the MPP nature of warehouses, but this reflects a common misconception between Azure Synapse and Fabric architectures. As one commenter noted, the key is recognizing that Fabric uses standard SQL Server DMVs rather than Synapse-specific ones.Official Reference
Exam Strategy
When studying for DP-600, distinguish clearly between Azure Synapse Analytics (which uses PDW DMVs) and Microsoft Fabric (which uses standard SQL Server DMVs). Memorize the specific DMVs listed in the Fabric monitoring documentation, as questions often test these specific tool mappings.
Frequently Asked Questions
Why not use sys.dm_pdw_exec_requests for Fabric?
sys.dm_pdw_exec_requests is specific to Azure Synapse Analytics (SQL DW). Fabric warehouses use standard SQL Server DMVs like sys.dm_exec_requests.
Where can I find the official list of Fabric DMVs?
Microsoft's official documentation for Fabric Data Warehouse monitoring lists all supported DMVs, including sys.dm_exec_requests for query diagnosis.
Related Analysis
Practice All DP-600 Questions
Access 115 questions with complete answers and detailed explanations.
View Full DP-600 Practice Test →