Easy-to-follow video tutorials help you learn software, creative, and business skills.Become a member
So I am going to go ahead and get started installing SQL Server 2008 R2 Standard edition. I have the installation media for a regular standard install here. I'm going to launch the setup application. Now I would often tell you to go and grab a cup of coffee while doing this but there'll be plenty of time for that. Installing SQL Server is a long install procedure and there are many steps to it. It's not something to try and do in a hurry. So let me tell you a little bit about what to expect here.
If you have a setup that is magically identical to mine in every single way, then you will have a similar experience to me. But if your machine or your environment differs in the slightest, you will have a different experience installing SQL Server. So if you have a different operating system or a different set of applications installed, you might expect to see a different message now and that's okay. It's just part of the deal when installing SQL Server. In fact, the first thing that opens here is not some kind of Next, Next, Next install.
It's called the Installation Center and it's on the first page, which is Planning, and there are whole bunch of different things. Documentation for requirements and Setup Documentation and Upgrade Advisors. If you've got old versions, Upgrade Documentation. What I'm going to do here because I'm on a fairly fresh machine is just run the System Configuration Checker and it's going to go through a whole bunch of rules just to give me some idea whether I can go ahead and install this. So just take your time, run this, pay extra attention to any messages you get during that installation.
You may have to install some prerequisite software if it's not on your machine already. So this runs through a whole bunch of rules. It says it's Passed: 15 and Failed: 0. I can click for the details and I can see the type of things it's checking. Things like whether the computer has been restarted recently, does the operating system work, are there any problems with incompatible SQL Server versions? Everything looks good, so I'll click OK. That didn't do anything except run a few checks.
We'll still have a few more checks to go on as we go forward. I am going to select the Installation section here on the left-hand side and over there I'll say I want to do a new installation. There obviously are different ideas and different options if I'm installing on top of say SQL 2000 or SQL 2005. But it's a new one for me and before it does its thing it's going to make me go through a whole bunch of different questions about how this is going to be installed.
It first runs its own set of rules. I can click Show details. Everything looks good. Click OK. Then it gives me the opportunity to enter in my product key. Also here you could actually choose to install an evaluation or trial edition without a product key or even select the Express edition or Express with Advanced Services. I am just going to go ahead and do a regular install, so I'll click Next. I will accept the license terms and usually that would be about it, but we still have a long way to go.
What SQL Server it will do now is install support files. This is not at doing the proper install. It takes longer than most installs you would do but this is just some supporting stuff in the background. So I am going to click the Install button to go ahead with that and that will take a couple of minutes. When it's done it will appear to disappear for a second but it should come back in just a moment with the results of those support files.
What I can see here is most things have been passed. I do have a warning here besides Windows Firewall and if I click that it will tell me that it's detected that the Windows Firewall is enabled. And that will be a problem if I was expecting someone else to be able to connect to the SQL Server on this machine, if I am shutting them down with my firewall. It's okay because this is a development machine so I am going to say that's not a problem and go ahead and click Next. Next up, we have a choice . Are we installing SQL Server by selecting the different features, the different component pieces of it, or do we want to install all features with defaults? The second option here would be the easy button but I'm not going to do that.
I am going to step through the feature level installation. Even though I am going to install everything I want to show that part to you. So click Next into the different features and this is where we see that yes indeed, SQL Server is installed as our whole bunch of different pieces. The database engine itself and the different parts of that such as Replication and Search. Analysis Services, Reporting Services, then a lot of different tools like Books Online the Business Intelligence Development Studio, the Management Tools.
In fact I am just going to go ahead and click the button to say Select All. I am not going to touch any of the paths that this will be installed on. Just accept the defaults there and click Next. It runs one more in a whole bunch of checks that it's running through and everything looks okay. I'll click Next. What it's asking me now is what's the name of the Instance. And what does this mean? Well, you can actually install multiple instances of SQL Server and each instance can contain its own set of databases.
It's not something you have to do but you can have up to 50 instances of SQL Server on one machine. If you do, you have to give each of those 50 or 5 or 10 a different name. But if we're installing it from scratch we can say I don't need to name this instance because I'm not intending to put any others on. So I'm just going to call it the default instance. That means later on if I want to access this instance I don't really have to care about what it's called because it's the default instance on this machine. I can see there are no existing instances here.
So I will go ahead and click Next. It gives me a summary of the amount of space it's going to take up, not something I really care about if I've got plenty of disk space available and I'm not expecting this database to grow very large. I'll click Next. What we have now is the place that I can plug in those service accounts that I created a little earlier, giving different identities to each part of SQL Server that will be running. So I'm going to go ahead and type in the account names that I had set up earlier, the first one being for SQL Server Agent and give it the password that it knows about.
Then the database engine, which for me was SQLEngine, and go ahead and enter the remaining service accounts. I am going to leave the last two just setup as using the built-in local service account. This is a fairly low privilege account, which is fine for those. The tab behind it is something called Collation. I am not going to touch that. Collation is the idea of how does SQL Server do things like case sensitivity and accent sensitivity behind the scenes. If you are ordering a bunch of last names of people, does it care whether it's an uppercase A or a lowercase a? Does it care if it's an a or an a with an accent over the top of it? I'm going to accept the default, which is just for this case a SQL Latin1-General case-insensitive, accent-sensitive, and just not touch it.
But if you have to handle multiple languages, you may have to do something slightly different. So I'll go ahead and click Next and it asks me how the security is going to be set up on this instance of the database, and it's saying the authentication mode is Windows authentication or Mixed Mode. Windows is the default and it means that everybody who's going to get access to these databases has to have a Windows account and it's by that that we will specify what they're allowed to do.
Mixed Mode means there could be either a Windows account or you could actually set them up their own username and password within SQL Server. It wouldn't be a Windows account. Now the default and the recommendation for Microsoft these days is stick with Windows authentication mode because it's a bit more secure. But in some cases, say when you're building web applications you may be working with Mixed Mode and you get to set up different kinds of accounts. I'll leave it at the default, and the only thing I'm going to do on this screen is down here where it asks me to specify the SQL Server administrators.
I am going to say Add Current User. Yes, I want to be added as an administrator on this box. I am going to leave the other two tabs of Data Directories and FILESTREAM, which name both where these files are going to be installed on the machine. FILESTREAM is a new feature in SQL 2008 that allows you to store large files, even bigger than two gigabytes, on the file system and still manage them through the database. I'm not going to touch this right now. It's little bit beyond the scope of this class. So with Windows authentication mode set and me listed as the user I can go ahead.
Just to let you know, you can actually change the authentication mode later. So it's not a disaster if you have the wrong one. Next up, it's asking me to specify the administrators for Analysis Services. This isn't something we've talked about a lot yet, but what I'm going to do is just go ahead and click that Add Current User button again and name myself as having unrestricted access there and just go ahead and click Next. In this screen, we're being asked to set up Reporting Services, this part of SQL Server that can handle reporting.
There are three options here. Installing the native mode default configuration, getting it set up from scratch to install with SharePoint, and then installing it but not configuring it. I am again going to accept the default one, which is the first option, and click Next. I am going to choose not to send any error reports to my corporate report server and click Next. It runs through a few more checks. I am going to say Show details. Everything looks okay.
Click Next and it gives me a summary. It's going to install all these different features. These are the names it's going to use. These are the accounts that it's going to use. As you can see, there is a whole lot of stuff going on here. We're ready to go. I'm going to go ahead and click Install and this will take several minutes. So I'm just going to go ahead and let it do its thing. So later on, perhaps much later depending on the speed of your machine, but certainly after many minutes you should hopefully get to this screen, that your SQL Server 2008 R2 installation completed successfully.
It will give you a log file if you feel like you need to take a look at it. Obviously if there are any alternate messages, you get anything else, you need to go and take a look at that too. But hopefully that should do it. Going back to the Installation Center we can also run a search for product updates. I am not going to do that right now but it's certainly something that in the long process we should do. So we now have SQL Server 2008 pretty much up and running. If I look at my All Programs I should find a whole section under SQL Server 2008 R2 with the Analysis Services Tools, Configuration Tools, Documentation, Integration Services and Performance, and we're going to go through quite a few of these as we go through the course.
But we're ready to go.
Get unlimited access to all courses for just $25/month.Become a member
Access exercise files from a button right under the course name.
Search within course videos and transcripts, and jump right to the results.
Remove icons showing you already watched videos if you want to start over.
Make the video wide, narrow, full-screen, or pop the player out of the page into its own window.
Click on text in the transcript to jump to that spot in the video. As the video plays, the relevant spot in the transcript will be highlighted.
Your file was successfully uploaded.