Which Diagnostic Setting Tracks Query Start and End Times in Synapse SQL Pool?

DP-203 By islever Editorial Last updated

Short answer

D Exec Requests

Question

You have an Azure subscription that contains an Azure Synapse Analytics dedicated SQL pool named Pool1. You need to monitor Pool1. The solution must ensure that you capture the start and end times of each query completed in Pool1. Which diagnostic setting should you use?
  1. Sql Requests
  2. Request Steps
  3. Dms Workers
  4. Exec Requests Correct Answer

Key Takeaways

This question tests your understanding of Synapse diagnostic log hierarchies, where the common trap is confusing query-level tracking (ExecRequests) with step-level distribution tracking (SqlRequests).

Selecting the correct diagnostic log category for Azure Synapse Analytics is critical for accurate performance monitoring and troubleshooting. Community consensus and official documentation confirm that ExecRequests is the required setting to capture the complete lifecycle timestamps of executed queries.

Common mistake: Candidates frequently choose Sql Requests (Option A) due to its intuitive naming, but this setting actually records granular distribution metrics for individual query steps rather than the overall query execution window.

Expert Analysis

Why the Answer Is Correct

The ExecRequests diagnostic setting directly corresponds to the sys.dm_pdw_exec_requests dynamic management view, which maintains high-level metadata for every submitted query. It explicitly logs the request_id, status, start_time, and end_time, making it the precise configuration for capturing the full duration of completed queries. Configuring this setting ensures you meet the requirement without unnecessary granularity.

Why the Other Options Are Wrong

Sql Requests (Option A) logs the distribution of query steps across compute nodes, not the overarching query timeline. Request Steps (Option B) provides even deeper granularity by tracking intermediate phases within a single query execution. Dms Workers (Option C) monitors background data movement service activities for ETL processes, completely bypassing T-SQL query boundary tracking.

Community Comment Notes

The voting split reflects a common point of confusion, as several candidates initially favored Sql Requests based on surface-level naming. However, experienced users like comment [1] and [4] correctly referenced Microsoft’s official documentation to clarify that ExecRequests handles top-level query tracking while Sql Requests handles step distributions. Leveraging authoritative source material during review eliminates this ambiguity effectively.

Official Reference

https://learn.microsoft.com/en-us/azure/azure-monitor/reference/supported-logs/microsoft-synapse-workspaces-sqlpools-logs

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

Exam Strategy

Always map diagnostic setting names to their underlying system views or architectural scope when studying cloud monitoring features. Differentiate between aggregate-level metrics and granular sub-component logs to quickly eliminate closely named distractors on exam day.

Community Votes

D
55%
A
45%

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

Discussion 11 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 11

  1. [Removed] 👍 4 Answered D
    D seems correct, I was wondering if B could also be correct but apparently it only gives start and end times for the steps of a query and not for the query itself. Following link for reference : https://learn.microsoft.com/en-us/azure/azure-monitor/reference/supported-logs/microsoft-synapse-workspaces-sqlpools-logs
  2. aca357f 👍 2 Answered D
    It should be D. Key Information Provided by sys.dm_pdw_exec_requests: 1. Request ID (request_id): A unique identifier for each query request that was executed or is in progress. You can use this ID to trace the specific query's progress and status. 2. Status (status): The current status of the query. It can show values such as: o Running: The query is currently being executed. o Finished: The query has completed. o Aborted: The query was canceled or failed. o Queued: The query is waiting to be executed. 3. Start Time (start_time): The timestamp when the request started execution. 4. End Time (end_time): The timestamp when the request finished execution (if completed). If still running, this will be NULL. 5. Duration (total_elapsed_time): The total amount of time (in milliseconds) that the request has been running. This can help identify long-running queries.
  3. Legato 👍 2 Answered D
    ExecRequests - "Information about SQL requests or queries in an Azure Synapse dedicated SQL pool." SqlRequests - "Information about query distributions of the steps of SQL requests/queries in an Azure Synapse dedicated SQL pool." Key difference - query distributions of the steps. Source - https://learn.microsoft.com/en-us/azure/azure-monitor/reference/supported-logs/microsoft-synapse-workspaces-sqlpools-logs
  4. Thameur01 👍 2 Answered A
    Sql Requests captures the start and end times of each query executed in the pool, as well as other relevant details like the status, duration, and resource consumption of the query. This diagnostic setting allows you to track query performance, including the time a query starts and completes, which is essential for auditing and performance monitoring.
  5. Aurangzaib 👍 2 Answered A
    This diagnostic setting captures detailed information about each SQL request executed in the Synapse dedicated SQL pool, including the start and end times, duration, and status of the queries. This is the most appropriate setting for monitoring query execution details.
Show 6 more comments
  1. de_examtopics 👍 2 Answered A
    A. Sql Requests. This setting helps monitor and capture essential information such as the start and end times of queries.
  2. f7c717f 👍 1 Answered A
    Sql Requests Explanation: This diagnostic setting captures information about SQL requests, including the start and end times of each query. This is directly relevant to the requirement of capturing the start and end times of each query completed in the SQL pool. Reason Chosen: It directly addresses the requirement to capture the start and end times of each query. For D, It captures execution details but may not provide the specific start and end times of each query as required.
  3. de_examtopics 👍 1 Answered A
    A. Sql Requests The Sql Requests diagnostic setting captures detailed information about SQL requests, including the start and end times of each query, which is essential for monitoring query performance.
  4. fahfouhi94 👍 1 Answered D
    Information about SQL requests or queries in an Azure Synapse dedicated SQL pool.
  5. JamieMcD 👍 2 Answered D
    Exec Requests
  6. HUSSAIN_ALYAFEI 👍 1 Answered A
    i think A

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.

How to Verify Result Set Cache Usage in Azure Synapse SQL Pools?

S-grade

Which Integration Runtime Connects On-Premises Linux Databases to Azure Data Factory?

S-grade

Which Log Analytics table stores ADF pipeline runs in resource-specific mode?

S-grade

Can ARM template export save unpublishable ADF pipelines?

S-grade

← Back to DP-203 Study Guide