Changes in Daily Build and SQL Server

I'm going to try to automate the daily build, which will include database changes, code generation, and of course build, commit and late deployment. At the moment, each developer in the team includes their structure and data changes for the database in two files, respectively, for example. 6.029_Brady_Data.sql. Each structure and data file contains all changes for the version, but all changes are repeated, i.e. with EXISTS checks and so on, so they can be run every day if needed.

What can I do to give more order to this process, which is currently basically merging all the structure change files, rerunning them until all dependencies are resolved, and then repeating with the data change files.

0


source to share


1 answer


Create a database project using the Visual Studio version of the database, put it in the original control, and let the developers test their code. I did this and it works well with daily builds and offers a lot of support for structuring your database code. See this blog post for features



http://www.vitalygorn.com/blog/post/2008/01/Handling-Database-easily-with-Visual-Studio-2008.aspx

+1


source







All Articles