sqldb-operations-cli

Query the Query Store views (sys.query_store_query, sys.query_store_runtime_stats) via sqlcmd against the OLTP endpoint to rank queries by duration, CPU, or logical IO. The skill provides ready-made T-SQL for top resource consumers over the last hour or 24 hours.

Run the live blocking queries against sys.dm_exec_requests and sys.dm_exec_sessions to identify blocked sessions, the head blocker, and the blocking chain. For intermittent blocking, create a database-scoped Extended Events session with a ring_buffer target, then clean it up afterward.

This error occurs when connecting to the SQL analytics endpoint, which has no Query Store or DMVs. Connect to the SQL database (OLTP) endpoint instead to run diagnostic queries.

Check sys.dm_db_tuning_recommendations first because auto-tuning is enabled by default and may create the index automatically. Only use DMV missing-index recommendations, ranked by index_advantage, when auto-tuning has nothing pending.

You need VIEW DATABASE STATE to query DMVs and Query Store views, and ALTER ANY EVENT SESSION to create Extended Events sessions for capturing intermittent blocking. Grant these to the investigating user identity.

Server-scoped DMVs like sys.dm_os_*, trace flags, DBCC TRACEON, and server-scoped or file-target Extended Events are not supported. Use sys.dm_db_resource_stats, Query Store, and database-scoped XE sessions with ring_buffer targets instead.