Posts Tagged with SQL Source Control

Six reasons to version control your database

For most application developers, it’s unthinkable to work without version control. The benefits of tracking and retaining an incremental history of code changes are long understood in the world of software development. No surprise then that the overwhelming majority of respondents in our State of Database DevOps survey confirmed they’re already using this practice... read more

How to version control a database using GitHub and SQL Source Control

Are you interested in version controlling your SQL Server database in GitHub? This article explains some simple steps to create a GitHub database repository and get your database code in there, using SQL Source Control. I assume you’re a SQL Server professional and don’t need a deep dive into how source control systems work,... read more

An introduction to SQL Source Control

In our series of blog posts about Version Control and the Database, we’ve explored the history of version control, why databases have some unique requirements, and why it’s important to include them in your VCS. In this concluding post, I focus on Redgate SQL Source Control and answer some fundamental questions about what it... read more

Versioning an existing database using SQL Source Control

A while ago, maintaining a reliable database change history was an ongoing problem within our development team. It seemed we were forever asking questions such as “Who made this change?”, “When was the stored procedure last edited?”, “When was this view created?”, and so on. Our initial approach was simply to store a list... read more

Teamwork is the key to developing SQL Source Control as well as using it

The long-awaited release of SQL Server Management Studio (SSMS) 2016 is approaching, bringing with it a more modern look and feel, more features, and more advantages for users. At Redgate, we’ve been working closely with Microsoft to make sure the latest version of SQL Source Control supports SSMS 2016 from launch day. SQL Source Control... read more

Source controlling your database permissions

The problem A common question we encounter when working with SQL Source Control is about database permissions. Different environments require different permissions, so should you just omit them entirely from Source Control? Or perhaps include only permissions for your production environment? Permissions are extremely important, so not source controlling them at all doesn’t seem... read more

The key to avoiding database version control problems

It’s a familiar story. Two developers are working on a database, they’re using version control, and there’s a problem. The bigger problem is, they don’t even know they have a problem. As far as they’re concerned, they’re doing everything right. They’ve been using version control, so they can deploy the database changes they’ve been... read more

Sometimes the tool just fits – using Redgate DLM and Octopus Deploy for data change control

From a business risk perspective, data change can be just as significant as code or schema change. Sometimes even more so; an incorrect static (or reference, or master) data change can drive your software’s behaviour more dangerously askew than pretty much any bug can. Imagine treating a retail customer for an investment fund as a corporate... read more

Source controlling database users

How should you source control database users? This topic came up a couple of times recently. Once at the inaugural Redgate database source control training day and once or twice at SQL Saturday Exeter when, somewhere in between the foot jenga, pirate hats, and explosive Phil Factor unmasking (if you believe it?), I found... read more