How to manage version controlled SQL Server database static data; from commit to usage, to deployment


As explained in this article Understanding SQL Server database static data and how it fits into Database lifecycle management including static data in SQL Server database source control is important for a successful CI/CD implementation.

Once you make a commitment to version controlling your static data, you’ll want to know how to get it into a repository, work with it once it has been committed and get it out.


We will look at managing SQL Server database static data as a three step process: initially getting it versioned in your source control repository, managing it with changes, updates etc and deploying it to a database.

Initially committing static data to a source control repository

The following articles will demonstrate how to initially commit static data to a repository:

Working with version controlled static data in the repository

Static data, although “static” by definition, does eventually change, just not as often as other data. Thus, updating and managing version controlled SQL database static data and tracking changes, is the next step, which is described in the following articles:

Deploying static data from a repository

Finally, more information on getting static data out of the repository and into a database, either for just getting the latest changes, or building a database for QA testing, staging or other purposes during a continuous integration process, is provided in the following article:


February 3, 2017