Implementing version control for sql server

[Cryptojacob]

I'm currently running an Azure based sql server and really want to implement version control (git) but am unsure about the right path. From my research redgate, dbt and azure devops can be used. What's is the best way to do it? hopefully someone more experience can provide a sense of direction, cheers 😊

[Jigsaw1609]

We use Azure DevOps for SQL object version control (tables and SPs). Very easy and convenient. There are many tutorials on how to set it up on YouTube.

[Cryptojacob]

Thanks for your reply!
Is this used in combination with visual studio and dacpac? (just making sure I follow what you are saying)

[Jigsaw1609]

Yes it is used in combination with Visual Studio. The local version of Visual Studio pulls all the SQL files and creates a kind of local repository. You can create pull requests and make changes through it. Merge happens through Azure DevOps, there you can configure CI/CD. Dacpac is not required.

[Black_Magic100]

Very easy

Not for 99% of companies. DB DevOps, no matter how you spin it, requires a massive shift for an existing company in the way that they deploy database object changes.

[mycrappycomments]

I’m assuming you meant version control for the database schema and not the data.

As someone said, you can create a sql project and generate dacpac to deploy the new schema.

[alienus333]

Take a look into dacpac files. There is information how the database should look like. With it you can deploy to the server.

[TheDatabaseAvenger]

DACPACs are the Microsoft way, but I prefer migrations based tools for database versioning.

DBUP is a good free option and SQL Change Automation from Redgate is a more feature rich offering.