SQL Clone
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in

Updating SSMS to 17.9.1

I went to download the SSMS v17.9.1 package the other day and saw this:

2018-11-27 12_48_59-Download SQL Server Management Studio (SSMS) _ Microsoft Docs

I remember some issues with a C++ redistributable with a SQL Server install (2016?) and decided to just check on this. I really wish that these articles and items were crosslinked, so I could check them easily.

I decided to write this post to note how to do a few things, maybe to help you, but mostly so that I’ll remember things later.

I don’t know if I need a reboot, but I’d rather not if I can avoid it, through I’m slightly concerned this stuff will force a reboot.

Checking C++ Redistributable

The first thing is to check the Visual C++ 2013 version. I found this KB article on the update with downloads. The file information is

Name: VCRedist_x86.exe

X64 location: %WinDir%\SysWow64

A search was slow, but found files. Lots of them. Apparently this is put down quite a bit by various software.

2018-11-27 12_53_25-VCRedist_x86.exe - Search Results in SanDisk900_a (C_)

Let’s go to the location noted. In there, I find I don’t have the file.

2018-11-27 12_53_40-SysWOW64

Not good, and I’m glad I checked. I’ll download the US English version from: http://download.microsoft.com/download/0/5/6/056dcda9-d667-4e27-8001-8a0c6971d6b1/vcredist_x86.exe

Once that’s done, I’ll install it.

2018-11-27 12_54_58-Microsoft Visual C   2013 Redistributable (x86) - 12.0.40660 Setup

This is 12.0.40660 and the minimum for SSMS is 12.0.40649.5, so I should be good here. The installation is slow, especially for a 6MB download.

It finishes, and I’m out of luck. I’ll reboot and continue this post.

2018-11-27 13_00_26-Microsoft Visual C   2013 Redistributable (x86) - 12.0.40660 Setup

Checking .NET

There’s a KB for this and it has various links, including viewing the registry or using code. I’ll use PoSh. The code they give is:

# PowerShell 5
Get-ChildItem 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\' | Get-ItemPropertyValue -Name Release | Foreach-Object { $_ -ge 394802 }

That last value is the minimum for .NET 4.6.2. If I remove the Foreach, I get a result of 461808, which is 4.7.2. I’m good here.

OS Updates

I’ll check Windows Updates, and its shows a couple items, none of which matter. Not sure what the SQL2016 item is. I know I have a couple old installations that are broken, so maybe that’s for one of those. Fortunately I have a couple working instances, should I need them.

2018-11-27 13_11_49-Settings

Upgrade SSMS

Let’s install.

2018-11-27 13_15_26-Microsoft SQL Server Management Studio

The process runs without issues, as I’d expect. For the most part SSMS 17.8 has been what I’ve run and it’s been fine. No real issues, and not sure this updates changes anything for me.

The list of issues is small, and I haven’t had any of these. Even the 17.9 list of issues isn’t anything that concerned me, so this was more updating for the sake of updating here.

This completed, and when I restart SSMS, I see what I expect. All my plugins and the tool connects to my instances.

2018-11-27 13_19_43-SQL Source Control - Microsoft SQL Server Management Studio

The Voice of the DBA

Steve Jones is the editor of SQLServerCentral.com and visits a wide variety of data related topics in his daily editorial. Steve has spent years working as a DBA and general purpose Windows administrator, primarily working with SQL Server since it was ported from Sybase in 1990. You can follow Steve on Twitter at twitter.com/way0utwest


Leave a comment on the original post [voiceofthedba.com, opens in a new window]

Loading comments...