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

Azure SQL offerings

By

There are three Azure SQL products with so many different deployment options, service tiers,...

T-SQL Tuesday #183 Roundup

By

I hosted this month’s T-SQL Tuesday party with my invitation asking about tracking permissions....

A Little Brainstorming with an AI

By

I was asked to do some a little thinking and brainstorming recently. Rather than...

Read the latest Blogs

Forums

MEMORYBROKER_FOR_RESERVE experience

By tony28

Hi, Does anyone have experience with MEMORYBROKER_FOR_RESERVE ? when suddenly there is somehow constantly...

Moving Database Files

By Ahr Aitch

I just learned that my database was created on my C:\ drive in the...

Migrate MSSQL to MYSQL - Different Servers

By cajun_sql

I am needing to migrate a MSSQL db to MySQL, on a different server...

Visit the forum

Question of the Day

Mixed Backups

I have a complex database with a few filegroups and files. Can I run a backup command like this? (assume file/filegroup names are valid).

BACKUP DATABASE [complex]
    FILE = N'thirdone'
 ,  FILE = N'thirdtwo'
 ,  FILEGROUP = N'second' 
 TO  DISK = N'C:\Program Files\Microsoft SQL Server\MSSQL16.SQL2022\MSSQL\Backup\complex.bak' 
 WITH NOFORMAT, NOINIT,  NAME = N'complex-Full Database Backup', SKIP, NOREWIND, NOUNLOAD,  STATS = 10
GO

See possible answers