SQL Server Database Detail

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

SQL Server Database Detail shows database-level metrics, properties, workload, files, tables, locks, memory, waits, health checks, and query detail for a selected database.

Database Detail Tabs

Depending on the selected tab, the page can show:

Summary and database properties.
Activity and database workload.
Queries, including slowest, recent, expensive CPU, and expensive I/O categories.
Query detail and execution plan viewing.
Locks and blocking context.
Tables and table data helpers.
Indexes through the dedicated indexes page.
Files and log flush metrics.
Memory and database-level waits.
Change history where available.
Health check summary.

Workflow

Open Databases.
Select a database.
Use the tabs to review the symptom area.
Open query detail for expensive statements.
Load the execution plan where available and drill into expensive operators.
Use database Query Store, indexes, or database health checks for deeper analysis.

How To Use Database Detail

Database Detail is the main workspace for investigating one SQL Server database. Use it after the server-level pages show that a specific database is affected, or when an application team already knows which database owns the problem.

Start with the tab that matches the symptom. Use activity and locks for live blocking, queries for expensive SQL, files for growth or storage issues, waits for delay patterns, and health checks for configuration or maintenance findings. If the same query appears repeatedly, move to Database Query Store or SQL Server Indexes for historical and schema evidence.

This page is also useful for handover because it gathers database-specific context in one place. Capture the database name, time window, affected tab, key finding, and related query or wait evidence before assigning work.

Database Detail FAQ

When should I use Database Detail instead of server-level pages?

Use it when one database is the focus. Use server-level pages when the symptom affects the whole instance.

Which tab should I open first?

Choose the tab that matches the symptom: activity for live issues, queries for workload, files for storage, waits for delays, and health checks for risk review.

Can this page replace Query Store?

No. Database Detail gives broad context, while Query Store provides deeper historical query and plan analysis.