As your KQL database grows, tables gather data from several Eventstreams, functions connect different tables, update policies move and transform data, and materialized views quietly keep aggregated data up to date - all working together behind the scenes
It’s powerful, but it can also be hard to see the full picture.
That’s exactly why we built the Entity Diagram - to give you a simple, visual way to explore how everything in your database connects. No more guessing where data comes from or where it goes, no more wondering what depends on what - just a clear view that helps you understand, troubleshoot, and design with confidence.
What is the Entity Diagram?
The Entity Diagram gives you a visual map of your database. It shows the relationships between your entities: tables, functions, materialized views, update policies, shortcuts, and continuous exports. It also shows cross-database relationships and Eventstream items that serve as data sources for tables, so you can instantly understand how data flows through your system.
You can view details, follow connections, and see what depends on what - all in one place.
View Ingestion Details
You can now see the number of records ingested for each table or materialized view. If the ingestion comes from an Eventstream, you can also see a node for the Eventstream item. If you click on the Eventstream, it will take you directly to it. You can track how data flows through update policies and how it is aggregated into materialized views, giving you a complete view of your data flow.
Spot Schema Violations
The Entity Diagram also flags schema violations between entities, such as broken references from functions to tables or columns, or update policies referencing functions or source tables that no longer exist. This helps you quickly identify and fix issues that might disrupt your data flow.
Whether you are a developer, data engineer, or analyst, the Entity Diagram helps you understand your KQL database clearly. You can explore how tables, functions, materialized views, update policies, and other entities are connected, track data flow including the number of records processed through tables and passed along update policies or materialized views, identify schema violations, and make confident changes with a complete understanding of your database.
To learn more, check out the View an entity diagram in KQL database (preview) documentation.