Approaches

State-based approachMigrations-based approach
SummaryA single step between the current database state and the desired database state. A CREATE script or the DDL for each object in your database is stored in version control.Changes are captured in “migration” scripts, which are applied in sequence to effect larger, iterative updates to a database. Typically, a series of numerically ordered ALTER scripts.
Key points

Focused on defining the desired end state of your database schema, not how the transition occurs.

A simple approach for getting database automation in place, as the deployment script is auto-generated in seconds prior to upgrade using SQL Compare diffing technology.

Focused on how to get to the desired end state through "migration scripts", which act as the building blocks for the eventual deployment script.

Ideal for more complex database changes as there is no ambiguity in how an upgrade will be performed. SQL Change Automation can use environment-specific variables, allowing server and database names to be different in each environment.

Tools needed

Use SQL Source Control to commit database changes to your version control system in SQL Server Management Studio.

Use SQL Change Automation to put in place Continuous Integration and automated deployments for your database changes.

Make changes to your database in SQL Server Management Studio or Visual Studio, then use the SQL Change Automation Visual Studio extension to commit changes to a SQL Change Automation project.

Use SQL Change Automation to put in place Continuous Integration and automated deployments for your database changes.

What to buy

SQL Toolbelt gives you access to all the tools needed and exclusively contains SQL Change Automation

Find out more about the SQL Toolbelt