Source Control for VMs

Question

We are looking to implement some kind of Source Control on our VM(Virtual Machine) side of the farm. We have implemented CI/CD on the Microsoft Azure side...now we are looking to implement some kind of Source Control on our VM side for SQL Server Stored Procedures, SSIS Packages .dtsx files, SSRS .rdl files.

I think we all agree at our site that TFS is a bit klunky and hard to work with.

So just a General Question as to what kinds of Source Control you all use...be it 3rd party...something home grown....etc..

Just looking for some ideas to maybe start an analysis document which will most likely end up in Managements hands as a proposal for SQL Server Source Control for our shop.

Any and all replies are Welcome and Thanks in advance for your review and replies.

Answer 1

VS natively supports GIT and GITHUB. If you do not like TFS, I would suggest using one of those.

https://learn.microsoft.com/en-us/visualstudio/version-control/git-visual-studio-source-control?view=vs-2019

Answer 2

Do you use any source control for the your client code? You should have your database and client code in the same repository, since you need to track them together. (And I don't understand what the VM has do it with it. Unless it is the VM configuration itself, you want to track.)

As Tom says, if you don't like TFS, Git is the obvious alternative. Then again, if you find TFS klunky, you may find GIt klunkier. There is certainly a learning curve. At the site where I am we switched to Git from TFS at the beginning of the year. Admittedly, I still have a lot to learn, but in some regards Git feels more primitive to me.

As Tom mentions, Visual Studio has support for Git, and maybe it has improved in VS2019. I only have VS2017 on my machine, and the Git support there is of little use, and I rather work from the command line directly.

Answer 3

Hi @Bobby P ,

Did you check the replies from Tom and Erland? If the response helped, do "Accept Answer". If it is not help, please let us know. By doing so, it will benefit all community members who are having this similar issue. Your contribution is highly appreciated.

I asked help from VS support team member, for Source Control issue, suggest customer reporting issues follow this link.