Upvotes: 2<=-=May 18 2016 9:50AM=-=>
We are working on getting source control integration lit up in SSMS. It got a bit complicated when we moved to the VS 2015 Isolated shell. We ran into some side-by-side issues and the way Visual Studio bundles the source control packages. We are working through that and I expect in one of the next couple monthly releases we will have it spelled out.
Cheers,<=-=May 23 2017 3:28PM=-=>
Since the last comment on this was over a year ago, is there any update?
This aligns with our vision for improved manageability, particularly for VLDBs. Will consider for future development.
Object Explorer doesn’t populate the entire tree in memory, unlike visual studio’s solution explorer. It wouldn’t know if database “MyDatabase” existed until you expanded the Databases node.
There are third party plugins that provide this type of functionality, I believe, by downloading a bunch of data in the background and exposing a search.
CMS (RegisteredServers) has been ported. It will be included in the next version of SMO and/or the next version of the SQL Powershell module.
An error occurred while saving the commentTristan W commented
This is a major hole in Azure features, especially since this is a downgrade from the features we have on-premise using VMWare.
1 voteTristan W shared this idea ·