Deploying SQL Server 2016 Management Tools

TL;DR SSMS is now a separate 800MB+ download. https://msdn.microsoft.com/en-us/library/mt238290.aspx

Long story (Begin Rant):

As much as I can, I always deploy Windows features and products using either direct to command line or with a configuration XML or INI file. In this case, I am installing SQL Server.

image

On previous version of SQL Server you can use the INI file to indicate what features you are going to install. Syntax is FEATURES=<FEATURE><,><FEATURE>

image

And before you can add the SSMS feature by adding SSMS –or- ADV_SSMS for Management Tool Basic –or- Advanced, respectively.

There seems to be a change with SQL Server 2016 as adding the SSMS will throw an install error.

So I saw the Management Tools now  located in the installation tab and under the new stand-alone link. I remember that in order for me to add SSMS before, it is under the add features to an existing installation. But now it seems that SSMS has its own link. But be warned, it is an actual “HREF” to a webpage. https://go.microsoft.com/fwlink/?LinkId=531355

image

Yes. You guess it right, you have to download SSMS as a separate installer.

image

https://msdn.microsoft.com/en-us/library/mt238290.aspx

That link, Download SQL Server Management Studio (16.5.3): https://go.microsoft.com/fwlink/?LinkID=840946 is 898MB. Surprise!

image

Now using Philippine internet connection: See you after 3 hours or more.

image

So after downloading we can now launch the installer.

image

Next time, I will be using /Install /Quiet as my command line parameters based on the MSDN article here: https://msdn.microsoft.com/en-us/library/bb500441.aspx but for now, lets do a GUI install.

image

Wait for the setup to finish. This will not ask for your install location nor what tool to install – it will install everything on your C:\Program Files so be careful if you have SSD. Hope in the future, since this is a standalone product that we can choose which drive to use. But for now its just a straight forward install.

image

image

So after installation, launch..

image

We now have SSMS back!

image

Advertisements

Windows could not start SQL Server Error Code 100048

So SQL Server on my dev machine is not running. I think this machine did an update today and when I came back it was restarted.I don’t use SQL Server on my laptop not unless I am doing development outside of the office so my SQL Server Service is set to start manually.

Tried starting the SQL Server (MSSQLSERVER) service  manually using services.msc but there are errors: Windows could not start the SQL Server on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 100048.

image

So it says check event viewer (eventvwr) for the details:

image

Yeah, there are some errors! Checked one by one saying check the previous error so I did. Says TCP port 1433 is already in use. We all know that port 1433 is used by SQL Server. See: http://support.microsoft.com/kb/287932 

image

Lets terminate that process so that using 1433. Lets check using netstat.

Open a command prompt using Administrator (Run as Administrator) and type: netstat –a –n –o | findstr 1433

image

Take note of the process ID. It is the number at the right most column. Take note of it and terminate it. Use:

taskkill –pid <ID>

or

taskkill –pid 7372 as seen in my example.

Now after terminating / killing the process, switch back to the Services console and start SQL Server.

image

You should be able to log-in in SSMS 🙂

image

Okay now, back to work!