Fabric IQ: the ontology is now a workspace item and refresh has a price

The demo convinces, the workspace disagrees. In Microsoft Fabric the ontology is now a real item: a REST API, a definition in files and a child graph created on its own — and it is that child that issues the bill. This article gathers what the item really is, why every refresh is full and freshness became a cost decision, the four capacity meters, how far binding actually reaches, three points where the official documentation contradicts itself — and what has to be in place before switching this on in production.

Continue ReadingFabric IQ: the ontology is now a workspace item and refresh has a price

Federate, mirror, or ingest: the decision between Databricks and Fabric

Federating, mirroring, and ingesting are not synonyms — and in Fabric "mirroring" already means three different mechanisms. When to use Lakehouse Federation, when to mirror a catalog or a database into Microsoft Fabric, when to ingest with Lakeflow Connect, what is actually free, and why source permissions do not cross the OneLake boundary.

Continue ReadingFederate, mirror, or ingest: the decision between Databricks and Fabric