ContinuousIntegration

tsql2sday-300x300

T-SQL Tuesday #90 – You are doing “Continuous Integration” wrong!

It’s still Tuesday alright… In the USA anyway. (And by the USA I mean Hawaii.) This blog post is part of T-SQL Tuesday #90 – Shipping Database Changes, hosted by James Anderson. T-SQL Tuesday is an online blog party started by Adam Mechanic and you are invited to join in. A record of every previous T-SQL Tuesday is maintained by Steve Jones.…

buildLogSquare

ALM, databases, TFS build vNext (2015) and Redgate: A tutorial for my SQL in the City demo

I’m in Seattle chilling out around PASS Summit, meeting old SQL friends and duelling with jetlag. A couple of days ago I did a talk with Brian Randell MVP (b|t) at SQL in the City. The talk featured a demo of a CI process for SQL Server using Team Foundation Build vNext (TFS 2015) and Redgate’s SQL CI tool (part…

BambooLogo

Continuous Delivery for Oracle Databases, with Atlassian Bamboo and the Redgate DLM Automation Suite for Oracle (part 2)

Welcome to part 2 in this short series. In this post I’ll explain how to extend the Oracle DB continuous integration process I set up in part 1 by adding a release management process that deploys changes to staging or production databases at the click of a button. Objective for part 2 At the click of a button, at a…

BambooLogo

Continuous Delivery for Oracle Databases, with Atlassian Bamboo and the Redgate DLM Automation Suite for Oracle (part 1)

Welcome to part 1 in this short series, where I explain how to set up a continuous integration process for Oracle databases. In part 2 I’ll set up a release management process that allows a user to deploy changes to staging and live databases at the click of a button. Objective for part 1 Whenever a developer commits a change…

Jenkins

Database CI with Jenkins: A step by step tutorial

Edit: Originally written in Oct 2013, this post was updated in Nov 2016 due to software updates from Redgate. While Continuous Integration (CI) started with application code you should apply the same principles to databases. The point is that CI reduces your feedback loop such that changes that break the build are caught as soon as they are committed to source…