Identify Long-Running Query in Fabric Warehouse DMV

DP-600 By islever Editorial Last updated

Short answer

A Use sys.dm_exec_requests to monitor query execution status and wait conditions in a Microsoft Fabric warehouse.

Question

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?
  1. sys.dm_exec_requests Correct Answer
  2. sys.dm_exec_sessions
  3. sys.dm_exec_connections
  4. sys.dm_pdw_exec_requests

Key Takeaways

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.

Common mistake: 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.

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

https://learn.microsoft.com/en-us/fabric/data-warehouse/monitor-using-dmv

This link opens the official vendor documentation in a new tab.

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.

More DP-600 FAQ →

Community Votes

A
100%

100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 10 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 10

  1. Sanji931 👍 14 Answered A
    Answer is A. https://learn.microsoft.com/en-us/fabric/data-warehouse/monitor-using-dmv
  2. rlo123 👍 3
    D. A or D are really close, but since it is Azure Synapse Analytics D is probably the best answer. Why sys.dm_pdw_exec_requests is better for this Fabric scenario: Fabric's MPP architecture: Fabric warehouses utilize a distributed architecture where queries are broken down and processed across multiple compute nodes. This is why sys.dm_pdw_exec_requests is the ideal tool. MPP-specific insights: This DMV gives you visibility into how the query is being executed across the nodes, which can reveal bottlenecks or performance issues that wouldn't be apparent in sys.dm_exec_requests. Targeted troubleshooting: With the MPP-specific data from sys.dm_pdw_exec_requests, you can pinpoint the exact steps or nodes causing the slow performance, leading to a more efficient resolution.
  3. dvenkatesh 👍 3
    Answer would be D, I guess... Here the key word might be warehouse... The sys.dm_exec_requests dynamic management view is used in SQL Server to provide information about each request that is executing within SQL Server. On the other hand, the sys.dm_pdw_exec_requests dynamic management view is used in Azure SQL Data Warehouse to provide similar information about each request executing within the data warehouse environment. Both views offer insights into the current status and details of queries running in their respective environments.
  4. Pegooli 👍 2 Answered D
    sys.dm_pdw_exec_requests: This DMV provides information about the status of requests (queries) executed in SQL Data Warehouse (now known as Azure Synapse Analytics) environments. It includes details about query execution, such as start time, end time, status, and any error messages. This DMV is particularly useful for diagnosing long-running or stuck queries.
  5. MultiCloudIronMan 👍 1 Answered D
    Given that Fabric uses a Massively Parallel Processing (MPP) architecture similar to Azure Synapse Analytics, sys.dm_pdw_exec_requests (Option D) could indeed be relevant for monitoring requests in this environment.
Show 5 more comments
  1. XiltroX 👍 1 Answered C
    Answer is C https://learn.microsoft.com/en-us/sql/relational-databases/system-dynamic-management-views/sys-dm-exec-connections-transact-sql?view=sql-server-ver16
  2. stilferx 👍 1 Answered A
    IMHO, "A", it may be found here: https://learn.microsoft.com/en-us/fabric/data-warehouse/monitor-using-dmv#identify-and-kill-a-long-running-query
  3. Estratech 👍 1 Answered A
    You can use the sys.dm_exec_requests dynamic management view (DMV) to identify what is preventing the report query from completing 1.
  4. azure_bimonster 👍 2 Answered A
    A would be correct
  5. Rakesh16 👍 1 Answered A
    sys.dm_exec_requests

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Fabric Deployment Pipeline Folder Structure Behavior

S-grade

Accessing OneLake Shortcuts in Fabric Notebooks

S-grade

Direct Lake Fallback to DirectQuery with Row-Level Security

S-grade

Displaying All Rows in Power BI Python Visuals

S-grade

Practice All DP-600 Questions

Access 115 questions with complete answers and detailed explanations.

View Full DP-600 Practice Test →

← Back to DP-600 Study Guide