Microsoft has separated installation of SSMS from SQL Server Engine Installation since SQL Server 2016 and if you see the SQL server setup page it has an option to Install SSMS
I wanted to try out the new and shiny features of SQL Server 2017 when it was released last fall, so I opted to install it on one of my virtual machines.
I’ve had a lot of problems, but some of them are strange and can happen if certain default values are left on. Either they were enabled later for some reason and not restored, or they were skipped during the post-config check after SQL was installed.
In most cases, adding any service, such as SSAS, SSRS, or a database engine, to an existing installation is not possible, and such additions require a named Instance installation.
This problem first appeared in 2013 on a SQL server 2008 R2 that was running on Windows Server 2008 R2.
This is the first of a multi-part article on how to run a SQL test lab on a laptop. To begin, we must first enable Windows’ hyper-V feature. Hyper-V is included with Windows 10, however it is turned off by default. We can utilize the GUI, PowerShell, or the command line to enable HyperV.
With the Cloud at our disposal and a myriad of virtual Labs available, setting up a lab in this day and age is like reinventing the wheel. (MSDN membership, AWS free credits, additional offers) Both Azure and AWS provide free credits up to the tune of $150/mo or $100/mo to test their products, but sometimes your desire to build from the ground up takes over and you plunge in without a second thought.