Document query metrics limitations on Azure SQL Database - #38582
Document query metrics limitations on Azure SQL Database#38582joeykelroy wants to merge 1 commit into
Conversation
Added information regarding query metrics collection limitations on Azure SQL Database Basic, S0, and S1 tiers, including required permissions and configuration adjustments.
![datadog-official[bot]](https://avatars.githubusercontent.com/in/1358509?s=60&v=4){kind=small}
There was a problem hiding this comment.
The new troubleshooting section contains a malformed Microsoft reference: the rendered text joins Microsoft and sys.dm_exec_plan_attributes as Microsoftsys.dm_exec_plan_attributes, making the permission guidance difficult to follow. The documented query_metrics.disable_secondary_tags setting is valid and selects the integration path that avoids the restricted DMV.
📊 Validated against 4 scenarios · Open Bits AI session
🤖 Datadog Autotest · Commit 7f0f496 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest
| VIEW SERVER PERFORMANCE STATE permission was denied on object 'server', database 'master'. | ||
| ``` | ||
|
|
||
| Collecting query metrics requires reading the sys.dm_exec_plan_attributes dynamic management view. On these service tiers, Azure restricts that view to a server-level principal — the server administrator or the Microsoft Entra administrator as documented in the Microsoftsys.dm_exec_plan_attributes [permissions] [15]. |
There was a problem hiding this comment.
Users troubleshooting missing query metrics may have difficulty identifying or following the Microsoft permissions reference needed to configure the affected Azure SQL tiers.
Assertion details
- Input: Render the added troubleshooting paragraph containing the Microsoft DMV reference.
- Expected:
The referenced DMV and its permissions documentation are presented as readable linked text. - Actual: The source renders the phrase as
Microsoftsys.dm_exec_plan_attributes [permissions] [15]; the missing separator makes the object name and vendor name run together and obscures the reference.
Was this helpful? React 👍 or 👎
🤖 Datadog Autotest · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest
| Collecting query metrics requires reading the sys.dm_exec_plan_attributes dynamic management view. On these service tiers, Azure restricts that view to a server-level principal — the server administrator or the Microsoft Entra administrator as documented in the Microsoftsys.dm_exec_plan_attributes [permissions] [15]. | |
| Collecting query metrics requires reading the `sys.dm_exec_plan_attributes` dynamic management view. On these service tiers, Azure restricts that view to a server-level principal, which is the server administrator or the Microsoft Entra administrator, as documented in the [`sys.dm_exec_plan_attributes` permissions][15]. |
There was a problem hiding this comment.
Slightly amended the above suggestion to add monospace formatting and to remove the em dash
Preview links (active after the
|
janine-c
left a comment
janine-c
left a comment
There was a problem hiding this comment.
Looks great! Just some minor edits. Once we've got that link fixed, we're all good to go 🙂
| VIEW SERVER PERFORMANCE STATE permission was denied on object 'server', database 'master'. | ||
| ``` | ||
|
|
||
| Collecting query metrics requires reading the sys.dm_exec_plan_attributes dynamic management view. On these service tiers, Azure restricts that view to a server-level principal — the server administrator or the Microsoft Entra administrator as documented in the Microsoftsys.dm_exec_plan_attributes [permissions] [15]. |
There was a problem hiding this comment.
Slightly amended the above suggestion to add monospace formatting and to remove the em dash
|
|
||
| Collecting query metrics requires reading the sys.dm_exec_plan_attributes dynamic management view. On these service tiers, Azure restricts that view to a server-level principal — the server administrator or the Microsoft Entra administrator as documented in the Microsoftsys.dm_exec_plan_attributes [permissions] [15]. | ||
|
|
||
| To continue collecting query metrics on affected databases, enable query_metrics.disable_secondary_tags for those instances. |
There was a problem hiding this comment.
| To continue collecting query metrics on affected databases, enable query_metrics.disable_secondary_tags for those instances. | |
| To continue collecting query metrics on affected databases, enable `query_metrics.disable_secondary_tags` for those instances. |
2 participants
Added information regarding query metrics collection limitations on Azure SQL Database Basic, S0, and S1 tiers, including required permissions and configuration adjustments.
What does this PR do? What is the motivation?
Merge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Additional notes