Huge frustration - Database watcher with two elastic pools

• bjorn.c.w

  SSC Journeyman

  Points: 75

  More actions

  February 5, 2026 at 2:39 pm

  #4730479

  Think there's a reason why this is still in preview, but have someone manage to get this to work properly with two Elastic Pools on one Virtual SQL Server?

  Regardless how I try to add the target, it always end up collection databases from the first Elastic Pool.

  Dashboard would say number of databases equal to first EP, then under EP, it says two pools.

  If I try to add or remove some targets, the whole database watcher goes down, and I sometimes have to drop all targets and create a new fresh datastore.

  Feels like I'm going crazy here, since the Dashboard seems very random for each time I try to set it up.

  Setup:

  * One database watcher

  * One Private Endpoint to Server

  * Two Elastic Pool Targets, pointing to each dbwatcher01/02 database anchors for the pool

  * Added all databases (also tried without this)

  Permission for Identity:

  { "database": "Master", "roles": ["##MS_DatabaseConnector##","##MS_DefinitionReader##","##MS_ServerPerformanceStateReader##"] }

   

  For each database:

  "grantView": ["DATABASE STATE", "DEFINITION"]