Paid Database Visualization Tools for PostgreSQL, MySQL and SQL Server: What They Cost

DbSchema shows PostgreSQL, MySQL and SQL Server in the same diagrams with one licence. You pay once, not per database. DbSchema Pro costs 294 USD once per user, or 29.40 USD a month. The free Community Edition already connects to all three and draws their diagrams. Over three years, Pro costs 444 USD if you also take the two optional update years.

One licence covers all three databases

DbSchema sells one product for every database it supports. You pick PostgreSQL, MySQL or SQL Server in the same window. Every edition, the free one included, connects to all of them. Say your application runs on PostgreSQL, a legacy system on MySQL and reporting on SQL Server. Your team still buys one licence per person.

Check this point on every quote you get. Some vendors sell a separate product per database. Navicat, for example, sells Navicat for MySQL, Navicat for PostgreSQL and Navicat for SQL Server. Its Navicat Premium product connects to several databases. That is how its products page listed them on 6 November 2026.

What the free edition shows and what Pro adds

You don't need to pay to see a structure. The Community Edition is free for any use. It connects, reverse-engineers the schema and draws interactive diagrams. You pay for what you do with the diagram afterwards:

What to see: the free edition answers "what is in this database?", and Pro is for keeping the answer and sharing it. The rows come from the edition comparison and the documentation page.

Which database visualization tool to buy explains why reading the structure from the database beats drawing it by hand.

What three years cost

Compare the cost over the time you'll use the tool, not the first invoice. DbSchema sells Pro as a perpetual licence or by the month. DBeaver Enterprise, a database client that also draws ER diagrams, is sold as an annual subscription. dbeaver.com listed it at 255 USD a year on 6 November 2026.

What to see: the perpetual DbSchema licence is the lowest three-year total, and the monthly plan suits a short project.

If you stop paying for updates, a perpetual DbSchema licence keeps working on the version you own. Perpetual or subscription for database tooling works through the break-even month by month.

MySQL can hide foreign keys from any tool

A paid tool reads the same catalog as a free one, so it can only draw the foreign keys the database stored. PostgreSQL keeps every declared foreign key in its pg_constraint catalog. In MySQL, the 8.4 reference manual names only InnoDB and NDB as the storage engines whose tables support foreign key checking. This table uses the older MyISAM storage engine:

CREATE TABLE order_notes (
  id INT PRIMARY KEY,
  order_id INT,
  FOREIGN KEY (order_id) REFERENCES orders (id)
) ENGINE=MyISAM;

MySQL created the table without an error or a warning. Asking the catalog for the foreign keys of the schema returns only the one on orders, which is an InnoDB table:

SELECT table_name, referenced_table_name, constraint_name
FROM information_schema.referential_constraints
WHERE constraint_schema = 'shop'
ORDER BY table_name;

No tool can draw a line from order_notes to orders, because the database never stored it. In DbSchema you add it as a virtual foreign key, which lives in the model and never in the database. Keeping it means saving the model, which needs DbSchema Pro.

Pick the licence type that fits who pays

DbSchema lists three prices for the same Pro features, by who buys it:

What to see: a company buys business licences, and the other two are for personal use and education. Prices are per developer: one person installs DbSchema on two computers and uses one at a time. For people who need Pro only now and then, a team can share seats with a floating licence.

Download DbSchema, connect to your PostgreSQL, MySQL or SQL Server database and look at the diagram in the free Community Edition. When you want to save the model, document it or query it visually, DbSchema Pro covers all three databases with one licence.

Sources

1. DbSchema: Pricing and edition comparison
2. DbSchema: Connect to Database
3. DbSchema: Schema Documentation
4. DbSchema: Foreign Keys
5. PostgreSQL 16 documentation: pg_constraint