Azure SQL Database runs the SQL Server engine as a managed service, and DbSchema treats it exactly like SQL Server: reverse engineer the schemas, diagram and document them, and promote T-SQL changes between environments — from Windows, macOS, or Linux.
Trusted by teams at
Microsoft now patches, backs up, and fails over your databases. What a column actually means, which environment drifted, and what changed before the audit — those questions still land on your team, whether the database is a single instance, an elastic pool, or Managed Instance.
DbSchema answers them with one model: diagrams for the structure, published documentation for the meaning, and T-SQL diffs for the history.
The design work SQL Server DBAs expect, pointed at the cloud.
Give billing its own diagram and user management another, both backed by the same schema model — then export any layout to PDF or SVG for review.
Diff two Azure SQL databases, or the model against a live one, choose which differences count, and get the ALTER and CREATE statements — nothing executes unseen.
Export interactive HTML documentation — diagrams, comments, column details — that compliance reviewers and new hires browse without any database access.
DbSchema keeps the schema in a model file next to your code, separate from the live service. Work on it anywhere, track it in Git, and let Azure see only the SQL you approved.
Model changes against the saved schema — the live database stays untouched.
Branch, diff, and pull-request the model alongside the application code.
Read the statements a change generates before they run in Azure.
Carry the reviewed change through each environment with its own approval.
DbSchema connects through the Microsoft SQL Server JDBC driver,
downloaded automatically, on port 1433. The URL takes the form
jdbc:sqlserver://server.database.windows.net:1433;database=dbname;encrypt=true.
One prerequisite is easy to forget: the Azure SQL server firewall must allow your client IP,
or every login attempt is rejected regardless of credentials.
Authenticate with SQL authentication, or with Azure Active Directory by appending
;authentication=ActiveDirectoryPassword and using your AAD credentials.
Azure SQL Managed Instance connects the same way — the managed instance hostname, port 1433,
identical URL format.
Download without an account — Community Edition free forever, Architect free for 15 days.
Teams working with Azure SQL often use these engines too. Explore dedicated guides and JDBC setup for each.