Supported versions

–Microsoft SQL Server 2012 (x64) or later

–Microsoft SQL Server 2008 R2 (x64) with Service Pack 1 or later

Required components

–Database engine

–Management tools (recommended)

–Components for specific workloads

Components for specific workloads includes Reporting Services and Analysis Services

DON’T need to install the SQL Server Full-Text Search Engine (SharePoint has its own search engine) UNLESS you’re planning to create an Access Services service application. In this case, there are other additional restrictions and requirements for the database server – you must use SQL Server 2012 or later, you must enable mixed mode authentication on the database, you must enable Named Pipes. Of course there’s nothing to stop you using a separate SQL Server installation to host your Access Services databases.

SQL Server Surface Area Configuration

  • Network configuration  –Enable TCP/IP configuration
  • Configure SQL Server ports   –Standard ports (default instance)  –Dynamic ports (named instances)  –Configured ports
  • Add firewall exceptions

Default instance: TCP port 1433

SQL Server Browser service: UDP port 1434

Instance-Level Settings 

Max Degree of Parallelism setting in SQL Server

This setting controls the number of processors that SQL Server uses to execute queries with a parallel plan. You typically use a higher value if you have a small number of concurrently executing queries relative to the number of processors, and you use a lower value if you have a large number of concurrently executing queries relative to the number of processors.

However, in a SharePoint farm, the optimum value is always 1. You should configure this setting before you deploy SharePoint.

By default, the value is 0, which effectively limits the MaxDOP value to the number of processors.

Some versions of SharePoint will prevent you from provisioning a SharePoint farm if your MaxDOP value is not set to 1 on the database server.

Configuring Client Aliases

  • Configure client alias on each SharePoint server
  • Tells clients how to connect to SQL Server instance
    • –Server
    • –Port
    • –Protocol
  • Use cliconfg.exe to configure aliases
    • –32 bit and 64 bit versions
    • –C:\Windows\SysWOW64\cliconfg.exe
    • –C:\Windows\System32\cliconfg.exe

Installing SharePoint Prerequisites

  • Microsoft SharePoint Products Preparation Tool
    • –Downloads and installs prerequisites automatically
    • –Requires internet access
  • Manual installation
    • –Install prerequisites from a network share
    • –Use prerequisiteinstaller.exe from a command line
  • Install any required updates

 

Scripted Installations

  • Create or modify a configuration file
    • –Config.xml
    • –Files folder contains examples
    • –Remove comment tags from PIDKEY value
  • Provide the installer with a path to the configuration file
    • –setup.exe /config:[path]\config.xml
Patch Slipstreaming

Install service packs and cumulative updates at the same time as the core SharePoint binaries

1.Copy installation files into a local folder

2.Extract updates into the Updates subfolder

–[filename].exe /extract: .\[installer root]\Updates

3.Run the installer

 

Best Practices

  • Check for updates after installing prerequisites
  • Check for pending restarts if you plan an unattended installation
  • Install on non-system drive for best performance
  • Install on all application and web front-end servers before you run the configuration wizard on any server