sys.dm_exec_sessions identifies the users actively running warehouse queries
Monitor Fabric items
AnswerCorrect answer: E - sys.dm_exec_sessions lists every active session with its login name, identifying the users currently running queries on Warehouse1.
You have a Fabric workspace that contains a warehouse named Warehouse1. Data is loaded daily into Warehouse1 by using data pipelines and stored procedures. You discover that the daily data load takes longer than expected. You need to monitor Warehouse1 to identify the names of users that are actively running queries. Which view should you use?
100% of anonymous learners picked answer E.
Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
sys.dm_exec_sessions is the server-scoped view carrying user identity for active sessions; sys.dm_exec_requests focuses on executing requests, and queryinsights views are historical summaries.
Query the sys.dm_exec_sessions DMV on Warehouse1: it lists all active sessions with their login names and status, which identifies the users currently running queries while the daily load executes.
Choosing queryinsights.long_running_queries or frequently_run_queries; those views report historical query behavior, not the users currently connected and running queries.
Community Discussion (4 comments)
GHill1982👍 7Selected: E
Use sys.dm_exec_sessions. This view has info about all active user sessions, including user names, session IDs and status.
prabhjot👍 2Selected: E
sys.dm_exec_connections: This view returns information about the current connections to the database instance, such as the client IP address, the login time, and the number of reads and writes. It focuses on connection details rather than identifying specific user queries. sys.dm_exec_requests: This view provides information about requests currently executing on the server, including the session ID, request status, and resource consumption. While it can show active requests, it doesn’t necessarily identify the specific users running the queries. The sys.dm_exec_sessions view, on the other hand, contains information about all active user connections and internal tasks, including details like the session ID and login name. This makes it more suitable for identifying which users are actively running queries in your database.
38578c4👍 1Selected: E
sys.dm_exec_sessions is a server-scope view that shows information about all active user connections and internal tasks
Tuki93👍 2Selected: E
sys.dm_exec_sessions
Comments & Corrections
No comments 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.
Expert Analysis
Why the Answer Is Correct
The goal is to identify the names of users actively running queries. sys.dm_exec_sessions is a server-scoped DMV that shows one row per session, including the login name, session id, and status - exactly the user names and session activity needed to monitor Warehouse1 during the load window.
Why the Other Options Are Wrong
Option A (sys.dm_exec_connections) reports connection-level details such as client addresses and connection times without per-session user context. Option B (sys.dm_exec_requests) shows currently executing requests but is aimed at request-level diagnostics rather than enumerating users. Options C and D (queryinsights.long_running_queries and frequently_run_queries) summarize historical query patterns, not users active right now.
Community Comment Notes
The community is unanimous (E 100). GHill1982 (7 likes) states sys.dm_exec_sessions has info about all active user sessions including user names, and 38578c4 notes it is a server-scoped view showing all active user connections and internal tasks.