Azure SQL Activity

Start Here

Manual Home Installation Getting Started Licensing Servers Connect Database Servers Troubleshoot Connectivity Host OS Login Enable WMI Multi-Engine Settings

Console

Console Overview Enterprise View AI Assistant Execution Plans Alerts Custom Alerts Reports Settings Service Log Connectivity Log Web Log About

PostgreSQL

Overview Connection and Permissions Activity Databases Queries Waits Memory I/O Indexes Deadlocks Server Log Settings Permissions Health Checks Alerts Performance Tuning

MySQL/MariaDB

Overview Connection and Permissions Activity Databases Queries Memory I/O InnoDB Permissions Deadlocks Health Checks Alerts Performance Tuning

Oracle

Overview Connection and Permissions Activity Databases Queries Waits Memory Health Checks Alerts Performance Tuning

Settings And Integrations

Security SQL Options Email Server Alert Recipients Recipient Groups Server Groups Cloud Providers Web Proxy Slack Microsoft Teams PagerDuty Jira Performance Logging AI Provider MCP Server

Legacy Documentation

Azure SQL Activity shows active, blocking, blocked, and idle sessions for an individual Azure SQL database. It is the first page to open when users report slow or stuck workload.

Tabs

Active: current running sessions.
Blocking: sessions blocking others.
Blocked: sessions waiting on blockers.
Idle Connections: connected but idle sessions.

Session Detail

Selecting a session can show SQL statement text, locks, waits, and an estimated execution plan where available.

Workflow

Open the Azure SQL database.
Select Activity.
Review active and blocking tabs.
Open session detail for the statement, locks, waits, and estimated plan.
Review Azure SQL Execution Plans when an estimated plan is available.
Continue to Locks, Waits, or Queries.

How To Interpret Azure SQL Activity

Azure SQL Activity is the best starting point when an Azure SQL database feels slow right now. Focus first on blocked and blocking sessions, then long-running active sessions, then repeated idle connections that may indicate application connection handling issues.

Session detail can connect one user complaint to the SQL statement, lock information, wait information, and estimated plan. Use that detail to decide whether the next step is query tuning, index review, lock investigation, service tier review, or elastic pool analysis.

When the estimated plan is available, drill into expensive operators, warnings, predicates, and missing index evidence before recommending a change. You can also pass the plan to the AI Assistant for an explanation that uses the selected plan context.