ReadyRoll is a Visual Studio project system that makes it easy to create and manage migration scripts for SQL Server databases. What I like about the product is that it is heavily focused on making sure it works well in a continuous delivery environment, unlike certain other SQL deployment tools, and it uses change scripts.
I wrote previously about how to deploy a SQL database using Octopus Deploy and an open source tool called DbUp, but ReadyRoll 1.3.3 makes this much easier:
Today I am excited to announce Octopus support in ReadyRoll SQL Projects! If you’re not familiar with it, Octopus is the automated release management tool for .NET that everyone’s talking about.
In a sense Octopus and ReadyRoll are spiritual cousins in that they both support the build once, deploy many times tenet of Continuous Delivery: the practice of ensuring that the same build artifacts (binaries, scripts, etc) used in Dev testing are carried all the way through to Production.
If you are using Octopus Deploy and need to deploy SQL Server database changes, I’d definitely recommend giving ReadyRoll a try!
Tags:
Related posts
Changes to the TFS/VSTS Extension
If you're one of the many Visual Studio Team Services (VSTS) or Team Foundation Server (TFS) users who make use of the Octopus Deploy Build and Release Tasks extension, you might have noticed a couple of changes.
Octopus.Client goes Open Source
A few weeks ago we separated Octopus.Client from our main code base and quietly sent it on it's way with an Open Source license.
RFC - Octopus Reactions - Integration toolkit
Recently at Octopus HQ we've been looking at how to better integrate with other tools in the DevOps ecosystem.