fabric-mirroringlisted

Use for Mirroring in Fabric — the `MirroredDatabase` item that brings an external database or catalog into OneLake with no ETL pipeline. Three kinds, and which each source uses: database mirroring (continuous replication to Delta — Azure SQL DB/MI, SQL Server, Cosmos DB, PostgreSQL, MySQL, Oracle, SAP, BigQuery), metadata mirroring (catalog sync over OneLake shortcuts, data never moves — Snowflake, Databricks, Dremio, AWS Glue, Azure Monitor), open mirroring (you write change files to a landing zone). REST surface (`mirroring.json`, `mountedTables`, `retentionInDays`, startMirroring/getTablesMirroringStatus), landing-zone protocol (`_metadata.json` keyColumns, `__rowMarker__`), extended capabilities (change data feed, mirroring views), and gotchas: 1,000-table cap, 1 TB/day throttle, no views, DDL and capacity-pause reseeds, varchar truncation, RLS/DDM not propagated. For many-source→many-destination ingestion use fabric-copy-job.
wardawgmalvicious/agent-config · ★ 0 · Data & Documents · score 72

Install: claude install-skill wardawgmalvicious/agent-config

# Mirroring in Fabric Mirroring brings an external database or catalog into OneLake as a unit — no ETL pipeline, no orchestration, no compute you allocate. It creates a **`MirroredDatabase`** item plus an autogenerated read-only **SQL analytics endpoint**. There is **no local file artifact** (unlike TMDL or PBIR). You configure mirroring in the portal or through the REST API. ## 1. Three kinds — settle this first Every later answer depends on which kind you are in. All three are called "mirroring", and only one of them copies data. | Kind | Mechanism | Data location | Latency | | --- | --- | --- | --- | | **Database mirroring** | Continuous replication into OneLake as Delta | Copied into OneLake | Changes published as fast as **every 15 s** | | **Metadata mirroring** | Syncs catalog names, schemas, tables; reads through **OneLake shortcuts** | Stays at the source | Source access + shortcut time; no replication step | | **Open mirroring** | *You* write change files to a landing zone; Fabric merges them into Delta | Copied into OneLake | As fast as you land files | **Database mirroring is source-driven, not polled.** The source engine identifies changed data — SQL Server 2025 scans its own transaction log — and publishes to a Fabric landing zone. A replicator engine inside Fabric scans for new files at high frequency and merges them into the target Delta table. **Backoff logic** slows polling for idle tables to avoid loading the source engine, and resumes automatically wh