 Hello and welcome. My name is Mark Heslin. I'm a senior principal engineer at Red Hat and also the technical program manager for the Red Hat and Microsoft partnership. I'm here today to show a simple demonstration on how to install SQL Server 2017 on Red Hat Enterprise Linux. This demonstration tends to show how quickly and easily it can be deployed. For our purposes today I've used a developer edition. This is a fully functional version of Red Hat Enterprise Linux intended for non-production use. If you're interested in learning about our offerings for a developer program, please go to developers.redhat.com. At the same time I've already run a young update on our host. The local host is a laptop and any bare metal simple VM deployment will work fine for this purpose. The demonstration today consists of three parts. First we'll install SQL Server itself, then the command line tools, and then we use a sample database to do a load and query against. The total time to complete this is about five minutes. Let's get started. First we need to download the repository. We'll do a simple sudo curl. Next we'll install the SQL Server bits itself with the sudo young install. This is the longest portion of our time to take. It's fairly quick as you can see it's just about done now. Now it's beginning the installation itself. There we go, it's complete. Now when the installation runs by default it starts the SQL Server service itself. So what we'll do is we need to stop it to run the setup. So we'll run that sudo system cuddle stop. And then we'll run the setup itself. First time through it's going to ask you to accept the license and do what edition you want to select. So we're going to do the eval edition here. Set the system administrator password. It reminds us that this is an eval version. Let's start SQL Server back up now. Now we can see with the simple system cuddle status we can double check the service and we see it's active and running. And then last we have to set some firewall connections to allow remote access to port 1433 TCP. Simple sudo firewall command and then do a reload and activate it. So that completes the first part. So now SQL Server is installed. So let's move on to the command line tools. Now just like the database itself, the command line tools has a repo. So we'll pull that down with a sudo curl. Next it's recommended to remove any old Unix ODBC drivers. So we'll do that here. Now I didn't have any installed so it's just going to tell me that, which it does. Next we'll install the tools themselves. Again sudo yum install. It asks us to accept the license terms. We'll say yes. Note it is case sensitive. It must be uppercase. And that completes installation of the tools. And last we'll change our path so that we can find the tools. So we'll modify our .bash profile, our .bash rc, and then we'll source .bash rc to make it active interactively. Next let's use the SQL command tool to actually connect to the database. So format simple, SQL command, name of the host, the user is the system administrator, SA here, and then your password. So we've connected. I'm going to show here just the version just to confirm and we can see the version. So the database is up and running at this point. So that completes the command line tools. So now let's do a simple load of a sample database. I've created one here and loaded up with a script called loadDB. Let's see what that looks like. So it's a simple database. I'm doing a create database. I'm using a new Hampshire mountain theme, one I was like to hike here in the northeast. So we create a simple database. We'll load it up. It's the name of the peaks and the elevations. So now we'll run the command to load it. It's inserted everything in there. The rows are there. So that completes the creation of the sample database. Now let's run some queries against it. I've also created a simple SQL script, a query. Take a look at that. Three simple queries. First select the mountains order by the highest elevation and then list them in descending order. Next we do a simple query by names and sort them by ascending order. And the last is a simple query to look for elevation of peaks between 5,000 and 6,500 feet. We'll run that command. And here we can see our output. I can scroll back up. Here's our first query. So it changed to the Hampshire mountain database. You see from Mount Washington, our highest peak, down to our lowest peak, the mighty Takunza, as we like to call it here. Then the sorted list of the 48 peaks in alphabetical order, A to Z. And then last, our listing of peaks that matched the criteria between 5,000 and 6,500 feet. And that concludes our demo for today. Thank you very much for your time.