Home > SharePoint > Just another SharePoint VM–Part 3–Installing SQL Server 2012

Just another SharePoint VM–Part 3–Installing SQL Server 2012

Now that we have a virtual machine with Windows Server 2012 installed and configured with the roles/services required (published in Part 1) and the service accounts required all set up (published in Part 2), we can go on to the next step – installation of SQL Server 2012. It is possible to install SharePoint 2013 with a built-in version of SQL but I wanted to attempt using an individual instance of SQL Server 2012.

We start by choosing to open the ISO file for SQL Server 2012 from the VirtualBox menu and when the virtual drive loads up, choose to run “setup.exe”.


Screen clipping taken: 10/5/2012 10:08 AM

The SQL Server Installation Center launches with all the usual guidance around planning for deployment of SQL Server.


I chose to move on to the next step – Installation by clicking on the link on the left and the following options are presented:


Chose the first option “New SQL Server stand-alone installation or add features to an existing installation”. Setup support rules are run and any items that may prevent complete or proper setup of SQL Server will be identified here. In my case, everything passed.


Clicked on “OK” to move on to the next step. Here’s where you choose to install an evaluation copy or enter a key if you have one and move on.


Read and accepted the license terms on the next screen and moved on.


The following warning came up with searching for updates – this was because after I had made my DNS installation on the machine, I’d forgotten to go back and auto-detect DNS on the VM virtual network card. This is a problem that can be fixed later by ensuring the tunnel through to the host machine network works. So I moved on.


Installation of setup files comes next


The following warnings showed up


The first that the computer is a domain controller. But we are doing that by intent – so that is fine to ignore. The second was caused by my non-existent internet connection again which should be remedied later – so I ignored it. The last relating to the Windows Firewall was expected as well since I disabled it. Moving on. The next screen is for the role you want to install. Went with “SQL Server Feature Installation” here.


Next comes the feature selection page. Since I was installing a developer machine for some basic testing, I went with Database Engine Services, the Management Tools and the SQL Client Connectivity SDK. You can always add features to the existing instance later.

NOTE: If you would like to use Business Intelligence features on SharePoint with Analysis services in SQL Server, choosing Analysis Services here will help. If you would like to use reporting features, installing SQL Server Reporting Services will help. This will require installing the SQL Server Reporting Services add-in for SharePoint and will require some configuration post installation.


Again, an installation rule check occurs and any failures are reported. Clicked “Next” to move on


The instance configuration page is next. I chose to install the default instance:


A small pause and the disk space requirement page is shown. Our allocation of space on the virtual machine disk should suffice for this requirement.


On the Server Configuration page that shows up next, we set up the service accounts we want to use for the SQL Server Agent and the SQL Server Database Engine – the account known as SQL Service above. To do this, I dropped down the account name and “Browse…” for the user by typing their name into the object selection box and clicking on “Check Name”. Once the name was resolved, I clicked on “OK” to add them in. Back on the Setup page, you will need to type in the password you used when you were creating the account.


This is what it should look like when done. Note that I keep the Startup Type on both as they are before I hit “Next” to move on.


On the next screen we get to specify the authentication mode -which I always keep as Windows – and list administrators – where I always add the “Administrator” which is easily done by clicking on the “Add Current User” button


I don’t change anything on the “Data Directories” tab usually – where SQL Server chooses to put its files is fine by me. I do head over to the FILESTREAM tab and make the following selections. These will help with configuration of Remote Blob Storage if required. You should be able to do this from SQL Configuration Manager later.


Next Step, error reporting. I didn’t turn this on and moved on.


Again a configuration rule check which passed in my case. Moved on to the next step


An installation summary is shown for all things selected and configured so far


Clicked “Install” and off we go… this could take a while so go get your coffee and donuts or whatever.


Done. SQL Server is installed.


The start menu looks fuller now


Now for some configuration – launched the SQL Server Management Studio and connected to the local database engine


Expanded the “Security” branch and selected “Logins”. Right click and select “New Login…” to add a new login for the SharePoint Setup account – known as SP Setup above.


On the “Login – New” dialog, clicked on “Search…” to locate the user named SP Setup. In the lookup dialog, typed spsetup and hit “Check Names” to resolve the name, then hit “OK”. Back on the “Login – New” dialog, selected “Server Roles” in the left navigation and checked the roles “dbcreator” and “securityadmin”


That’s it. Hit “OK” on the dialog to create the new login and assign the server roles specified.

After the installation of SharePoint 2013, during configuration, one of the things the Configuration Wizard attempts to do is to check the maximum degree of parallelism setting on SQL Server. This “maxdop” setting determines how many processors SQL Server can assume it can use to create its execution plans. For some reason, the standard installation of SQL Server 2012 sets this to ‘0’. We need this to be at least ‘1’.

Now if we were using the administrator account during SharePoint configuration, it probably wouldn’t be a problem because this account would have the permissions to change the setting on the fly. However, since we intend to use the Setup service account (and I haven’t been able to figure out what permissions this account will require to be able to change this setting), it would make sense to have this setting made before we get to that stage.

Therefore, there is one more thing to do while we are within the SQL Server Management Studio. Right click on the server name at the top and select properties.


This brings up the properties dialog. Selected “Advanced” from the left navigation and found “Max Degree of Parallelism” under “Parallelism” and changed the value against it (was 0 to start with) to 1. Clicked on “OK” to apply.


With that we come to the end of the installation of SQL Server 2012 and configuration in readiness for the installation of SharePoint 2013. The next step is to go ahead and install SharePoint 2013 itself.

Read about installation and configuration of SharePoint 2013 Preview in Part 4.

  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: