Bring Back TFS and Git in SSMS
According to this post: https://blogs.technet.microsoft.com/dataplatforminsider/2016/11/21/source-control-in-sql-server-management-studio-ssms/ these features were removed "because they didn't fit in the overall experience" for SSMS. This seems like an incredibly short-sighted decision for your user base. Many SQL developers use SSMS specifically because it is lightweight and does not require the massive baggage and learning curve of the full VS. That doesn't mean we don't need source control or task tracking in our process. Removing functionality that integrates two Microsoft products seems like a massive step backward. The suggestion to "work around" this poor decision by manually editing a definition file comes across as particularly condescending, given SSMS's "intended" use as a lightweight tool. Our team can not adopt a standard that involves "hacking" configuration files.
Microsoft, please educate your users by pointing out relative benefits between SSMS and VS and their use of source control. Please do NOT educate your users by destroying their workflow (SSMS/TFS). This is not how you win hearts and minds.
Carlos F Vargas commented
Esta es una publicación antigua, sin embargo, ahora con el lanzamiento del SSMS 18, es aún más necesaria.
Con SSMS 17 existía la solución "ssms.pkgundef". Esto ya no funciona con SSMS 18. ¡Permítase
conectarse al servidor Azure DevOps desde SSMS 18!
Jimmy Rüedi commented
It's absolutely essential for us to have source control for our SQL code since we are programming every stored procedure using SSMS.
We manage our stored procedures, views, functions and so on in TFS since it's intuitive and flexible.
Adjusting the ssms.pkgundef after each installation was absolutely tedious.
Michael Mertens commented
This is an old post however now with SSMS 18 being released it is even more necessary.
WIth SSMS 17 there was the "ssms.pkgundef" workaround. This is not working any more with SSMS 18.
Please allow to connect to Azure DevOps Server from SSMS 18!