SQL Studio Management Studio 2017

At first glance it might appear SSMS 2017 no longer supports third party source controls only because the Tools, Options menu no longer displays the Source Control section.

However, it turns out it is quite easy to tweak the SSMS 2017 configuration to restore those missing Source Control configuration options as described below.

Enabling Source Control for SSMS

The test described below was done using the SSMS v17.4 release:

SSMS 2017 About

Step 1. With SSMS not running, open up a command prompt in administrator mode and make a backup copy of the SSMS configuration file shown below, copying it to a safe location just in case:

C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\ManagementStudio\ssms.pkgundef

Step 2. From that command prompt edit the SSMS configuration file using notepad.exe; located the Visual SourceSafe entries and remove the three entires usign the // *** line comments as indicated in the text below:

    // TFS SCC Configuration entries.  The TFS entries block Team Explorer from loading.
    // Microsoft.VisualStudio.TeamFoundation.VersionControl.HatPackage
    // Microsoft.VisualStudio.TeamFoundation.Lab
    // GitHub Package
    // Team Foundation Server Provider Package
    // Microsoft.VisualStudio.TeamFoundation.WorkItemTracking.WitPcwPackage
    // Microsoft.VisualStudio.TeamFoundation.Build.BuildPackage
    // Microsoft.VisualStudio.TeamFoundation.WorkItemTracking
    // Microsoft.VisualStudio.TeamFoundation
    // Microsoft.TeamFoundation.Git.Provider.SccProviderPackage
    // Microsoft.VisualStudio.TeamFoundation.VersionControl.SccPcwPluginPackage
    // Microsoft.VisualStudio.TeamFoundation.VersionControl.HatPackage
    // Visual SourceSafe Provider Package
    // *** [$RootKey$\Packages\{AA8EB8CD-7A51-11D0-92C3-00A0C9138C45}]  <===== Comment out this line ****
    // Visual SourceSafe Provider Stub Package
    // *** [$RootKey$\Packages\{53544C4D-B03D-4209-A7D0-D9DD13A4019B}]  <===== Comment out this line ****
    // Microsoft.VisualStudio.TeamFoundation.Initialization.InitializationPackage
    // Team Foundation Server Provider Stub Package
    // Microsoft.VisualStudio.Services.SccDisplayInformationPackage
    // Microsoft.VisualStudio.TeamFoundation.Lab.LabPcwPluginPackage
    // *** [$RootKey$\ToolsOptionsPages\Source Control]  <===== Comment out this line ****
    // TFS SCC Configuration entries.

Step 3. Save the file changes, start SSMS 2017 and now the Source Control section is once again accessible by using the Tools, Options menu:

SSMS 2017 Options

IMPORTANT: If that Source Control option is missing it means the MS-SCCI source control components are not installed.

To get these missing components installed will require the installation of the Visual Studio 2015 IDE as that installer will add in these components.

Alternatively the Visual Studio 2015 Community Editon can also be used. A web search will locate that free download.

Step 4. To make sure all the componets mentioned earlier are in fact installed, select Source Control section shown below:

SSMS 2017 Options

If that panel does not show correctly it means the Visual Studio 2015 components are not installed.

Step 5. With those changes made just create a SSMS project and start adding the items to source control:

SSMS 2017 Options
Latest Version: Agent SVN 2.73
Released: 14 th June 2022