1. Setup and Installation of SQL Server 2016
One of the major updates to SQL Server 2016 is the addition of R as an integral part of the database engine. R began in 1993 as a data analysis language developed by Robert Gentleman and Ross Ihaka at the University of Auckland. It started as a language that could rival the S language in statistical analysis and evolved into arguably the most popular language in the world for statistical computing, data analysis, and machine learning.
With the business world making a major shift toward business intelligence and data analysis, the addition of R as an integral part of SQL Server is a smart business move for Microsoft. Not only is Microsoft introducing new functionality into an already widely accepted platform, but they are also leaving the core of the language intact so that current R statisticians can easily move onto the SQL Server platform to enhance their statistical computing methodology. In the end, this enhances visibility for Microsoft in the business intelligence field, and hopefully, leads to even greater acceptance for SQL Server in everyday data analysis operations.
In 2016, Microsoft bought Revolution Analytics, which is built around R and provides both an open source (Revolution R Open) and commercial (Revolution R Enterprise) development platform for R. Heavy integration of R into existing products is now Microsofts focus, with the obvious choice of SQL Server and, eventually, Azure. This is an exciting release, because it gives Azure hosted services the opportunity to deliver content based on R computations done in an Azure site or database.
Since R has been added as an installation portion of SQL Server 2016, all we need to do is select the option during installation to add it and then run through some minor configuration tasks.
There are certain things that we need to check and install to make sure that R runs, but I will show all that when we get there. For now, download SQL Server 2016, and then follow along with me on how to install it. It is worth noting that your installation screens may vary slightly from mine, depending on the service packs or if Microsoft decides to change the install screens, but I think that the gist of the content will be the same.
Planning
First things first though. Once you download SQL Server 2016, you want to plan out the basics, such as the account that youre going to use and where your default file locations are going to be. If you read my last book, then you know that I have a very particular way in which I organize my file system for SQL Server. For this book, I make a separate logical disk (E:\) with the following folder structure :
So, one main folder, SQL Server, and then three folders inside of that folder to hold the different bits as needed. There can be other folders, such as DTSX or Output, which you can use for other things, but for the most part, those three subfolders inside of the main folder work nicely.
Note
There are other locations that SQL Server wants to place files in during installation; this is fine, since this is how SQL Server wants to categorize the system files to keep everything copacetic. We will have control over our data, logs, and backups in the folders specified earlier.
As far as which account you should use to run the functionality of SQL Server 2016, this should be a no-brainer. It needs to run as if it were a regular database installation, so it needs to have the account assigned that it would normally have. To be clear, assign the same account that you are currently using for whatever version of SQL Server you are running. Most times, this needs to be an administrator in order to install programs.
A quick side-note here: if you havent read the hardware and software requirements for SQL Server 2016, you probably want to do that. Also, Appendix A covers installation of SQL Server 2016 onto an existing SQL Server 2014 server. If you are running SQL Server 2014 and want to try SQL Server 2016 on the same server, then look to Appendix A for guidance. (But in no case should you ever use a production server to follow along with this book).
Beginning the Installation
Here we go! Double-click the setup.exe file in the download folder. You should see whats shown in Figure .
Figure 1-1.
Initial SQL Server 2016 installation screen
If you see the screen asking to make changes to your system, go ahead and say Yes .
Figure .
Figure 1-2.
SQL Server 2016 installation options
Once here, click the top link, titled New SQL Server stand-alone installation or add features to an existing installation .
Note that the very bottom option is something new. It says New R Server (Standalone) installation . You would select this option if you only wanted to install R Server as either a server (standalone, self-contained data analysis server, in other words) or a client (manipulating data from a remote SQL Server R Services installation). Note that you need the SQL Server 2016 services running as well, so this would be to add R services to an existing SQL Server 2016 installation.
Product Key
Next is to enter your product key . Figure in the prior section. Here you can specify that you wish to run the free edition, or you may enter a product key in order to run a licensed edition.
Figure 1-3.
Product Key screen
SQL Server 2016 can be installed in one of three free editions:
Evaluation : A full set of features; basically, the Enterprise version of SQL Server 2016, but only good for 180-day spans.
Developer : A full set of features, but cannot be used for production database work.
Express : The smallest, bare-bones installation of SQL Server 2016; does not expire and can be used for production use.
If you would like to choose an option other than Evaluation, go right ahead. Just understand the implications of choosing that option; for example, the Express option doesnt support R so I wouldnt choose this option. For what you need here, the Evaluation version is perfect, because you certainly decide within 180 days if this new functionality is something you want to permanently include in your SQL Server installation.
When you have chosen the version you are most comfortable with, click Next to continue.
License Terms
The next screen, shown in Figure , simply asks you to accept the license terms.
Figure 1-4.
License terms