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.

Blogs

What Does It Mean to Make Data AI-Ready?

By

Making Data AI-Ready, Part 1 (This is the first article in a three-part series...

Using the Data API Builder–VS Live San Diego Resources

By

Thanks for attending my sessions. Resources below: Slides: Using Data API Builder GitHub repo: ...

Running a Local LLM On Your Laptop Resources

By

Thanks to everyone that attended my sessions at VS Live San Diego yesterday. It...

Read the latest Blogs

Forums

Hyperscale Replicas II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Hyperscale Replicas II

Practical Reporting Queries with CROSS APPLY (Part 3)

By Imran2629

Comments posted to this topic are about the item Practical Reporting Queries with CROSS...

Your Favorite Quotes

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Your Favorite Quotes

Visit the forum

Question of the Day

Hyperscale Replicas II

How many Azure SQL DB Hyperscale HA replicas can be configured as of Sept 2026?

See possible answers