This version of SQL Change Automation is for Visual Studio 2017 and 2019.
For Visual Studio 2017 Enterprise subscribers – this listing will install SQL Change Automation Core, a free extension included in VSE.
For all other compatible versions – this listing will install a 28-day trial of SQL Change Automation.
Redgate SQL Change Automation is a migrations-first database development and deployment tool inside Visual Studio, allowing you to extend DevOps processes to your SQL Server databases, so you can:
For each database change during development, a migration script is created. At release time these scripts form the building blocks for a full deployment script. By generating and deploying scripts in a predefined order, it saves both time and effort of having to do this release work manually.
Single source of truth
Changes are reviewed in development so any issues are spotted early, unpredictability is eliminated, and this all happens inside Visual Studio where database changes can be source controlled alongside application changes, establishing a single source of truth for both the application and the database.
Its migrations-first approach, together with script verification, means developers can be confident that any database changes are developed early in the lifecycle, are tested and remain immutable from development all the way through to production.
Fit into your existing stack
SQL Change Automation works with existing release management tools such as Team Foundation Server (TFS), Visual Studio Team Services (VSTS), and Octopus Deploy for automated database deployments. This is ideal for developers looking for an easier, more accurate way to deploy their databases from Visual Studio.
The hybrid approach
SQL Change Automation is a ‘hybrid’ tool: it combines the best of both migrations- and state-based approaches to database development and deployment, so database changes are treated in the most sensible and efficient manner. Programmable objects such as stored procedures are handled more effectively, so they can be branched and merged without overwriting changes, and reference data can be source controlled alongside schema changes.
Loading More data ...