Home > Docs > Features > Database Hub

🗄️ Database Hub — Unified Database Management¶

Last Updated: 2026-04-22 | Version: 1.0.0

⚠️ Early Access Notice: Database Hub is currently in Early Access (announced March 2026). Features, UI, and capabilities may change significantly before general availability. Do not use for production-critical workflows. Early Access requires opt-in via Fabric Admin portal.

📑 Table of Contents¶

• 🎯 Overview
• 🏗️ Architecture Overview
• ⚙️ Setup and Configuration
• 📊 Core Capabilities
• 🎰 Casino Use Case
• 🏛️ Federal Use Case
• 🔌 Integration Points
• ⚡ Performance and Health Monitoring
• ⚠️ Limitations and Early Access Status
• 📚 References

🎯 Overview¶

Database Hub is a unified management experience in Microsoft Fabric that provides a single pane of glass for discovering, monitoring, and managing databases across edge, cloud, and Fabric environments. Instead of switching between Azure Portal, SQL Server Management Studio, and the Fabric Portal to manage different database assets, Database Hub brings all database inventory into one centralized view.

Database Hub aggregates metadata from:

• SQL Database in Fabric -- Native Fabric SQL databases
• Mirrored Databases -- Real-time replicas of Azure SQL, Cosmos DB, Snowflake, and others
• Azure SQL Database -- Cloud SQL databases linked via Azure Resource Manager
• SQL Server (on-premises/VM) -- Edge databases registered through Azure Arc
• Warehouses -- Fabric Warehouse items

Key Capabilities¶

Where Database Hub Fits¶

flowchart TB
    subgraph Edge["🏢 On-Premises / Edge"]
        SQL1["SQL Server<br/>(via Azure Arc)"]
        SQL2["SQL Server<br/>(Gaming System DB)"]
    end

    subgraph Cloud["☁️ Azure"]
        ASQL["Azure SQL Database"]
        CDB["Cosmos DB"]
    end

    subgraph Fabric["🔷 Microsoft Fabric"]
        SQLF["SQL Database<br/>in Fabric"]
        MDB["Mirrored<br/>Databases"]
        WH["Warehouse"]
    end

    subgraph Hub["🗄️ Database Hub"]
        INV["Unified Inventory"]
        MON["Health Monitoring"]
        PERF["Performance Insights"]
        SEARCH["Cross-Environment Search"]
    end

    Edge --> Hub
    Cloud --> Hub
    Fabric --> Hub

    style Edge fill:#95A5A6,stroke:#7F8C8D,color:#fff
    style Cloud fill:#2471A3,stroke:#1A5276,color:#fff
    style Fabric fill:#E67E22,stroke:#CA6F1E,color:#fff
    style Hub fill:#27AE60,stroke:#1E8449,color:#fff

🏗️ Architecture Overview¶

Database Hub operates as a metadata aggregation layer. It does not store or replicate data -- it connects to existing database management APIs to gather metadata, health metrics, and performance telemetry.

flowchart LR
    subgraph Connectors["🔌 Metadata Connectors"]
        ARC["Azure Arc<br/>SQL Connector"]
        ARM["Azure Resource<br/>Manager API"]
        FAB["Fabric Internal<br/>Metadata API"]
    end

    subgraph Hub["🗄️ Database Hub"]
        CACHE["Metadata Cache<br/>(refreshed every 5 min)"]
        SEARCH["Search Index"]
        HEALTH["Health Aggregator"]
    end

    subgraph UI["🖥️ User Interface"]
        LIST["Database List"]
        DETAIL["Database Detail"]
        ALERT["Health Alerts"]
    end

    Connectors --> Hub --> UI

    style Connectors fill:#8E44AD,stroke:#6C3483,color:#fff
    style Hub fill:#2471A3,stroke:#1A5276,color:#fff
    style UI fill:#27AE60,stroke:#1E8449,color:#fff

⚙️ Setup and Configuration¶

Prerequisites¶

⚠️ Early Access: Enable Database Hub via Fabric Admin Portal → Preview Features → Database Hub

1. Fabric capacity: F64 or higher SKU
2. Admin permissions: Fabric Administrator or Workspace Administrator role
3. Azure Arc (optional): For on-premises SQL Server registration
4. Network connectivity: Hub must reach Azure Resource Manager APIs

Step 1: Enable Database Hub (Early Access)¶

Fabric Admin Portal → Tenant Settings → Preview Features
  → Database Hub (Early Access): Enable
  → Allowed Security Groups: [Select groups with access]

Step 2: Register Database Sources¶

Fabric-Native Databases (Automatic)¶

SQL Database in Fabric, Mirrored Databases, and Warehouses appear automatically in Database Hub once the feature is enabled. No additional registration is needed.

Azure SQL Databases¶

Database Hub → + Register Database → Azure SQL Database
  Subscription: [Select Azure subscription]
  Resource Group: [Select resource group]
  Server: [Select Azure SQL Server]
  Databases: [Select one or more databases]
  Authentication: Entra ID (recommended) or SQL Authentication

On-Premises SQL Server (via Azure Arc)¶

Database Hub → + Register Database → SQL Server (Arc)
  Arc Resource: [Select Arc-enabled SQL Server]
  Instance: [Select instance]
  Databases: [Select databases to register]
  Connectivity: Azure Arc agent (outbound HTTPS 443)

Step 3: Configure Health Alerts¶

Database Hub → Settings → Health Alerts
  CPU Threshold: 80% (warning), 95% (critical)
  Storage Threshold: 85% (warning), 95% (critical)
  Mirroring Lag: 5 minutes (warning), 15 minutes (critical)
  Notification: Email / Teams channel / Data Activator

📊 Core Capabilities¶

Unified Database Inventory¶

The inventory view shows all registered databases in a sortable, filterable table:

Cross-Environment Search¶

Search for a table or column name across all registered databases:

Database Hub → Search: "player_transactions"

Results:
  ✅ lh_bronze.bronze_player_transactions (SQL Database in Fabric, ws-gaming)
  ✅ casino_ops.dbo.PlayerTransactions (Azure SQL, eastus2)
  ✅ mirror_casino_ops.PlayerTransactions (Mirrored DB, ws-gaming)
  ✅ gaming_dw.dbo.fact_player_transactions (Arc SQL Server, on-prem-01)

Connection String Manager¶

One-click connection string generation for any registered database:

Database Hub → [Select Database] → Connect
  ADO.NET: Server=tcp:xxxxx.database.fabric.microsoft.com,1433;...
  JDBC: jdbc:sqlserver://xxxxx.database.fabric.microsoft.com:1433;...
  ODBC: Driver={ODBC Driver 18 for SQL Server};Server=...
  Python (pyodbc): connection_string = "DRIVER={ODBC Driver 18}..."

🎰 Casino Use Case¶

Unified View of Gaming System Databases¶

A casino operation typically runs multiple database systems:

Without Database Hub, the DBA must check Azure Portal for casino_ops, SSMS for the on-premises server, and Fabric Portal for the mirror and Lakehouse. With Database Hub, all five databases appear in one view with health status, storage, and performance metrics side by side.

Mirroring Lag Monitoring¶

Database Hub surfaces mirroring health for the mirror_casino_ops Mirrored Database:

Database Hub → mirror_casino_ops → Mirroring Status
  Replication Lag: 12 seconds ✅
  Tables Mirrored: 47 / 47
  Last Sync: 2026-04-22T14:30:12Z
  Throughput: 2,450 rows/sec
  Status: Healthy

If mirroring lag exceeds the configured threshold (e.g., 5 minutes), Database Hub triggers a health alert -- critical for compliance workflows where near-real-time data is required for CTR/SAR monitoring.

🏛️ Federal Use Case¶

Multi-Agency Database Inventory¶

Federal organizations managing data across multiple agencies can use Database Hub to maintain a centralized catalog:

Cross-Agency Data Discovery¶

A federal data analyst searching for "loan" across all registered databases:

Database Hub → Search: "loan"

Results:
  ✅ sba_loan_programs.dbo.ppp_loans (SQL Database in Fabric, ws-sba) [CUI]
  ✅ sba_loan_programs.dbo.loan_disbursements (SQL Database in Fabric, ws-sba) [CUI]
  ✅ legacy_grants_db.dbo.SBA_Loans_Archive (Arc SQL Server, dc-east) [CUI]
  ⛔ Access Denied: usda_loan_guarantees (Mirrored DB, ws-usda) [insufficient permissions]

The search respects sensitivity labels and Purview policies -- the analyst sees results from databases they have access to, while restricted databases show an access-denied indicator.

FISMA Compliance Dashboard¶

Database Hub provides a compliance-oriented view showing database health aligned with FISMA controls:

🔌 Integration Points¶

⚡ Performance and Health Monitoring¶

Database Hub aggregates performance metrics from all registered databases:

⚠️ Limitations and Early Access Status¶

⚠️ Early Access Disclaimer: Database Hub is in Early Access. The following limitations are expected to evolve before GA.

📚 References¶

🔗 Related Documents¶

• Fabric SQL Database -- Native SQL databases managed through Database Hub
• Mirroring -- Real-time database mirroring monitored by Database Hub
• OneLake Catalog -- Data discovery that complements Database Hub
• Workspace Monitoring -- Workspace-level monitoring alongside database monitoring
• Identity & RBAC Patterns -- Access control for database assets
• Architecture -- System architecture overview

📝 Document Metadata - Author: Documentation Team - Reviewers: Data Engineering, Database Administration, Federal Operations, Security - Classification: Internal - Next Review: 2026-07-22