Documentation

SQL Simulator lets you see what a migration or schema-change script will actually do before you run it on production. Point it at your existing SQL Server, PostgreSQL, MySQL, or Oracle database, upload the script you're testing, and it walks your schema's foreign keys — and, if you're on Standard or Multi, any triggers, stored procedures, views, or functions those scripts touch, no matter how many steps away — to build a small, FK-consistent sandbox scoped to exactly what you need, not a full clone of the whole database, then actually runs your script against it so you can see what happens first.

This documentation covers the Docker-based, self-serve version of SQL Simulator. If you're looking for 00DB — the Kubernetes-native version built for giving a whole team database access without a direct path to production — see the 00DB product page instead; the two products share the same underlying engine but are documented separately, since their governance and sandbox-lifecycle behavior genuinely differ (see Limitations).