Installing SQL Server 2008 R2
The SharePoint databases need to reside in a SQL Server implementation. The version of SQL must be either SQL Server 2008 or higher, or SQL Server 2005. The SQL server component can either reside on a separate server or installed on the SharePoint server itself, for smaller, single server deployments.
This chapter assumes that the full SQL Server 2008 R2 product will be installed on a single SharePoint all-in-one server. Installation steps are subsequently illustrated for this scenario. The same concepts can be used for installing a two-server farm as well, with SQL Server on a single server and all SharePoint roles on another server. For more advanced installation scenarios, including scenarios where SharePoint is installed from PowerShell, refer to Chapter 4.
Installing SQL Server 2008 R2
From the SQL 2008 R2 binaries, perform the following steps to install:
- Run setup.exe from the SQL binaries.
- SQL Server 2008 R2 requires the .NET Framework; click OK to install it.
- From the SQL installation center, shown in Figure 3.1, click on the installation link in the navigation bar, and choose the link for new installation or add features to an existing installation.
Figure 3.1 Starting a SQL Server 2008 R2 install.
- Click OK on the Setup Support Rules dialog box.
- From the dialog box specifying the edition to install, enter a valid product key, and click Next to continue.
- Check the box to accept the license terms, and click Next to continue.
- Click Install to install the Setup Support Files.
- Review the warnings, as shown in Figure 3.2, and click Next to continue.
Figure 3.2 Reviewing setup warnings from SQL Server.
- Select SQL Server Feature Installation from the Setup Role dialog box; then click Next to continue.
- From the Feature Selection dialog box, click the Select All button, and click Next to continue. In a distributed environment, some SQL services may run on separate servers, but for a single SQL Server environment, all services may be installed.
- Click Next at the Installation Rules dialog box.
- Choose to install the Default instance, and click Next to continue.
- Review disk space requirements, and click Next to continue.
- From the Server Configuration dialog box, choose Service Accounts for each service. In most cases, you'll want to use the NT AUTHORITY/SYSTEM accounts for each service, as shown in Figure 3.3. In certain other cases, you may need to specify service accounts. After setting the service accounts, click Next to continue.
Figure 3.3 Setting SQL Service Accounts.
- Under the Database Engine Configuration, choose Windows authentication mode. Click the Add Current User button to add the installation account as a SQL Administrator. (Or add an account that will be logged in later.)
- Click the Data Directories tab, and choose default installation directories for logs, database files, and backup files. It is recommended to do this in advance and to separate SQL Logs from the databases from the beginning. Click Next to continue.
- For Analysis Services configuration, add the Current User as an Administrator, and click the Data Directories tab. Select directory locations for data and logs, separating them on separate drive spindles when possible. Click Next to continue.
- For the Reporting Services integration, select to install the SharePoint integrated mode default configuration, as shown in Figure 3.4. This enables Reporting Services to be integrated with SharePoint 2010. Click Next to continue.
Figure 3.4 Installing SQL Reporting Services in SharePoint integrated mode.
- Accept the defaults for Error Reporting, and click Next to continue.
- After the installation configuration rules have run, click Next to continue.
- At the summary page, review the settings and click Install.
- When the install is complete, review the summary log file and click Close to finish.
Post-installation tasks should be conducted after SQL Server has been installed. Some of these post-installation tasks will validate whether the installation was successful, whereas other tasks are required to ensure that the server is secure and operational. The post-installation tasks include the following:
- Review installation logs.
- Review event logs.
- Obtain and apply the latest SQL Server service packs and critical updates.
- Verify the server components that were installed.
It is also critical to rerun Microsoft Update to apply any necessary SQL Server patches. Running Microsoft Update will display the patches necessary for SQL.
Creating a Windows Firewall Port Exception for SQL Server
The Windows firewall is highly recommended for security reasons, and it is not recommended to simply turn it off. By default, however, to get SQL services to run, you must create a manual Windows firewall port rule that enables port 1433, the SQL port, to be open on the server, as shown in Figure 3.5. If this port is not open, SharePoint cannot connect to the SQL server if it is installed on a separate server from the SharePoint server.
Figure 3.5 Creating a SQL port exception for the Windows firewall.
Enabling TCP/IP in SQL Configuration Manager
By default, some SQL Server installations do not have TCP/IP enabled for remote access. This is required for use by a remote SharePoint server. To enable TCP/IP, simply open SQL Server Configuration Manager (Start, All Programs, Microsoft SQL Server 2008 R2 – Configuration Tools, SQL Server Configuration Manager) and navigate to SQL Server Network Configuration, Protocols for <INSTANCENAME>. Change the TCP/IP to Enabled, as shown in Figure 3.6. If this is not done, SharePoint cannot connect to the SQL Server.
Figure 3.6 Enabling TCP/IP support in SQL Configuration Manager.