ChoicesI have selected these SQL Server features:
- Database Engine Services, no sub-features.
- Client Tools Connectivity.
- Client Tools Backwards Compatibility.
- Client Tools SDK.
- Management Tools - Complete.
- SQL Client Connectivity SDK
- Windows 10 Pro (build 10586) virtualized on VMware Workstation 12 Pro.
- SQL Server 2016 CTP 3.2.
PreparationsBefore installation I make some notes on what is installed. How to do this is nicely described by Marc Carter in the blog entry „Use PowerShell to Find Installed Software“.
Also I make notes on which services are running. This can be collected with the cmdlet Get-Service.
Finally I check if .NET 3.5 is enabled on the computer as this is a requirement for my SQL Server installation.
On Windows 10 the cmdlet is Get-WindowsOptionalFeature, but on other Windows (Server) version it is Get-WindowsFeature.
Get-WindowsOptionalFeature -Online –FeatureName NetFx3
In the output the State property indicates if .NET 3.5 is enabled:
FeatureName : NetFx3
DisplayName : .NET Framework 3.5 (includes .NET 2.0 and 3.0)
Description : .NET Framework 3.5 (includes .NET 2.0 and 3.0)
RestartRequired : Possible
State : Enabled
\FWLink : http://go.microsoft.com/fwlink/?LinkId=296822
If .NET 3.5 is not enabled, this can be done
Enable-WindowsOptionalFeature -Online –FeatureName NetFx3
I have experienced this error when enabling .NET 3.5, but checking as above gave a positive result, and the SQL Server installation completed nicely afterwards:
Enable-WindowsOptionalFeature : One or several parent features are disabled so current feature can not be enabled.
At line:1 char:1
+ Enable-WindowsOptionalFeature -Online –FeatureName NetFx3
+ CategoryInfo : NotSpecified: (:) [Enable-WindowsOptionalFeature], COMException
+ FullyQualifiedErrorId : Microsoft.Dism.Commands.EnableWindowsOptionalFeatureCommand
InstallationThe SQL Server installation is usually done by the wizard or by command-line. This I will look into the details later.
In this case I use the default service accounts given by the SQL Server installation, but I change the SQL Server Agent Startup Type to Automatic. These issues are subjects for many great discussions, but not here and now.
SQL Server 2016 gives the possibility to enable Database Instant File Initialization on installation, but I have chosen not to. The subject is greatly described by Kimberly Tripp in the blog post „Instant Initialization – What, Why and How?“.
The default collation for the SQL Server installation is still the SQL collation „SQL_Latin1_General_CP1_CI_AS“ where the recommendation for some years has been a Windows collation. Usually I recommend the SharePoint collation „Latin1_General_CI_AS_KS_WS“ to ensure a better information integration. In this case I changed to the collation „Latin1_General_100_CI_AS_KS_WS_SC“ to get the Special Characters available.
With SQL Server 2016 it is now possible to configure tempdb on installation. This is a really great feature – that I have not used in this case.
The installation took about 44 minutes by the summary log file.
ControlLike before the installation I note what is installed and which services that are running.
Also I take a look into the summary log file.
Post-ConfigurationUsually I stop and disable the SQL Server VSS Writer service as I take backup with T-SQL through the Database Engine:
Get-Service -Name SQLWriter | Set-Service -StartupType Disabled -Status Stopped
Finally I run Windows Update to get the latest patches for the new components on the computer. In this case there were a Security Update and a regular Update for Visual Studio 2010 SP1 (KB2645410 & KB2635973).