Dave Green

Stairway to Database Source Control

Stairway to Database Source Control Level 5: Working with Others (Distributed Repository)

This level starts with an overview of how versioning works in Git, a DVCS, and suggests a sensible database project versioning strategy. It then offers some simple, but illustrative, practical examples showing how to share database changes and deal gracefully with any conflicting changes.

2016-05-18

1,080 reads

Stairway to Database Source Control

Stairway to Database Source Control Level 4: Getting a Database into Source Control (Distributed Repository)

Now that we have our database under source control, we will want to share our work with other developers. If we are in a centralized source control system, our changes may be committed straight into the central repository.

When we are working in a distributed system, it means pulling down any changes from other developers, addressing any areas of conflict, and pushing our changes up to allow others to benefit from our work. This allows our changes to be synchronized with the changes other developers have made.

This level is principally about setting up a distributed source control system, namely Git, and how to commit database development changes to a local repository, before pushing them into a remote 'central' repository for sharing with other developers.

The next level will delve a little deeper into Git's versioning mechanisms, and show some examples of how to share database changes during development, and how to deal with conflicting changes.

2016-02-03

2,233 reads

Stairway to Database Source Control

Stairway to Database Source Control Level 3: Working With Others (Centralized Repository)

One of the main purposes of placing a database under source control, alongside the application code, is to allow team collaboration during development projects. The Version Control System (VCS) stores and manages all of the project files, maintaining an audit trail of what changed, and who made the change. Each team member can work on a file, or set of files, and submit their changes to the VCS to make them available to other team members. They can also inspect the VCS to discover recent changes made by other team members.

2015-03-04

3,913 reads

Blogs

SQLDay 2019 – day 3 (last)

By

SQLDay 2019 has come to an end. Three days with workshops, technical sessions, networking...

Back with a new focus

By

First let me say wow can’t believe that it has been almost 3 years...

Information Measurement with SQL Server Part 4.5: The Squared L2 Family of Distances

By

By Steve Bolton …………In the last two installments of this series of amateur self-tutorials...

Read the latest Blogs

Forums

Preventing Access

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Preventing Access

Creating Aliases for Docker Commands in Linux

By carlos10robles

Comments posted to this topic are about the item Creating Aliases for Docker Commands...

error Output File cleanup does not delete files script d'olla

By abdalah.mehdoini

Hello everyone, I use olla scripts in my backup and maintenance operations there is...

Visit the forum

Ask SSC

SQL Server Q&A from the SQLServerCentral community

Get answers