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.

You rated this post out of 5. Change rating

2016-05-18

1,450 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.

You rated this post out of 5. Change rating

2016-02-03

2,752 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.

You rated this post out of 5. Change rating

2015-03-04

4,240 reads

Stairway to Database Source Control

Stairway to Database Source Control Level 2: Getting a Database into Source Control

In this level, we're going to continue the philosophy of learning by example, and get a database into our SVN repository. We will also consider our overall approach to source control for databases, and the manner in which our team will develop these databases, concurrently.

You rated this post out of 5. Change rating

2014-06-11

7,122 reads

Blogs

Mastering the ORDER BY Clause in SQL Window Functions

By

This article provides a comprehensive overview of the ORDER BY clause within SQL window...

SQL Data Pipelines: The Ultimate Guide to Streamlining Your Data Flow

By

Want to build a data analytics foundation that transforms raw data into valuable business...

Using SQL Compare in Read-Only Databases

By

Recently a customer asked if SQL Compare and SQL Data Compare can be used...

Read the latest Blogs

Forums

Logging from application to SQL server 2014..Using ODBC driver 18 for SQL SERVER

By SQL_Surfer

I'm using the below connection string using providing UserID and password on their respective...

Knowing Your Total Reward

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Knowing Your Total Reward

No Renames

By Steve Jones - SSC Editor

Comments posted to this topic are about the item No Renames

Visit the forum

Question of the Day

No Renames

Which of these can't be renamed with sp_rename?

See possible answers