New Changes to SQL Server 2016 Installation


With every new release of SQL Server, there are many changes that comes like new features, enhancement to existing features, etc. Important thing which DBAs look is SQL Server installation, as we need to first get the downloadable and then install the software to be able to explore the new features or play with the product and some enthusiastic users even want to find bugs and report to the product team. Over a period of time, since SQL Server 2000, there have been many changes to the way the installation of SQL Server in standalone or cluster environment. The installation wizard changes were also inspired by the newer versions of operating systems, like Windows Server 2008 lead to different experience of the installation wizards. In SQL Server 2005, install shield was used, and starting SQL Server 2008 R2, installation center has been introduced with various different options and there were major changes when it came to cluster SQL installation. In SQL Server 2005, cluster install was started from one node and automatically it used to install on both nodes using task scheduler, but there were lot of problems with that, so in SQL Server 2008, the cluster installation was changed significantly, where we install on one node and remaining nodes we perform Add node operation, this made life easier with cluster installs.

Now coming back to changes in installation wizard or steps with SQL Server 2016 are mentioned below.
– In previous versions of SQL Server, in the feature selection page, there were many options which include Database Engine services and under that there were sub options for replication, full-text, Data-quality services. Starting with SQL Server 2016, we now have a new option under database engine services, which is PolyBase Query Service for External Data. If you are wondering what is this new feature, it enables using integrated querying across Hadoop data and SQL Server data using standard T-SQL statements. When we select this feature to be installed along with database engine, there will be additional checks performed by the installer which include checking for Microsoft .NET Framework 4.0, and if Oracle Java SE RunTime Environment (JRE) version 7.51 or higher is present or not. If this are not present, then the installation will fail. Also, after the successful install you will find three new databases DWConfiguration, DWDiagnostics, and DWQueue created by default if we choose to install PolyBase Query Service for External Data.

Another change that comes with SQL Server 2016 installation is, we can now select number of tempdb files when want to create along with the SQL Server installation. Previously this option was not present and DBAs had to manually create additional data files for tempdb. Also, there is a recommendation on number of tempdb files to be created based on number of cores on the server. Primarily, there are the tow main changes, other than this there are changes to licensing agreement and feedback to be sent to Microsoft, which is now an option which we cannot opt out off.

Hope this was helpful.

This is applicable for below versions of SQL Server

Microsoft SQL Server 2016

SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, Frequently asked questions, SQL Server Trainings