Export (0) Print
Expand All

Phase 3: Configure SQL Server Infrastructure

Updated: April 23, 2014

[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]

This is the third phase of deploying SharePoint with SQL Server AlwaysOn in Azure, which includes configuring the two SQL Server computers. You must complete this phase before moving on to Phase 4.

For the previous phase, see Phase 2: Configure Domain Controllers.

For the next phase, see Phase 4: Configure SharePoint Servers.

For all of the phases of this deployment, see Deploying SharePoint with SQL Server AlwaysOn in Azure.

This deployment of SharePoint with SQL Server AlwaysOn is designed to accompany the SharePoint with SQL Server AlwaysOn Infographic and incorporate the latest recommendations.

Configure a Virtual Machine with SQL Server 2012

This procedure is executed on both virtual machines that host SQL Server. One VM contains the primary database replica of an availability group. The second VM contains the secondary backup replica. The backup is provided to ensure high-availability.

By default, only the user account that was created with the Virtual Machine (in the Azure Management portal) can access the SQL Server default instance. But the Virtual Machine must be joined to the domain in order to add a domain user account to the list of log ins. Therefore, you must first join the machine to the domain, then log on as the original user in order to access the SQL Server instance.

  1. From the Azure Management portal, attach a 50-GB empty disk to the VM that hosts SQL Server. For more information, see Creating and Attaching and Empty Disks to a Virtual Machine.

  2. Connect to the VM using the user name and password created with the machine. Use the format <machineName>\<username>. By default, the user is a member of the Administrators group. For more information, see Connecting to a VM after its creation.

  3. Use the Disk Management tool to partition the disk and assign it the letter F:.

  4. On the new partition, create three folders named Data, Log, and Backup.

  5. Join the VM to the domain. For instructions, see Joining a Virtual Machine to a domain.

    When prompted for a user that has permission to join the domain, specify a member of the Domain Admins group, such as sp_install. Use the format: sp_install@<domainName>.com.

  6. Restart the machine to complete the join.

  7. Connect to the VM using the user name and password created with the machine. Use the format: <machineName>.clouapp.net\<username>. (At this point, only the user created with the machine has permission to log onto the SQL Server instance.)

  8. On the Start menu, type SQL Server Management Studio and open the tool.

  9. Connect to the SQL Server default instance using the Windows account.

  10. Right-click the top node—the default instance named after the machine—and click Properties.

  11. In the Server Properties window, click Database Settings.

  12. Locate the Database default locations and set the values for Data, Log, and Backup to the newly created folders. Only new databases use these locations.

  13. Click the OK to close the window.

  14. In the left pane, expand the Security folder.

  15. Right-click Logins, then click New login.

  16. In the Login-New dialog, type sp_farm_db. Use the format: sp_farm_db@<domainName>.com

  17. After the name resolves, click OK to close the dialog.

  18. In the left pane, click Server Roles, and select the checkbox for Sysadmin role. Click OK to close the dialog.

  19. Right-click Logins and click New Login.

  20. In the Login name box, type NT Authority\System and click OK.

  21. In Object Explorer, right-click NT AUTHORITY\System and click Properties.

  22. In the Securables page, for the local server, select Grant for the following permissions and click OK.

    • Alter any availability group

    • Connect SQL

    • View server state

  23. Click OK and close the SQL Server Management Studio.

  24. SQL Server requires a port that clients use to access the database server. It also needs a port to manage the high-availability group. By default, the client port number is 1433, and the high availability port is 5022. The Windows Firewall, however, blocks both ports. To open the ports:

    1. In the Start menu, type Windows firewall with advanced security.

    2. Click Inbound Rules.

    3. On the Action pane, click New Rule.

    4. On the Rule Type page, select Program, and click Next.

    5. In the Program page, select This program path and type C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Binn\sqlservr.exe in the text box. Then, click Next.

    6. On the Action page, keep the default ("Allow the connection") and click Next.

    7. On the Profile page, accept the defaults, and click Next.

    8. On the Name page, type SQL Server ports 1433 and 5022, and click Finish.

    For more information, see Configure a Windows Firewall for Database Engine Access

Next Steps

For the next phase of the deployment, see Phase 4: Configure SharePoint Servers.

For all of the phases of this deployment, see Deploying SharePoint with SQL Server AlwaysOn in Azure.

See Also

Community Additions

© 2014 Microsoft