What WoodFireERD does not support: other database engines, check constraints, renames without data loss, and more.
What WoodFireERD does not support, so you can check it suits your database before you start.
Databases
SQL Server and Azure SQL only. PostgreSQL, MySQL, Oracle and SQLite are not
supported.
Your database is never changed. WoodFireERD only reads it and writes a script for you to
run yourself.
Schema features
Check constraints are not read and not scripted. Tables, columns, primary
keys, foreign keys, defaults, views, procedures, functions, triggers and indexes are.
Renaming a column or table is scripted as a drop and an add, which loses
the data in it. Rename in the database with sp_rename and refresh your
project, or edit the script before you run it.
Identity cannot be added to or removed from an existing column, because
T-SQL cannot do it. The change appears in the script as commented instructions for a
manual table rebuild. Identity on a new column or table is scripted normally.
Database-level DDL triggers and CLR functions are not read.
Unique constraints are not shown as indexes, and disabled indexes are not
listed.
Column names inside a view or procedure are not checked. Syntax is, and
so are the tables and views it names.
Working with others
Projects are files on your machine. There is no shared workspace, team library, comment
thread or version history — share a project by sharing the file.
There is no undo. Closing a project without saving loses your changes.
The diagram
The whole schema is never drawn at once. You pick a table and the diagram grows outward
from it.
A diagram stops at 80 boxes and tells you how many more were reachable.
Box positions are not saved in the project file.
Platforms
The desktop application is Windows only.
The website runs in any modern browser, on any operating system.