Design and Manage Microsoft Dataverse Databases with DbSchema

Build a clearer workflow for Microsoft Dataverse: reverse engineer existing schemas into interactive ER diagrams, model changes visually, and generate reviewed SQL scripts before deployment.

DbSchema is built for visual modeling, schema documentation, and deployment. Keep an offline model in Git, collaborate across teams, and publish documentation that developers, analysts, and stakeholders can navigate in minutes.

DbSchema Database Designer

Download DbSchema See Microsoft Dataverse Features Download Microsoft Dataverse JDBC Driver

What happens after you download?

Get to your first Microsoft Dataverse schema diagram in minutes. No account, no credit card.

1
Install in minutes

Download the installer for Windows, macOS, or Linux and launch DbSchema. No signup required.

2
Connect to Microsoft Dataverse or open a sample

Reverse engineer an existing Microsoft Dataverse database or open a sample model to explore tables, relationships, and indexes.

3
Design, document, and deploy

Edit schema visually, generate documentation, and prepare reviewed migration scripts for safer releases.

Visual Entity Model Exploration for Microsoft Dataverse

Microsoft Dataverse underlies Power Apps, Power Automate, and Dynamics 365, storing application data as tables with relationships managed by the Power Platform. Dataverse exposes a Tabular Data Stream (TDS) endpoint that accepts read-only T-SQL queries, making it accessible to SQL-based tooling without requiring Power Platform SDK access. DbSchema connects to Dataverse via a SQL Server-compatible JDBC driver and renders the entity model as an interactive ER diagram for Power Platform architects and Dynamics 365 developers.

Download DbSchema Free See Microsoft Dataverse Features

ER Diagrams for Dataverse Tables and Relationships

DbSchema connects to the Dataverse TDS endpoint and reads table definitions, column types, and relationships from the Dataverse metadata. The resulting entity diagram maps standard Dataverse tables alongside custom tables, making it easier to understand the data model backing a Power Apps solution or Dynamics 365 module.

Visualizing Microsoft Dataverse entity relationships in DbSchema

Visual Query Builder for Dataverse TDS Queries

DbSchema's query builder lets you construct T-SQL queries against Dataverse tables using a graphical interface, selecting columns and applying filters without writing SQL directly. This is practical for Power Platform developers who need to inspect Dataverse data without manually constructing T-SQL against the TDS endpoint.

Building T-SQL queries against Microsoft Dataverse tables in DbSchema's query builder

Schema Documentation for Power Platform Teams

DbSchema generates HTML schema documentation from the Dataverse entity model, covering table structures, column definitions, and relationships. For Power Platform implementation teams, this documentation provides a structured reference for the data layer underlying Power Apps and Dynamics 365 customizations, useful for handoffs and solution reviews.

Auto-generated Microsoft Dataverse schema documentation in DbSchema

Connecting DbSchema to Microsoft Dataverse

Dataverse exposes a TDS endpoint at port 5558. The JDBC URL format is: jdbc:sqlserver://org.crm.dynamics.com:5558, where org is your environment's organization name. You must first enable the TDS endpoint in your Power Platform environment settings under Settings > Features > TDS endpoint. Authenticate using an Azure AD account that has the Dataverse Security Role assigned. The TDS endpoint supports read-only T-SQL queries against Dataverse tables; DDL statements are not supported through this interface.

Why DbSchema for Microsoft Dataverse

  • Visualize the Dataverse entity model with ER diagrams for Power Platform solutions
  • Run T-SQL queries against Dataverse tables via the TDS endpoint from a desktop client
  • Generate schema documentation for Dataverse-backed Power Apps and Dynamics 365 implementations
  • Explore Dataverse table structures without Power Platform SDK or REST API calls
  • Compare entity schemas between Dataverse development and production environments