Database Journal
MS SQL Oracle DB2 Access MySQL PostgreSQL Sybase PHP SQL Etc SQL Scripts & Samples Tips Database Forum Rss Feed

» Database Journal Home
» Database Articles
» Database Tutorials
MS Access
SQL Scripts & Samples
» Database Forum
» Slideshows
Free Newsletters:

News Via RSS Feed

Rss Feed

Database Journal |DBA Support |SQLCourse |SQLCourse2

Featured Database Articles


Posted November 2, 2015

Installing SQL Server 2016 - Page 2

By Greg Larsen

Once the JRE was installed I clicked on the “Re-Run” button.   This ran through the feature rule tests again.  Since no errors where found this time, I was taken directly to the “Instance Configuration” window. 

“Instance Configuration” Window
“Instance Configuration” Window

Here I decided to create a default instance, instead of a named instance. When I clicked on the “Next>” button the “Server Configuration” window is displayed

“Server Configuration” Window
“Server Configuration” Window

Here I can define the accounts that will be used for each service, and additionally I can use the “Collation” tab to identify the collation I would like for my instance. When I look on the “Service Accounts” tab I noticed two new services: SQL Server PolyBase Engine, and SQL Server PolyBase Data Movement.  These two services are shown here because I selected to install the “PolyBase” feature.  If I hadn’t selected to install the new PolyBase feature then these two services would not have shown up on “Service Accounts” tab.  From my test installation I just take the default values for the “Account Name”, “Password” and the “Startup Type”. When I click on the “Next>” button the “Database Engine Configuration” window is displayed. 

“Database Engine Configuration” Window
“Database Engine Configuration” Window

On this window you can see a new tab called “TempDB”.  I’ll get to that tab in just a bit, but first on the “Server Configuration” tab I just take the default “Windows Authentication” for my “Authentication Mode”.  I also click on the “Add Current User” button account I’m using for the installation.  When I do that the account I am logged in as will be placed in the “Specify SQL Server administrators” section of the screen below.  In my case that will be my machines “Administrator” account. I then click on the “Data Directories” tab, which brings up a list of default directories where the installation process will store different SQL Server components. 

“Data Directories” Tab
“Data Directories” Tab

I just take the default directory settings.   If I was doing a real installation I would not put anything on the C drive.  Instead I would spread out these directories across one or more drives to optimize I/O contention. But on my test machine I only have a C drive. For the next step of my installation I clicked on the “TempDB” tab. This brings up the configuration options for TempDB. 

“TempDB” Tab
“TempDB” Tab

This tab was a new addition that was added with the rollout of CTP 2.4.  On this screen I can configure the number of tempdb data files I want.  By default the installation my installation process set the default to the number of core on my machine, which is 4.   The initial number of temdb files is determined by the number of cores, up to 8 that is.  If your machine has more than 8 cores this initial number of tempdb will be set to 8.  In my case I have 4 core, so that’s why 4 came up as a default.  I could have changed this number to something less than 4.  But I just left this item set to 4.   Additionally this screen allows me to set the initial size and autogrowth setting for my tempdb data and log files.  This is a great addition.  No longer do you need to go to a post installation step to configure multiple tempdb data files and set appropriate sizing setting for all tempdb data files.  When I click the “Next>” button the “Ready” to install window is displayed. 

“Ready” to Install Window
“Ready” to Install Window

Here I can use the scroll bar on the right side to review the installation setting I selected.  If for some reason I wanted to change one of the settings because I incorrectly set it during the prior installation screens, I could then use the “<Back” button to go back and modify the installation options I selected.

After I’m satisfied with my installation settings I then clicked on the “Install” button to start the installation process.  When I do this the following “Installation Progress” window is displayed.    

“Installation Progress” Window
“Installation Progress” Window

Once my installation is finished the “Complete” screen and the “Computer restart required” windows are displayed.

“Complete” Screen and the “Computer restart required” Windows 
“Complete” Screen and the “Computer restart required” Windows

I closed the “Computer restart required” screen by clicking on the “Ok” button.  After doing that I could use the scroll bar to review the status of each of the features I installed.  Once I’m done reviewing my installation results I then clicked on the “Close” button and restarted my machine.

Once my machine was restarted I had my installation of SQL Server 2016 CTP 2.4 up and running. 

Trace Flags 1117 and 1118 are no longer needed

In the old days when you had to configure multiple tempdb data files it was recommended that you also turn on trace flags 1118 and 1117.   Those days are now gone with SQL Server 2016.  There is no need to set Trace flag 1117 to make sure your tempdb files all grow at the same time.  There have been improvements is how page extents verses mixed extents get allocated to tempdb file.  With those improvements you no longer need to set trace flag 1118.  

What I got when I installed PolyBase

When I install PolyBase, I found three new databases defined on my instance.  Not only that, I also found two additional services were installed.

I looked under the “Database” node in SQL Server Management Studio (SSMS) and found the three databases used to support PolyBase:

“Database” Node in SQL Server Management Studio (SSMS)
“Database” Node in SQL Server Management Studio (SSMS)

These databases are: DWConfiguration, DWDiagnostics, and DWQueue.    

Additionally if you use the services applet (services.msc) you can see there are two PolyBase services:

Two PolyBase Services
Two PolyBase Services

Based on the description, the “PolyBase Data Movement” services manages communication and data transfer between SQL Server and external data sources, whereas the “PolyBase Engine” creates, coordinates and executes the parallel query plan against external sources.


As with any new release of SQL Server there are many new features to explore.  In this article I highlighted those new features you can configure as part of the installation of SQL Server.  Keep in mind I only showed you CTP 2.4, which is just a preview of things to come.  It is not the final baked version of SQL Server 2016.  Therefore the final release of SQL Server 2016, or any future CTP might look slightly different then what was shown here.   Download CTP 2.4 today and start exploring all the cool new features that are available in SQL Server 2016.

See all articles by Greg Larsen

MS SQL Archives

Latest Forum Threads
MS SQL Forum
Topic By Replies Updated
SQL 2005: SSIS: Error using SQL Server credentials poverty 3 August 17th, 07:43 AM
Need help changing table contents nkawtg 1 August 17th, 03:02 AM
SQL Server Memory confifuration bhosalenarayan 2 August 14th, 05:33 AM
SQL Server Primary Key and a Unique Key katty.jonh 2 July 25th, 10:36 AM