Support source control integration in Management Studio 2016
Currently, source control integration in Management Studio appears to be unavailable (though the official notes say it's only deprecated - https://msdn.microsoft.com/en-us/library/ms143729.aspx#Anchor_1).
I have read on some forums that this has been discontinued effective SSMS 2016 but nothing official.
The alternative sometimes suggested is SSDT. SSDT is great for taking the entire database schema in source control. However, having ad-hoc scripts in source control so they can be shared with team members is an entirely different scenario and one that most likely uses SSMS and not VS.
Upvotes: 94<=-=Sep 5 2016 6:18AM=-=>
Teams working with SSMS solutions for ad-hoc T-SQL code also require the ability to integrate those solutions with TFS<=-=Nov 4 2016 8:54AM=-=>
This issue needs to be addressed. Integration with some sort of source control solution – including Visual Studio Team Services and Git – is something that should be available in every Microsoft Developer Tool.<=-=Nov 4 2016 11:47PM=-=>
I agree with both previous posts, The SDLC requirements of many of the consulting gigs I have worked require that my SQL Dev work be included in existing Source Control repositories. I am primarily working with SSMS solutions and this has always been a pain point for me. Now that some companies are using the GitHub repository it feels even harder to maintain the SQL code without a nice Msft plugin to help.
Even with the previously available MSSCCI Provider which allowed integration with TFS from SSMS, sometimes the SSMS solution needed to be included in Visual Studio and made a part of a Visual Studio solution … of course the file extensions were different and the formatting was different so the SSMS solution could not be recognized in Visual Studio … Aaarrgh
If you ever do decide to bring this back also please consider how to ease the pain of including a SSMS solution/project into a Visual Studio project (but not have the requirement that it be considered a database project type).<=-=Dec 13 2016 2:11PM=-=>
I like working on Visual Studio but I also like working on SQL Server Management Studio. I’m using the workaround but having it be an officially supported option would make it easier for us to keep using TFS for all our source control needs, including SQL.<=-=Jan 11 2017 2:28PM=-=>
I agree. There are two types of DBA’s in the world. Those who use source control, and those who will use source control. Lets have a way to connect to Source Control please! Even if just for scripts, it is so meaningful to have the history behind file edits.<=-=Nov 15 2017 4:33AM=-=>
Since, SQL Server Management Studio (SSMS) is uses the Visual Studio IDE, it would make sense to ship the source control integration. This will allow both developers and DBAs to store SQL scripts in the same source control system that their development team is using to save their source code for years. This shouldn’t require any 3rd party software or require the SSMS user to rely on command line tools to store scripts in source control.<=-=Nov 15 2017 5:21AM=-=>
This needs to support git, not just TFS. Ideally, it uses a straightforward plugin model so that more providers can be added by third parties.<=-=Nov 15 2017 11:23AM=-=>
I am going to venture a guess and say that the answer will be to use “SQL Server Operations Studio”