SQLServerCentral Article

A Version Control Strategy for Branch-based Database Development

The migration to a different VCS should not be underestimated, as there is a lot more involved than just switching tools, and that’s what Tonie Huizer covers in this article.
First, the team needed to migrate the monolithic repos over to Git, second the team needed to make sure we had a branching strategy and workflow in place.
It involved a big process change for the team as well, but this switch is mandatory to make full use of branch-based database development.

SQLServerCentral Editorial

Fear of "What If"

Fear and aging. Two of the things that most human beings have in common is that we are scared and getting older. Most of us we fear getting older, but that is a very different conversation altogether. I want to talk about the fear of what if. Today I have two things I am keenly […]

Blogs

Getting the SQL Server MCP Server Running

By

If you’ve wanted a SQL Server MCP server for your databases, it’s available. The...

Introducing azsql-migration-test: Test and Validate Azure SQL Database Migrations

By

Introducing azsql-migration-test, a small open-source CLI that validates your Azure SQL Database migrations against...

Rambling about Data on Wheels – origins, branding, expansion

By

I have been asked many times about how the name “Data on Wheels” came...

Read the latest Blogs

Forums

Make It Routine

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Make It Routine

DBCC CHECKDB Limits III

By Steve Jones - SSC Editor

Comments posted to this topic are about the item DBCC CHECKDB Limits III

CROSS APPLY Fundamentals: Part 1

By Imran2629

Comments posted to this topic are about the item CROSS APPLY Fundamentals: Part 1

Visit the forum

Question of the Day

DBCC CHECKDB Limits III

On SQL Server 2025, does DBCC CHECKDB support Memory-Optimized tables?

See possible answers