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,441 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,733 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,230 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,095 reads

Blogs

THAT Conference 2024 in Wisconsin Dells

By

I’m headed back to Wisconsin Dells next week for THAT! Conference 2024. This is...

7 Best Online Advanced SQL Training Courses to Learn in 2024

By

The world runs on data, and SQL is the key to unlocking its secrets....

Calling a REST Endpoint from Azure SQL DB

By

External REST endpoint invocation in Azure SQL DB went GA in August 2023. Whereas...

Read the latest Blogs

Forums

Issues adding and updating a column

By richardmgreen1

Hi all   I'm hoping someone will able to say "you're an idiot because....."...

Deadlocks with UPDATE statements using serializable transaction isolation level

By zoggling

We are seeing frequent deadlocks occurring due to a particular stored procedure that is...

Use Polybase with ODBC to create external table

By blom0344

I'm trying to use the installed Polybase service on an  SQL 2019 server to...

Visit the forum

Question of the Day

The Last DBCC Date

How can I easily get the last DBCC CheckDB date from T-SQL in SQL Server 2022?

See possible answers