Deploying an SQL Project DACPAC on Check-In
This post is a follow up to this post about a talk I gave at the Boston Code Camp.
One of the questions from the talk was “Can you automatically deploy SQL Database Project changes when the code is checked in?”.
I found a blog post by Jamie Thompson called How deploy a DACPAC on Check-In using MS Azure which explains how to check an SQL Database Project, build and deploy it. The article is from 2013 and mentions TFS Online, which is now Visual Studio Online. I assume the article should translate to using VSO and TFS or Git version control, if anyone has tried it please let me know.
The output of “building” an SQL Database Project is a file called a DACPAC. A DACPAC is defined on MSDN as:
A data-tier application (DAC) is a logical database management entity that defines all of the SQL Server objects - like tables, views, and instance objects, including logins – associated with a user’s database. A DAC is a self-contained unit of SQL Server database deployment that enables data-tier developers and database administrators to package SQL Server objects into a portable artifact called a DAC package, also known as a DACPAC.
Deborah Kurata mentions a few ways to deploy a DACPAC in her excellent pluralsight video Visual Studio Data Tools for Developers and on her blog in the post Multiple ways to deploy a DACPAC.
I hope you find the above info useful, post in the comments if you know of any other good resources for deploying SQL Database Project on Check-In.