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.
Schlosser, Ken R commented
To make matters even worse, you can't script out objects in SSMS 17 when you are connected to a SQL2019 database. So using the older version of SSMS so you can use source control won't work going forward. Please get TFS/GIT enabled in SSMS 18!!
Like the others, source control is even more important in SSMS 18+
It's November 18, 2019, and the SSMS dev team at Microsoft have yet to enable TFS and GIT in SSMS 18 (currently 18.4). Please put this on the front burner. SQL 2019 just went RTM on Nov 3rd, and I have authority to upgrade, once SSMS supports source control by way of TFS or GIT.
Angela Kim commented
Ditto on all of the previous comments.
When the push is even greater to move to DevOps and to automate deployments, why would Microsoft remove an integration with source control.
This capability is necessary from SSMS, our db developers do not need the power of VS.
I echo the sentiments. It is astounding that Microsoft would tell its customers that SSMS can no be used for database development. That is exactly the message, since no one in their right mind would think of publishing a dev tool without source control integration.
I use and love the VS db project. But it is too heavyweight to be used everywhere, and SSMS still has traction.
Microsoft, do better!
Narayan Gupta commented
Please include Teams Explorer in SSMS 18 and above. I am reverting back to SSMS v17.x just because this feature is not available / can't be made available as it was the case earlier with ssms.pkgundef. Thanks very much
Russell Shilling commented
I used the TFS integration for several SSMS projects. It worked well, and I am sad that this was removed.
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!