Options
SQL Change Automation for Visual Studio 2019 does not create MigrationLog and SchemaSnapShot tables
Evangeline
Posts: 2 New member
I'm using Visual Studio 2019 version 4.8.04084 with SQL Change Automation extension from here https://marketplace.visualstudio.com/items?itemName=vs-publisher-306627.RedgateSqlChangeAutomation
When creating a new SQL Change Automation project with source/target database, it's stuck at 90% for more than 12 hours. I have to terminate Visual Studio manually from task manager. When I go back to look at the project, it generated scripts/folder for baseline/programmable-objects/schema-model. However, it did not generate those two tables __MigrationLog and __SchemaSnapShot in target database.
It used to work few months ago when I did this for another database.
Has anyone encountered this issue?
When creating a new SQL Change Automation project with source/target database, it's stuck at 90% for more than 12 hours. I have to terminate Visual Studio manually from task manager. When I go back to look at the project, it generated scripts/folder for baseline/programmable-objects/schema-model. However, it did not generate those two tables __MigrationLog and __SchemaSnapShot in target database.
It used to work few months ago when I did this for another database.
Has anyone encountered this issue?
Tagged:
Answers
Does this happen even if you create a new project from scratch?
Product Support Engineer
Redgate Software Ltd
Please see our Help Center for detailed guides on how to use our tools
I just realized those tables are created after I "deploy" it.
However, there's no record in table __SchemaSnapshot. Is that normal?
Product Support Engineer
Redgate Software Ltd
Please see our Help Center for detailed guides on how to use our tools