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,283 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,421 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

4,102 reads

Blogs

Database DevOps Deployment to Azure–Webinar

By

You can register now, but on Dec 3, I have a webinar with Microsoft...

[PowerShell Newbie] Using Start-Transcript

By

This week we are going to launch a blog series geared towards folks that...

My Experience on Geeks on Screen with Coffee

By

Last week on appeared on Geeks on Screen with Coffee which broadcast on YouTube...

Read the latest Blogs

Forums

SQL Server Collations

By PearlJammer1

So can anybody tell me if they have experienced issues when running a SQL...

Points of consedering during "Transaction Processing"

By gaurav

Hello Everyone, Here I need suggestions while I am trying to do some transaction...

when use dbachecks, it has error: unable to find type [Pester.outputtypes]

By huishi.ca

hi there: When I type invoke-dbcCheck, it pops up error below: Unable to find...

Visit the forum

Ask SSC

SQL Server Q&A from the SQLServerCentral community

Get answers