SQL Source Control - Code Aperture

Code Aperture

Sign in Subscribe

SQL Source Control

A collection of 7 posts

Redgate SQL Toolbelt over Microsoft SSDT: My Biased Opinion

Back in the article How Redgate Helped Define our Process [https://www.codeaperture.io/2016/09/13/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

Static Data with Multiple Database Tenants

The loan origination system my team and I are responsible for have 20 tables marked as static data in Redgate's SQL Source Control. One example of static data is a tile type. The loan origination system has a dashboard made up of multiple tiles. There are six different

Using SQL Source Control to Filter Out Unwanted Items

Using SQL Source Control to Filter Out Unwanted Items

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

Branching with Redgate SQL Source Control

Branching with Redgate SQL Source Control

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

How Redgate Helped Define Our Process

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

Using Gitflow and Redgate DLM Automation for Continuous Delivery

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

Using Static Data in Red Gate's SQL Source Control

One area where Red Gate's SQL Source Control needs a little more information is the Static Data Feature. It is very easy to run into problems with it. Don't get me wrong, Red Gate's SQL Source Control is a fantastic tool. Their goal is