FAQ¶
Does Sql2DevOps check or rewrite my SQL? No. It runs your scripts exactly as written, in the order you define, and reports precisely what happened. What the scripts and their rollbacks do is up to you.
How is it different from migration tools such as Flyway or Liquibase?
The unit is a package that is promoted from environment to environment under approval rules, with a signed history, a tracked emergency path and follow-ups. Scripts are plain SQL in the engine's own dialect, including GO batches and psql variables.
Where is my data? Only in your infrastructure. The history lives in a Git repository you own, and the tool never contacts our servers, not even to check the license.
Can I adopt it on an existing database?
Yes. Package your next change and start from there. Scripts that were already run by hand can be recorded with record-manual.
Can two pipelines deploy at the same time? Not to the same database: a lock serializes them, and the control repository handles concurrent pushes with retries.
What if someone edits the history by hand?
sql2devops verify detects edited, removed or reordered events and modified package copies.
Does it work with databases in the cloud? Yes: managed SQL Server and PostgreSQL services use the same protocols. See Databases.
What happens when the license expires? The free edition applies again. Nothing is interrupted halfway and nothing is lost.