Sqldw Operations Cli
Analyze Fabric Data Warehouse performance via CLI using sqlcmd and queryinsights views. Diagnose slow queries, SQL pool pressure, cache coldness, and recommend clustering keys. Triggers: "DW slow query analysis", "slowest queries warehouse", "queryinsights long running", "warehouse CPU resource consumers", "SQL pool pressure window", "pressure events warehouse", "DW cache warmth cold start", "cache warmth analysis", "warehouse cluster key recommendation", "cluster tables performance", "DW performance baseline comparison", "performance degraded warehouse", "warehouse user query patterns", "queryinsights diagnostics", "DW optimization sqlcmd".
30-Second Summary
Sqldw Operations Cli is an agent-readable workflow from microsoft/skills-for-fabric for sqldw operations cli.
It gives the agent a trigger, ordered guidance, and source-backed checks instead of treating sqldw operations cli as a generic tool.
Use it as a brief only while the linked SKILL.md remains available and the risk boundary is still accurate.
1-Minute Read
What it is
Sqldw Operations Cli packages instructions from microsoft/skills-for-fabric into a reusable agent skill brief. The original source is a public SKILL.md file, so the brief can point readers back to the executable workflow instead of a product landing page.
When to use it
Use it when a user asks for help around sqldw operations cli and the agent needs a repeatable workflow, checklist, or review path rather than broad background information.
How to test it first
Open the linked SKILL.md, confirm the trigger and procedure still match sqldw operations cli, list the risk boundary, then ask the agent to apply the smallest read-only step to a sample task.
Watch out
Do not present this as a generic app or platform. Keep the scope tied to microsoft/skills-for-fabric. Risk boundary: CI/CD, deploy, release, rollback, and migration steps must start with read-only inspection and an approval gate; database, Fabric workspace, notebook, lakehouse, warehouse, or Power BI changes need credential and production-data approval; cloud resources, RBAC, credentials, tokens, and private keys must not be changed or exposed without a separate approval; Microsoft Fabric-specific workflow; do not describe it as a generic data engineering skill.