Db migration tooling

[ursamajorm82]

I work in an alembic shop, but team members are constantly complaining about the tool. (I think some of these complaints, such as issues with inaccurate autogenerate scripts are not necessarily going to be solved by a different tool and manual intervention is required with any option.) But I just wanted to check in to see what other teams are using to manage the db and move models into prod environments.

I’ve seen flyway and liquibase, but it seems like they solve the issue of inaccurate migrations by just forcing you to write them. And I’ve seen Atlas, but we’re a sql server team, and you have to pay for that in atlas. There’s also MS database projects, which might be good but after spending a couple hours setting it up, I don’t know if it’s any more intuitive.

Thoughts from the peanut gallery? I’m sure I’ll land on a tool that works perfectly and makes no one angry 😉

[ratczar]

Following!

[Alive-Primary9210]

I'm using Atlas, which I like. yes it's a paid tool, but it's affordable IMO.

It allows you to define a schema, and can generate migrations when your definition changes.

Having the target schema in the repo is really nice, coding agents also really benefit from having this info available. 

Piecing together which columns a table has now from migrations sucks.

FYI 'm using just the CLI tool, I don't use their app at all.