Making sure SQL is the right version for 2013
Am in the land of setting up quite a few 2013 environments to demo and test. Some using VMware, HyperV, Cloudshare to name a few. Ran into a ‘gotcha’ starring SQL which I thought I would share. In this scenario I’m setting up a Dev / POC environment which is a single server SharePoint 2013 environment and not set as a Domain Controller. SQL is also deployed to that box. Using the UI it’s not possible to create a new farm due to the fact I’m using a local account as farm admin, therefore, had to use the wonderful New-SPConfigurationDatabase Powershell command to create the SharePoint config database).
