The SQL query generated does not have a default integer as 0 in the migration causing failure. INFO [alembic.runtime.migration] Running upgrade 405de8318b3a -> 375a816bbbf4, add new field ...

I have the problem described in this closed issue, that Liquibase does not set the correct default value for addColumn in Microsoft SQL Server. The steps to reproduce described in #3417 worked for me.

Using SQL Server 2000.<P>In a table, I want to default a column 'BillingName' to another column's value in that same table, which is named 'Name'.<P>Using Enterprise ...