MS SQL Server script generation puts DATABASECHANGELOGLOCK prior to USE statement about liquibase HOT 2 OPEN

Hi @jjamieson-va, thank you for reporting this issue.
I have been able to reproduce it with Liquibase version 4.26.0, both with and without Ant. In my case the changesets still ran with no issues, but I agree that the USE statement should be at the beginning of the script.

I'll be leaving this ticket open for the community to propose a fix. Our development team will be available to provide guidance to whoever submits a PR.

Thank you,
Tatiana

from liquibase.

Thank you Tatiana, in most cases the generated script does run without issue. Where we see an error is when using SQL Server Management Studio (SSMS). If the user logged in to SSMS attempts to run the script and they have a database selected in SSMS (e.g. master instead of myDatabase as in the example code above) that does not have the DATABASECHANGELOGLOCK table in it, then the first statement of setting locked=1 fails. The rest of the script does run successfully, but it does create a scenario where the locking is not being applied correctly prior to running the rest of the script.

from liquibase.