You can keep your development database up-to-date by running any migrations in the SQL Change Automation project that have not been applied to the database. This action will use the migration log table to check which migrations have not been applied to your development database and run them.

This action will likely be necessary in the following scenarios:

• When you create a migration script or update a programmable object or additional script directly instead of generating migrations
• When you pull down new migrations from version control
• When you change development database

Learn more

• Applying changes to a database in SSMS
• Applying changes to a database in Visual Studio