Sql-server – Can’t find the client download for SSMS

If you want the shiny new 2016 monthly releases of Management Studio, which include a handy check for updates mechanism, negates the need for a full setup program and download (since it only retrieves the components you need), as well as a release cycle completely independent from SQL Server, go here (and you can read about it here and here).

If you use this new web installer, much of the below no longer applies. If you want to use previous versions (currently 2012 SP2 and 2014 SP1), they've made it easier to find and download (see this page), but much of the below will still apply.

Well, if you have a legal copy of SQL Server, you should be able to install Management Studio from that media wherever you need to manage SQL Server from.

That said, the Express version of Management Studio, since 2012 Service Pack 1, has been a fully functional product with absolutely no differences (except you can download it for free instead of finding your licensed media). I would recommend downloading the 2014 version, because why use an older version that will be out of support sooner? My philosophy is that SSMS should always be >= the highest engine version you need to manage.

Anyway, I found the link by searching - the hint to not jumping through hoops set up by Microsoft marketing or MSDN is to look for the page with download in the URL:

This brings me here, where I click Download:

Then pick either the 32-bit or 64-bit version, depending on your platform, and click Next:

And success. I even get handy tips for installation if I need them.

If you really, really, really want to use the 2012 version instead of the 2014 version, well first I'd be interested why, but the same process will work, just use this link instead. Note that the 2012 version is a 950 MB download vs. 684 MB for 2014.

Since a lot of people get confused on how to install JUST SSMS with this installer, here are some other things you'll want to follow once you launch the .exe. First it will open the installation center. You want Installation > New SQL Server stand-alone [blah blah]...

Clicking that link will launch a new wizard, and leave the installation center open. Leave it open (see the end of this post for why). On the new screen, you may have product updates offered, and you definitely want to select them if so (currently this should only happen for 2012 SP1 or 2014, since 2012 SP2 was not affected by Security Bulletin MS14-044).

Next, and this is where most people get confused, you want to choose Perform a new installation - even though you are not trying to install an actual instance of the SQL Server database engine.

Then, you want to select both Management Tools options, basic and complete. From here you should be ok on your own.

Regarding the installation center window above, you need to leave the "SQL Server Installation Center" window open during setup, or it will fail with an error like this (the actual folder name is some random GUID-based thing):

SQL Server Setup has encountered the following error: Could not find file 'c:\1d3c284ce0e72239e2f4e51c802d\MediaInfo.xml'

I filed a Connect item about it, but so far it remains active.

I haven't played with themes, but you can set per-connection properties, including the color of the connection info bar at the bottom of the query tab. And these settings are saved.

If you have a query tab open, go to "Change Connection" (either the button in the button bar, or via the Query menu, top item should be Connection >, and when it pops up the "Connect to a Database Engine" dialog, click on the Options >> button. Go to the Connection Properties tab and the bottom option is Use custom color:. Check the check-box for it and click on the Select... button on the right.

Just use different colors for the different servers/environments.

Technically speaking, there is a means of programmatically interacting with SSMS: write a plug-in / extension. I will list some resources below that deal with this topic. I have not tried it yet myself, but it seems as though it might be a lot of effort for a one-time config update. On the other hand, if SSMS will not record the setting for 100, let alone 400, separate connections (not sure what the limit is), then maybe this would be worth the effort.

• The art and science of creating SSMS 2012 add-ins – Part 1 – Laying the Foundation (this is a 3 part series with links to parts 2 and 3 towards the bottom; towards the bottom of part 3 are 6 links to other resources, the first of which I will duplicate as the next item)
• How to write own add-in for SSMS 2012 (Final release version)
• Automation and Extensibility Reference (for Visual Studio, but it should be very similar with SSMS, at least as of SQL Server 2012)