Blog Post

Azure SQL Blog
7 MIN READ

Database watcher for Azure SQL is retiring: simplify your monitoring with Database Hub

LanceWright's avatar
LanceWright
Icon for Microsoft rankMicrosoft
Oct 27, 2026

Today we're announcing the retirement of database watcher for Azure SQL Database and Azure SQL Managed Instance. This includes monitoring for databases in elastic pools. Database watcher won't move to general availability.

Database Hub in Microsoft Fabric gives you a simpler way to understand and manage your database estate:

  • No monitoring infrastructure to manage. Microsoft runs the performance-monitoring telemetry pipeline and storage. You don't need to set up or manage a separate monitoring data store, and there's no separate data-store charge for collecting that telemetry.
  • Issues and suggestions in one place. Identify resources that need attention and review suggestions to improve your database estate.
  • A view beyond SQL. See supported non-SQL resources alongside your SQL estate, with visibility into their available performance signals.
  • More SQL environments. Monitor SQL Server on Azure VMs and SQL Server enabled by Azure Arc. These environments aren't supported by database watcher.
  • A clearer path to investigation. Move from an estate-wide issue to the relevant resource details and performance data.
  • An easier way to start collecting data. Enable supported monitoring without provisioning a watcher or an ADX cluster.

Your databases stay where they are. You can start using Database Hub today and keep your watchers running while you make the transition.

You can continue using your existing watchers until April 30, 2027. Starting November 9, 2026, you won't be able to create new watcher resources or edit existing ones. Existing watchers will continue operating and collecting data until retirement.

Why we're making this change

Thank you to everyone who used database watcher and shared your feedback with us. Database watcher showed the value of an estate-wide performance view. But some customers also told us that managing watcher resources and the data store was burdensome, especially in large and diverse environments. Your feedback helped us understand what worked well, what needed to improve, and ultimately helped to shape Database Hub.

We built Database Hub to streamline that process. Microsoft manages the performance-monitoring infrastructure, so you can spend less time maintaining it and more time improving your databases. Database Hub also brings a broader view of your estate into the same experience. You can review issues and improvement suggestions across supported services, rather than treating SQL performance monitoring as a separate task.

Retirement timeline

Date

What happens

October 27, 2026

Database watcher retirement is announced.

November 9, 2026

- Creating new watcher resources and editing existing resources will be blocked. 
- Existing watchers will continue to operate.

During the transition

- Existing watchers continue collecting data until April 30, 2027.
- You can use Database Hub alongside your watchers while you move.

April 30, 2027

- All existing database watcher resources will enter into a stopped state and will stop collecting performance monitoring data. 
- After this date, you will not be able to start the watcher resources.

 

What you can do in Database Hub

Database Hub helps you understand where your estate needs attention, not just how an individual SQL database is performing:

  • Identify issues. Use Overview and Estate to find resources that need investigation.
  • Find opportunities to improve. Review suggestions for supported resources and follow through to the relevant configuration or investigation experience.
  • See beyond SQL. Include supported non-SQL services in your estate view. For example, review available performance metrics for Azure Database for PostgreSQL flexible server.

Available signals and actions vary by service. See the Database Hub overview for supported resources and capabilities.

Investigate SQL performance

Start with a performance question you already need to answer. For example, if CPU usage is higher than expected:

  1. Find the resources to investigate. Use Overview to identify areas that need attention. Open Estate and narrow the view to the subscriptions or resource groups you manage.
  2. Explore the performance signals. On the Performance page, use the Microsoft SQL dashboard to review CPU and other workload signals for your selected resources.
  3. Go deeper when you need to. Adjust the time range to investigate a spike. Query the underlying telemetry with KQL when you need your own analysis.

That gives you a path from an estate-wide view to a focused investigation without running a separate monitoring data store.

See the SQL monitoring walkthrough for the detailed flow.

You can get started with a Fabric Free license. Accessing Database Hub doesn't require Fabric capacity, and enabling supported performance monitoring doesn't incur an extra cost.

Additional workflows, such as custom dashboards and Activator alerts, can have separate capacity or licensing requirements.

Looking ahead: Database Agents

In the future, we'll bring Database Agents into Database Hub to help you use AI and agents to better manage your database estate. We'll share more as these capabilities become available.

More SQL monitoring capabilities before retirement

We're bringing additional performance-monitoring capabilities to Database Hub to help you build a more complete view of your SQL estate. Before database watcher retires on April 30, 2027, we'll add support for:

  • Azure SQL Managed Instance
  • Azure SQL elastic pools and their databases
  • Secondary replicas

You can start using Database Hub now. As these capabilities become available, use them alongside your existing watchers to bring more of your SQL monitoring into the new experience.

For current availability and regional requirements, see Enable performance monitoring for Microsoft SQL.

Start today

You don't need to complete your transition to start seeing value.

  1. Open Database Hub. Sign in to Database Hub. On the Estate page, find an Azure SQL database you manage. If your organization hasn't enabled the preview, ask your Fabric administrator to enable access.
  2. Start collecting data now. Microsoft will enable performance monitoring for existing Azure SQL Database resources over the coming weeks. You don't have to wait. Select an eligible database on Estate and choose Enable Performance Monitoring, or follow the enablement instructions.
  3. Explore your first performance view. Once data is available, open Performance and select the relevant resources in the Microsoft SQL dashboard. Choose a time range and review the signals for a workload you know.

The first goal is simple: find a database you manage and see its performance data. Keep your watcher running while you get familiar with the experience.

If a resource or its data doesn't appear, use the troubleshooting checks for access and monitoring setup.

Complete your transition before April 30, 2027

As you confirm that your database estate is appearing in Database Hub, work through the parts of your monitoring setup that you want to carry forward:

  1. Compare the monitoring you rely on. Use Database Hub alongside your watchers to validate the signals and dashboards your team needs. Bring additional targets into the experience as new monitoring capabilities become available.
  2. Adapt your custom queries. Review your KQL against Database Hub performance telemetry. Test the queries you use for operational decisions.
  3. Recreate and test your alerts. For alerts based on a custom dashboard, create a SQL monitor from a template. Then follow Create Activator alerts for a Real-Time Dashboard. This path requires a workspace with Fabric-enabled capacity. Confirm that each alert's query and notifications work before removing the existing alert.
  4. Retire your watcher when you're ready. Once you've validated the monitoring you need, follow the watcher management guidance to delete watcher resources you no longer need.
  5. Decide what history to keep. Keep your existing data store if you still need its history. Export any data you want to retain before deprovisioning resources.

Your historical data stays under your control

Retirement stops database watcher data collection. It won't stop or deprovision your Azure Data Explorer resources or Fabric Eventhouse. Existing data remains subject to your retention settings.

You'll continue paying for those resources unless you deprovision them yourself. When you're ready to clean up:

  • Check whether an ADX cluster or Eventhouse serves other workloads before deleting it.
  • Review the associated Fabric capacity. Deleting an Eventhouse doesn't automatically stop charges for retained or shared capacity.
  • Remove configured alerts you no longer need to avoid their ongoing charges.

Deleting a watcher doesn't automatically delete its data store or alerts. You can keep historical data while using Database Hub for new monitoring.

Frequently asked questions

Will existing watchers stop collecting data on October 27, 2026?

No. The announcement and shutdown are separate milestones. Existing collection continues during the transition until April 30, 2027.

Can I create or edit a watcher during the transition?

Starting November 9, 2026, you won't be able to create new watcher resources or edit existing ones. Your existing watchers will continue operating until April 30, 2027.

Will my historical data be deleted?

No. Database watcher will stop collecting performance data when it retires on April 30, 2027. Retirement won't stop or deprovision your Azure Data Explorer resources or Fabric Eventhouse. Your retention settings and resource-management choices still apply.

Will my existing monitoring costs stop automatically?

No. Azure Data Explorer and Fabric Eventhouse resources won't be stopped or deprovisioned as part of this retirement. You'll continue paying for those resources until you deprovision them yourself.

Retained or shared Fabric capacity can continue to incur charges after an Eventhouse is deleted. Review configured alerts for ongoing costs too.

What happens to my alert rules after April 30, 2027?

Retirement won't automatically delete your existing alert rules. However, database watcher will stop collecting new performance data, so those rules should no longer be relied on to monitor current database conditions.

Before retirement, recreate and test the alerts you need using Database Hub telemetry. Disable or delete old rules you no longer need to avoid unwanted notifications and ongoing charges.

What if I monitor Azure SQL Managed Instance or databases in elastic pools?

We're adding performance monitoring for these scenarios before database watcher retires on April 30, 2027. You can start exploring Database Hub now. Keep your watcher running alongside it as these capabilities become available.

Will Microsoft enable performance monitoring for my existing SQL databases?

Yes. Microsoft will enable performance monitoring for existing Azure SQL Database resources over the coming weeks. If you'd like to start collecting data sooner, enable it now.

Do I need to move my databases into Fabric?

No. Database Hub provides a monitoring experience for supported resources in their existing environments.

Learn more

Blog posts

Microsoft Learn documentation

Updated Oct 26, 2026
Version 1.0
Comments have been turned off for this post