Geeks With Blogs
David Atkinson SQL Server
List of resources for database continuous integration
Because there is so little information on database continuous integration in the wild, I’ve taken it upon myself to aggregate as much as possible and post the links to this blog. Because it’s my area of expertise, this will focus on SQL Server and Red Gate tooling, although I am keen to include any quality articles that discuss the topic in general terms. Please let me know if you find a resource that I haven’t listed! General database Continuous Integration · What is Database Continuous Integration? ......

Posted On Wednesday, May 9, 2012 12:10 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

Ever wondered what the Object Explorer Details window is for?
Typically, when I install SQL Server Management Studio and run it for the first time, the first thing I do is to close the Object Explorer Details window. After all, it doesn’t seem to serve a useful purpose, duplicating information that already exists in the Object Explorer. However, I have discovered that it has one important redeeming capability, the ability to allow multi-selection by holding the ctrl or shift key depressed during the selection. Why is this useful? If I want to rename an object, ......

Posted On Monday, April 23, 2012 5:06 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

Installing NAnt to drive database continuous integration
Before we start thinking about database continuous integration, described in an earlier blog post, we need to pick a build tool in which we define the commands for our build process. NAnt is a .NET version of Ant, a tool to drive build processes. Like MSBuild, Microsoft’s equivalent, NAnt build scripts can be driven by continuous automation tools, such as TeamCity, CruiseControl, Bamboo and many others. Yes, it would be possible to drive your scripts with DOS batch files or PowerShell, but NAnt specializes ......

Posted On Monday, April 16, 2012 2:08 PM

Using a SQL Prompt snippet with template parameters
As part of my product management role I regularly attend trade shows and man the Red Gate booth in the vendor exhibition hall. Amongst other things this involves giving product demos to customers. Our latest demo involves SQL Source Control and SQL Test in a continuous integration environment. In order to demonstrate quite how easy it is to set up our tools from scratch we start the demo by creating an entirely new database to link to source control, using an individual database name for each conference ......

Posted On Thursday, April 12, 2012 9:46 AM

What is Database Continuous Integration?
Although not everyone is practicing continuous integration, many have at least heard of the concept. A recent poll on www.simple-talk.com indicates that 40% of respondents are employing the technique. It is widely accepted that the earlier issues are identified in the development process, the lower the cost to the development process. The worst case scenario, of course, is for the bug to be found by the customer following the product release. A number of Agile development best practices have evolved ......

Posted On Thursday, April 12, 2012 6:38 AM

Copyright © David Atkinson | Powered by: GeeksWithBlogs.net