Ulysses Ludwig’Blog

This article describes the steps to install and configure SQL Server 2012 on Windows Server 2012 from permissions management to the installation and configuration process to creating a SQL alias for use as the core to a SharePoint 2013 lab. During the install, the latest version of SQL Server 2012 was downloaded from Microsoft.com as an ISO disk image, which was mounted to VMWare using VMWare’s native capabilities.

Note that this article is intended for installation in a development environment and should only be used as reference material. This guide should not be used for a production SQL server installation.

SharePoint 2013 Lab build – 8 Part Series

• SharePoint 2013 Lab Build - Part 1 - Getting Started
• SharePoint 2013 Lab Build - Part 2 - Windows Server 2012 Installation
• SharePoint 2013 Lab Build - Part 3 - SQL Server 2012 Installation (YOU ARE HERE)
• SharePoint 2013 Lab Build - Part 4 - Security Configuration
• SharePoint 2013 Lab Build - Part 5 - SharePoint Server 2013 Install
• SharePoint 2013 Lab Build - Part 6 - SharePoint Server 2013 Configuration
• SharePoint 2013 Lab Build - Part 7 - Visual Studio and SharePoint Designer Installation (INCOMPLETE)
• SharePoint 2013 Lab Build - Part 8 - Windows Azure Workflow Installation and Configuration

Table of Contents

• Create the Service Account
• Install SQL Server 2012
• Configure a SQL Alias

Create the Service Account

Create a SQL service account to run SQL.

Naviagate to and open ADUC.

Create the SQL service account, SQLService, under the Managed Service Accounts organizational unit (OU).

Install SQL Server 2012

Mount the SQL Server 2012 ISO and run the installer.

Note that if SQL Server 2012 was downloaded as an executable, the file can simply be copied to the server and run.

Select the file from the download location.

Run setup.exe.

Create a new SQL Server stand-alone installation.

It is not unusual to see warnings. Errors, identified in red, will need to be addressed before moving forward.

Choose the setup role to install SQL Server Features, which are the components of SQL Server itself.

Select the items that will be useful on the development box. Not all items are required and many, other than the core Database Engine Services, can be left unchecked.

Scroll down and select additional features as needed. Client tools should be checked unless the SQL Server will be managed remotely.

The installer will validate the environment against the selected features.

Update the target install location as needed.

Specify the appropriate service account to run each feature. Some features that run using local or built-in accounts will be greyed out.

In a development environment, it is not unusual for all of these accounts to run under a single account, such as SQLService.

Add the current user, the Administrator, and/or Enterprise Admins. In addition, only allow Windows Authentication Mode (this can be changed later).

Enterprise Admins are a useful group to grant access to SQL and SharePoint itself as it can provide immediate blanket access to resources for users logged in using their closely guarded Enterprise Account. With that said, membership to the Enterprise Admin group should be closely guarded and managed.

Grant the same users access to Analysis Services

Install reporting services but do NOT configure it at this time. If the environment will host SQL Reports in “integrated mode”, then the reporting server needs to be configured after SharePoint.

Note that integrated mode allows SQL Server Reporting Services Reports to “live” within SharePoint instead of being published and managed by the reporting server.

Review the installation plan.

Success!

Configure a SQL Alias

After installation, it is important to configure a SQL Alias for SharePoint. This allows SharePoint to point to a local SQL Server, then be re-homed to point to an external SQL server at a later point without having to run complicated migrate server commands.

Click on the start menu the start typing the letters “CliConfg.

Enable TCP/IP.

Create a SQL Alias so that SharePoint 2013 can be pointed to a different machine in the future.

Shut down the virtual machine and take another snapshot.

Continue onto SharePoint 2013 Lab Build Part 4 to configure security.