Hello and welcome to this video tutorial. My name is James Olorunosebi. I’ll be your guide for this video. Today we are going to talk about Installing SQL Server 2008 for a SharePoint 2013 farm. Principally this video will cover three things.
1. Why this is important.
2. Where to get the download files.
3. System preparation, what you need to do before installing SQL server.
Why is this important? It is important because SharePoint works as a database system, and therefore needs a database backend for it to function appropriately. Why SQL Server 2008? SQL server is important because that is what Microsoft has decided will be the database backend for SharePoint, which is their product. So what do you need? You need the SQL server setup files. And you can get that at the Technet Evaluation Center on this URL: https://technet.microsoft.com/en-gb/evalcenter?CR_CC=200157776.
For system preparation, in the real world no business is going to allow you to dump all of the files of the system into the C:\ drive of any machine. The best practice out there i to spread out the various component files into different drives or directories on that server. In this demonstration this is how how system preparation will look like:
For this demonstration, the following will be true.
- C:\Drive contains the operating system of the server.
- *D:\Drive or E:\ Drive will be the installation and user data destination of the SQL Server software.
- *E:\Drive or F:\ Drive will host the user log file of all user data.
- *F:\Drive or G:\ Drive will be where our administrator defined backups will reside
NOTE: * (asterisks) indicate the drive letters will change depending on your machine’s drive letter assignment, especially if you already have your VM enabled for DVD drive.
You will observe in the My Computer window of this machine that there exists only one drive, the C:\ drive. If I run the setup file of the SQL server, what it will do, it will go ahead and install all of the component files into the C:\ drive and that is not what we want to do. It is not an acceptable way of installation. The other drives E: drive, F: drive, G: drive are not currently visible. How do we make them visible?
In this VM that I am using, if we go the VM settings, you will see that I have several SCSI disks of varying sizes. How come these are not reflecting within the server’s operating system? They are not showing because even though they have been attached to the server machine (similar to real physical server machines), they need to be prepared by way of configuration for the operating system to recognize it for usage. What we need to do is:
Start Menu à Run Command à and in the Run dialog box type diskmgmt.msc.
These black-bordered rectangles are the various disks. Disk 0 is the C:\ drive. Disk 1, Disk 2 and Disk 3 are the unknown that are not reflecting in the system. The first step is to right-click Disk 1 and choose Online from the menu to bring the disk online. Repeat this for Disk 2 and Disk 3. Having done this the next step is to Initialize the disks by right-clicking Disk 1, and from the menu choose Initialize. Repeat this for Disk 2 and Disk 3. On completion, right-click again and select New Simple Volume. This will bring up the New Simple Volume Wizard, which will guide us through preparing the hard disk drive for usage.
In the Specify Volume Size page, accept the default values, which is to use all the space in the drive, click Next.
In the Assign Drive Letter or Path page accept the defaults, click Next.
On the Format Partition page, accept the defaults, click Next.
On the Completing the New Simple Volume Wizard page, Click Finish.
It formats the drive and shows it as a healthy primary partition. Repeat this procedure for Disk 2 and Disk 3. On completion now, in the My Computer window, we can see all four drives are present.
At this point, right click Drive E, select Rename from the menu, and type Data.
Repeat this for Drives F, and name it Log. Repeat this for Drive G, and name it Backup.
This naming makes it consistent with what we have in our PowerPoint presentation, and what is obtainable in the industry.
At this point, our system preparation is complete, and we can now proceed to run the SQL server setup file.
So, here at this point I have executed the setup file, and we have the SQL installation wizard come up.
Click on the INSTALLATION link on the left. In the menu on the right pane select NEW INSTALLATION.
The setup support rules executes to identify problems that might occur with your installation, and tells you ahead what you should fix. Here we see that all the checks are passed. Click OK.
Click Setup Support Files, click Install.
On completion, it runs another Setup Support Rules, click Show Details when the rule check completes to see if there are any issues. If all rule checks are complete except Microsoft.NET Application Security, and Windows Firewall, ignore these two and proceed.
On the product key page, provide the key or select Evaluation. On the License Terms page, click I accept the license terms checkbox, and click Next.
On the Setup Role page, click the All Features With Defaults radio button, click Next.
On the Feature Selection page, ensure all the features are selected and the green check mark is present for all features, click Next.
On the Installation Rules page, additional rules are checked, and when completed click View Details, to see what went well or bad. If any problem exists, fix it and re-run the rules. If all are good, click Next.
On the Instance Configuration page, ensure Default Instance is selected. In the Instance Root Directory section, change the drive root from C:\ to E:\. Click Next.
On the Disk Space Requirement page, there is nothing to do here except there is insufficient space problem, else click Next.
At this point on the Server Configuration page, we have to provide credentials for this installation. As you can see on the screen, the various service accounts that I have to use for this installation are not automatic, they are not inbuilt, I have to manually create them.
In the Account Name column, click the dropdown for each SQL service in the Service column, find the browse option, the Select User and Group active directory container dialog box opens up, and click Advanced. Click Find Now, and scroll through the various user accounts for the desired account, click OK, it takes you backward one step, click OK again. Repeat this step for SQL Server Agent account, SQL Server Database Engine account, SQL Server Analysis Services account, SQL Server Integration Services 10.0 account.
On the Database Engine Configuration page, accept the defaults, click Next.
On the Analysis Services Configuration page, click Add the Current User, and also click Add, this brings up the Select User and Group active directory container dialog box, click Advanced. Click Find Now, and scroll through the various user accounts for the Analysis Service Account, click OK, it takes you backward one step, click OK again.
On the Reporting Services Configuration page, accept the default, and click Next.
On the Error Reporting page, accept the default, and click Next.
The Installation Configuration Rules runs again, and all checks out fine. Click Next to continue.
Here is our summary of all of our configurations to this point on the Ready to Install page. Click Install to proceed.
When this installation is complete we will check a few places to verify that SQL server is successfully installed.
On the Complete page, click Close.
To verify the installation, navigate through the Start à All Programs menu and you can see the SQL server folders and programs.
Also, Start à Administrative Tools à Services, scroll down and look for the SQL services, there they are, some Started, some in Manual. In the Log On As column you can see that the various accounts we used for the configurations of the SQL components are present.
The final check itself is to launch the SQL program itself and see.
In the Connect to Server dialog box, ensure the Server Type is set to Database Engine, and the Authentication mode is Windows Authentication. However, you can see that the Server Name text field is blank.
Input a full stop mark or dot (.) into the field. A dot means local machine. Click Connect.
Now we are connected to the database engine and all looks good, and ready for the installation of SharePoint 2013.
Thank you for watching this video, see you again next time.