I am an avid fan of Pinal Dave’s blog, it has been one of my go to blogs throughout my career as a SQL DBA. He has covered almost everything in the realm of SQL Server.
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
With new version of SQL server i.e. 2017 out last fall, I too wanted to try the new and shiny features so I decided to install it on one of my VM’s
I have faced numerous issues , but some are strange and may occur if certain default values are left enabled. Either they were skipped during post config check after SQL was installed or were enabled later for some issue and weren’t reverted.
In normal circumstances addition of any service SSAS ,SSRS or DB engine is not allowed on existing installation and addition of these would need a named Instance installation.
This issue occurred somewhere in 2013 on a SQL server 2008 R2 hosted on Windows server 2008 R2.
This is first post in the multi post series for running a SQL test lab on laptop. To begin we need to enable hyper-V feature in windows. Hyper-V is shipped along with windows 10 but is not enabled by default. To enable HyperV we can use GUI, PowerShell or cmd line.
Setting a Lab in this day and age is like re-inventing the wheel, with Cloud at our disposal and plethora of virtual Labs available. Both Azure and AWS offers free credits up to tune of $150/mo or $100/mo to test their products, (MSDN subscription, AWS free credits , other offers) but sometimes your want of building from ground up takes control and you jump in without giving a second thought