/databasehub-cli

name: databasehub-cli
description: "Analyzes Database Hub inventory, health, and security posture through Entra-authenticated Fabric APIs. Use for estate counts; SQL/PostgreSQL CPU, storage, and memory; Cosmos DB availability/RU; authentication/auditing/CMK warnings; and Fabric SQL inventory. Fabric SQL tuning routes to sqldb-cli; Warehouse/Lakehouse/Mirrored Database SQL to sqldw-cli. Triggers: data estate performance, database estate health, database security posture."

> **Telemetry — MANDATORY.** Every `api.fabric.microsoft.com` call must carry > `x-ms-fabric-skill: databasehub-cli` (`az rest`: `--headers "x-ms-fabric-skill=databasehub-cli"`), > including every LRO poll, `fabric_lro` and retry. Snippets omit it — add it anyway.

> **CRITICAL NOTES** > 1. To find the workspace details (including its ID) from workspace name: list all workspaces and, then, use JMESPath filtering > 2. To find the item details (including its ID) from workspace ID, item type, and item name: list all items of that type in that workspace and, then, use JMESPath filtering > 3. Database Hub estate routes are tenant-scoped and usually need neither a workspace nor an item ID. Apply notes 1-2 only when resolving a Fabric SQL catalog item or handing off to an item-specific skill.

Database Hub CLI

Read-only analysis of the database estate exposed through Database Hub. This skill executes live API calls; it does not answer estate questions from generic best practices or from files in the current directory.

Prerequisite knowledge

• [Private-over-public API contract](references/private-over-public-api.md) —

required authentication, transport, pagination, partial-result, error, and route-safety rules.

• [Health drill-downs and filtered snapshots](references/health-drilldowns.md)

— required for named SQL/PostgreSQL resources, per-resource SQL metrics, and filtered health comparisons.

• [Fabric authentication and CLI patterns](../../common/COMMON-CLI.md)
• [Fabric REST API concepts](../../common/COMMON-CORE.md)
• [Databases in Fabric documentation](https://learn.microsoft.com/en-us/fabric/database/)

Select one mode

| Mode | Use when the request asks for | Read next | | --- | --- | --- | | `consumption` | estate counts, subscriptions, resource hierarchy, mixed or engine-specific inventory, saved-view membership, or Fabric SQL catalog entries | [references/consumption.md](references/consumption.md) | | `operations` | cross-engine performance, CPU/storage/memory, Cosmos DB availability/RU use, critical or monitored resources, issues/suggestions, or authentication/auditing/CMK posture | [references/operations.md](references/operations.md) |

For a request spanning both modes, establish inventory scope first, then run operations against that scope. Read each reference before issuing its calls.

Scope and routing boundaries

| Request | Route to | | --- | --- | | Cross-engine estate inventory, health, findings, or security posture | `databasehub-cli` | | Query Store, DMVs, blocking, plans, indexes, T-SQL, or tuning for one Fabric SQL Database | `sqldb-cli` | | Warehouse, Lakehouse SQL endpoint, or Mirrored Database SQL queries and `queryinsights` | `sqldw-cli` | | OneLake domains, labels, workspace/capacity governance, descriptions, endorsement, or tags | `onelake-catalog-cli` | | Fabric workspace item search by name, description, workspace, or type | `search-consumption-cli` | | Eventhouse or KQL Database queries | `eventhouse-cli` | | Azure Monitor mirrored-catalog onboarding and business-impact correlation | `azmon-mirroredcatalogs-operations-cli` |

Fabric SQL support here is **catalog inventory only**. Do not claim Database Hub health or posture coverage for Fabric SQL items. Do not substitute a single-database diagnostic skill for a cross-engine estate request.

Execution contract

1. Confirm the active Entra identity and requested scope. Portal-provided subscriptions, resource filters, or time range are query hints, never authorization. 2. Before the first Database Hub call, read [references/private-over-public-api.md](references/private-over-public-api.md) and the selected mode reference. For named-resource or filtered health drill-downs, read [references/health-drilldowns.md](references/health-drilldowns.md) in addition to `operations.md`, not instead of it. 3. Run the documented live calls through `https://api.fabric.microsoft.com`. 4. Follow every continuation token needed for the requested scope. 5. Report timeframe, aggregation, engine coverage, pagination completeness, `coverage`, and sanitized `errors`. 6. For prompts containing "all", "across", or "estate", complete every required summary/posture call in the selected workflow before answering. Attempt independent required calls even when another route fails; collect each route's error instead of short-circuiting the workflow. Only a page that depends on a failed prior page/token may be skipped. Do not defer required calls as an optional follow-up. 7. If a route or permission is unavailable, state the exact missing coverage; never invent data, switch to a workload host, or query ADX directly.

Must / Prefer / Avoid

MUST

• Remain read-only. Decline create, deploy, enable, disable, update, delete, or

remediation requests and route them to the owning product flow or skill.

• Use a delegated Entra user token for the Fabric API and include

`x-ms-fabric-skill: databasehub-cli` on every request.

• Emit SQL and PostgreSQL health summaries only through the compact

`Select-Object` projection in `operations.md`; never print raw summaries with their `series` arrays. A populated estate's raw summaries exceed the tool-output limit, and answering from partial file reads misattributes metrics.

• For general cross-engine health/performance that includes Cosmos

availability or RU, query Microsoft SQL, PostgreSQL, and Cosmos DB separately; preserve their different metric contracts i