visual studio 2017 sql server database project

The Pre-Deployment and Post-Deployment folders each contain a default script that SCA creates. Each is numbered and named by SCA, but they can be renamed if needed. The team can control the order in which these run, but by default they will run in the ordering that they appear. The Migrations folder will contain our set of database migration scripts, each one describing a distinct change to the database. If you are adding this project to an existing solution, it will appear as part of that solution, alongside any other projects that already exist. Once I click OK, SCA will create the project for me and set up a simple solution with several folders, which you can see in solution explorer. I also selected the option to create a directory for the solution and create a new Git repository in this location. I called mine simply “ SQLChangeAutomation” and put in my local user Repos folder. Give the project a name and choose a location for it. You can see this in the screenshot below, with the SQL Change Automation project type selected. You’ll find the SQL Change Automation Project in the Other Languages group, beneath the SQL Server item. You do have the option to search for online templates as well. Most of these are grouped by languages, though the exact list will depend on which templates you have installed. You’ll see the usual list of Visual Studio project templates. To begin database development, startup Visual Studio and use the File – New – Project menu to create a new project. SCA is a plug-in for Visual Studio that creates a new SQL Change Automation project type.

This will be a Brownfield development project, to upgrade an existing database, so you’ll need a SQL Server instance and database with existing objects (creation script for my sample database is here) Creating a Project SQL Server Management Studio is optional as the SQL Server Object Explorer in Visual Studio can be used instead.

Visual Studio installed (VS 2017 used here) with the SQL Change Automation pluginĪ version control system is highly recommended, and this article will use Git, but any version control system compatible with Visual Studio will work.

There are a couple of requirements to follow along with this tutorial:

In this article, the first in a short series, I’ll show you how a team can use SQL Change Automation in Visual Studio to do development work on an existing database. SQL Change Automation (SCA) is a tool designed to help you automate and optimize the way you develop, build, test, and release SQL Server databases, including integration with source control.

Visual studio 2017 sql server database project