Default Azure Pipeline yaml as task

A quick note on Azure Pipelines. If you create a pipeline thru Azure DevOps on a .NET Core App the yaml file will use script rather than tasks.

This is also used in the Azure Pipelines Yaml Templates Github Repo.

It works yes but I would rather use tasks. If you are interested to use that as well, head on here:

https://github.com/johndelizo/Bunch-of-scripts/blob/master/Azure-Yaml/azure-pipeline-task-not-script.yml

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.

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>

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

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

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!

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

So after downloading we can now launch the installer.

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.

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.

So after installation, launch..

We now have SSMS back!