Monitor T-SQL queries (Preview)

Applies to: ✅ SQL analytics endpoint and Warehouse in Microsoft Fabric

Use the Monitor to view your warehouse's running and historical T-SQL queries, long-running queries, and frequently run queries without running T-SQL code. Integrated into the Fabric portal, you can use Monitor to confirm that queries complete successfully, analyze execution patterns, and investigate slower query runs in detail.

Monitor was previously named "Query Activity".

Prerequisites

• You must be an admin in your workspace to access the Monitor. Members, Contributors, and Viewers don't have permission to access this view.

Get started

Launch the Monitor experience from your workspace, the query editor, or the Microsoft Fabric Capacity Metrics app.

• Select More Options (...) next to the warehouse you want to monitor within the workspace view, and select Monitor.

  

• Within the query editor of the warehouse you want to monitor, select Monitor in the ribbon.

  

Open Monitor from the Capacity Metrics app

Use Monitor in warehouse in the Microsoft Fabric Capacity Metrics app to investigate query activity associated with capacity usage. Monitor opens the associated item with a time range based on the selected operation or item detail context.

You need access to the Capacity Metrics app and the workspace Admin role for the selected item. Access to the Capacity Metrics app alone doesn't grant access to Monitor.

1. Open the timepoint page for the capacity usage you want to investigate.
2. In the background operations table, select a supported query operation. The Monitor in warehouse button becomes enabled.
3. Select Monitor in warehouse to open Monitor for the associated item.
4. Review the selected time range and investigate the query activity. Use query text, status, submitter, run source, and duration to narrow your investigation.

If you start from the timepoint item detail page, you don't need to select a record first. For a supported query operation, select Monitor in warehouse to open the associated item with the relevant time range. Select a record first if you want to narrow the range to that operation.

The following operations are supported:

• Warehouse Query - T-SQL statements in a warehouse.
• Warehouse Query (Accelerated) - T-SQL statements in a warehouse with workspace query acceleration enabled.
• SQL Endpoint Query - T-SQL statements in a lakehouse's SQL analytics endpoint.
• SQL Endpoint Query (Accelerated) - T-SQL statements in a lakehouse's SQL analytics endpoint with workspace query acceleration enabled.
• Warehouse Snapshot Query - T-SQL statements on a warehouse snapshot.

For operation definitions, see Data Warehouse operations.

Capacity usage at a timepoint can include smoothed consumption from earlier operations. The selected capacity timepoint and an operation's execution interval aren't necessarily the same. Use the operation context passed to Monitor rather than assuming that every contributing query ran within the displayed capacity timepoint.

Troubleshoot navigation from Capacity Metrics

Query history

On the Query history page, you can review recent query executions and identify patterns in warehouse activity. This view combines a request count chart with a detailed results grid so you can move from a high-level trend to a specific query run.

• Use the request count chart to spot spikes in activity during the selected time range.
• Use the Filter menu to refine the view by Submit time (UTC), Status, Submitted by, Run source, Statement type, and Label.
• Use the search bar to find specific keywords in the query text or other columns.
• Use the time filter to switch quickly between the last 24 hours, last 7 days, last 30 days, or a custom time range.
• Review active filters as removable pills above the chart area. When you apply or remove filters, Monitor refreshes the chart and the query grid to match the current filter set.
• Select Refresh to reload the current results. If you see a query that you want to stop, select the query by using the checkbox and then select Cancel. You're prompted to confirm before the query is canceled. Any unselected queries that are part of the same SQL sessions that you selected are also canceled.

• When you select one or more query runs that share the same query hash, View similar runs becomes available. Use this option to compare executions of the same query pattern and understand whether duration, failures, or resource usage changed across runs.

The chart updates to reflect the current filter selection, making it easier to answer questions such as:

• When did query volume increase?
• Which submitter or run source is associated with a spike in activity?
• Are failed or canceled queries concentrated in a specific time window?

You can also customize the table layout from the column menu:

• Choose which columns appear in the data grid.
• Drag items in the column menu to reorder them.
• Select Apply to update the grid to match the selected column order.

For each query, the following details are available in the Query history grid. Some columns might be hidden by default and can be added from Column options.

The same information regarding running queries can also be found using dynamic management views and Query insights views, for example, queryinsights.exec_requests_history.

Query insights

The other Monitor tabs help you move from history into summarized analysis:

• Long running queries helps you identify queries with consistently higher execution times.
• Frequently run queries helps you find repeated query patterns that might benefit from tuning.

For each query in the Long running queries insight, the following details are provided:

For each query in the Frequently run queries insight, the following details are provided:

To get the most value from these views:

• Start in Query history to identify the time range, submitter, or run source that you want to investigate.
• Use View similar runs to compare executions that share the same query hash.
• Move to Long running queries to identify query patterns with high median duration.
• Review Frequently run queries to find high-volume query shapes that are good candidates for tuning.

The same information regarding completed, failed, and canceled queries from Query history along with aggregated insights can also be found in Query insights in Fabric Data Warehouse.

Limitations

• Depending on the concurrent workload, historical queries can take up to 15 minutes to appear in Monitor.
• Monitor shows only the top 10,000 rows for the current filter selections. To reduce the result set, narrow the time range or add filters.
• If you open Monitor immediately after creating a new warehouse, you might see an Invalid object name queryinsights.exec_requests_history error. This error occurs because the underlying system views aren't yet generated. As a workaround, wait two minutes, and then refresh the page.

Related content

• Billing and utilization reporting in Fabric Data Warehouse
• Query insights in Fabric Data Warehouse
• Monitor connections, sessions, and requests using DMVs