The time had finally come. It was time to run the Redgate automated database deployment process in production for the first time. All we had to do was click the deploy button in Octopus Deploy, and we would be on our way. The button was pressed, and we were on
Tag: Red Gate
The tooling necessary to incorporate DevOps practices is already out there. There are many different flavors of build tools, Jenkins, TeamCity, VSTS, AppVeyor, and Bamboo. Release management is covered by Octopus Deploy, Release Management, and Bamboo. And finally, database automation tooling provided by Redgate SQL Toolbelt and Microsoft SSDT. The
Back in the article How Redgate Helped Define our Process, there was this small blurb about SSDT:
Microsoft SSDT Tooling Considered - the increased cost of licenses forced us to take a hard look at Microsoft's SSDT tooling. Could it do what Redgate did? Could we build additional functionality around
Everything written on this site is how to get a database change automatically pushed up through the environments. But that was for the entire database. There are some parts of the database where they shouldn't be put under source control or shouldn't be promoted. Now you are probably thinking, "
A couple of years ago my team and I decided to change the name of a column in a loan origination system. 99% of the time this was no big deal. However, this was the primary key identity column used to uniquely identify a loan in the application. Renaming a
Rolling back a database deployment is one the most complicated topics with Automated Database Deployments. The code is rather easy to rollback, just deploy the previous version of the code package and call it good. It is just as easy to rollback database schema changes using Redgate's Database Lifecycle Management
Without the help of Redgate, Farm Credit Services of America's automated database deployment process would not be where it is today. I'm not just talking about their tooling. Their employees have been an invaluable resource. In September 2014 Redgate sent a pair of employees, Alex Yates, a pre-sales engineer and
One of the key reasons to use Redgate's Tooling is to deliver value faster to the business. In order to do that, it is important to have a branching policy in place.
This is only possible with a local database and Redgate's tools. Prior to implementing their tools, all developers
Redgate has built a fantastic Database Lifecycle Management (DLM) suite to help with automated database deployments. Their tools cover 95% of the scenarios most people will encounter day in and day out. But...it cannot cover 100% of the scenarios. The other 5% of the scenarios are what this post
Red Gate's DLM Automation Suite is the second half of the automated database deployments process. It takes the scripts that were created by SQL Source Control, builds a package, and then deploys that package to the various database environments (test, staging, production, etc.). Red Gate has built the tooling so