Setting Up SQL Change Automation
Published 12 June 2018
This guide will walk you through setting up the different components of a SQL Change Automaton pipeline.
If you're evaluating SQL Change Automation, we recommend using a contained, non-essential environment. Any activities carried out on production or otherwise important systems are against our advice and at your own risk. We're unable to accept responsibility for any issues arising from your evaluation of SQL Change Automation.
Setting up SQL Change Automation on a development environment
- Select a database on a SQL Server instance to be your development database
- Pick a client machine on which to install SQL Change Automation
- Ensure SQL Server Management Studio and Visual Studio are installed on the client machine
- Install a version control system on the client machine
- Ensure the client machine can connect to the SQL Server instance with the correct permissions
- Download and install the SQL Toolbelt installer on the client machine
See Getting started with SQL Change Automation projects in Visual Studio for more information.
Setting up SQL Change Automation for Continuous Integration and automated deployments
The processes for conducting Continuous Integration and automated deployments are similar.
- Install build and release agents and configure them with administrator access
- TeamCity is recommended for builds
- Octopus Deploy is recommended for releases
- Identify a SQL Server instance to be used by the build agent for validation purposes
- Ensure the build agent machine has access to this SQL Server instance
- Ensure the agent machines have PowerShell 3.0 (or higher) installed
- Identify an accessible NuGet feed to use
- Some Continuous Integeration tools will provide a NuGet feed for you
- Download and install the SQL Toolbelt installer on the agent machines
- If possible, install the SQL Change Automation add-on for your chosen Continuous Integration and automated deployment tools
- See Add-ons
See Getting started with the SQL Change Automation PowerShell components for more information.