If you write code to SQL Server then you might be interested in this: at the end of 2017 I wrote a tSQLt tdd training course which has helped over 300 people learn both tSQLt and how to apply TDD practices to their SQL Server T-SQL development, you can join the course at https://courses.agilesql.club. The course is free if you are happy to wait 10 weeks to complete it, with 1 lesson being made available per week - if you are in more of a hurry or you would like to help support the project you can purchase the course which makes it instantly available to you.
If you already have a source code repository for your app code or other databases or you have another team that uses source control then just use theirs.
If you don’t then use whatever the members of your team have used most, they all basically do the same thing and having your database under source control is a million times better than not having it under source control.
There is an exception, if you use visual source safe and I know people do still use it then use something else, it hasn’t had a release in over 10 years and in my opinion is no longer fit for purpose, especially when you consider the other free options available to you.
October 9, 2015 - 15:52
I am currently going through
I am currently going through the process of assessing the benefits of difference SCM’s for databases.
As we are starting pretty much from scratch, we are looking to features such as branching, tagging and 3rd party support to inform our decision. Having used git previously, I’m very tempted to go for a cloud hosted git solution (such as bitbucket) as this removes the worst of the complexities whilst keeping the benefits ;)
My biggest challenge is working out the extent we will use some of the more advanced features and selling my colleagues on the benefits of git!