A JDBC driver is a Java library file (.jar) that enables Java applications — including DbSchema — to communicate with a database over a standard API. The driver translates generic JDBC calls into the network protocol understood by Microsoft Dataverse, so you never have to write low-level socket code. Drivers are typically distributed by the database vendor or as open-source projects.
Every JDBC driver identifies the target database through a connection URL. The URL encodes the hostname, port, database name, and any driver-specific parameters as a single string. The exact syntax varies per driver — the details for Microsoft Dataverse are listed in the section below.
Microsoft Dataverse is a cloud-based data platform that underlies Microsoft Power Apps, Power Automate, and Dynamics 365, providing a secure and scalable data storage service for business applications. It exposes a TDS (Tabular Data Stream) endpoint allowing read-only T-SQL queries against Dataverse tables using standard SQL tooling. Dataverse supports complex data models including relationships, business rules, and role-based access control.
Microsoft Dataverse exposes a TDS (Tabular Data Stream) endpoint on port 5558 that accepts read-only T-SQL queries. Authentication is via Azure Active Directory (Azure AD). Use authentication=ActiveDirectoryPassword or authentication=ActiveDirectoryInteractive in the JDBC URL. The TDS endpoint is available for Dataverse environments in Power Apps.
DbSchema connects to Microsoft Dataverse via the TDS endpoint using the SQL Server JDBC driver, enabling visualization of Dataverse table schemas, running read-only T-SQL queries against Dataverse data, and documenting Power Platform data structures for enterprise governance.
Have connection issues? Contact the DbSchema team for help.
Once the JDBC driver is configured, DbSchema connects to your Microsoft Dataverse database and gives you a full graphical workbench — no command-line required. Available as a free Community Edition and a full-featured PRO Edition. No registration needed to get started.
Reverse-engineer your Microsoft Dataverse schema into a drag-and-drop ER diagram. Arrange tables visually, add new columns, define foreign keys, and let DbSchema generate the DDL — all without writing SQL by hand.
Compose Microsoft Dataverse queries by clicking on tables and columns — no SQL knowledge required. Add joins, filters, groupings, and aggregations through a point-and-click interface, then copy the generated SQL or run it directly against the live database.
Browse Microsoft Dataverse table data and follow foreign key relationships across tables in a single view. Edit cells inline, filter rows, and paginate through large datasets — all without leaving the explorer.
Compare your Microsoft Dataverse schema across development, staging, and production environments. DbSchema generates the exact ALTER statements needed to close the gap and lets you review every change before executing — reducing the risk of unintended schema drift.
Write and execute Microsoft Dataverse queries in the integrated SQL editor with schema-aware autocomplete, syntax highlighting, and instant result display. Run scripts, inspect execution plans, and export results to CSV or JSON from a single interface.
Generate a static HTML site documenting every table, column, type, index, and relationship in your Microsoft Dataverse schema. Share it with your team or embed it in your project wiki — no extra tooling required.
For the full feature list and edition comparison, visit the DbSchema PRO Edition page.