Geeks With Blogs
David Atkinson SQL Compare
How the “migrations” approach makes database continuous integration possible
Testing a database upgrade script as part of a continuous integration process will only work if there is an easy way to automate the generation of the upgrade scripts. There are two common approaches to managing upgrade scripts. The first is to maintain a set of scripts as-you-go-along. Many SQL developers I’ve encountered will store these in a folder prefixed numerically to ensure they are ordered as they are intended to be run. Occasionally there is an accompanying document or a batch file that ......

Posted On Thursday, April 26, 2012 2:03 PM

Database continuous integration step by step
This post will describe how to set up basic database continuous integration using TeamCity to initiate the build process, SQL Source Control to put your database under source control, and the SQL Compare command line to keep a test database up to date. In my example I will be using Subversion as my source control repository. If you wish to follow my steps verbatim, please make sure you have TortoiseSVN, SQL Compare and SQL Source Control installed. Downloading and Installing TeamCity TeamCity (http://www.jetbrains.com/t... ......

Posted On Tuesday, April 24, 2012 7:18 PM

How to build a database from source control
If your organization has continuous integration in place, it will most likely contain a build step in which your latest application source code gets pulled from source control, compiled, and optionally subjected to a various tests. If you’re a Microsoft shop, chances are that your application works alongside an instance of SQL Server. SQL Source Control allows you to put your schema objects in source control by maintaining a set of per-object creation scripts representing in your existing version ......

Posted On Monday, April 16, 2012 6:18 PM

Copyright © David Atkinson | Powered by: GeeksWithBlogs.net