␡
- Understanding the SharePoint Server Roles
- Understanding the Reasons for Deploying Multiple Farms
- Choosing the Right Hardware for SharePoint
- Determining Optimal Operating System Configuration
- Planning for Database and Additional Software
- Examining Real-World SharePoint 2013 Deployments
- Addressing Common Business Issues with SharePoint Features
- Deploying a Team Collaboration Solution with SharePoint
- Deploying a Corporate Intranet Solution with SharePoint
- Deploying a Customer Extranet Solution with SharePoint
- Summary
- Best Practices
< Back
Page 12 of 12
This chapter is from the book
This chapter is from the book
This chapter is from the book
This chapter is from the book
Best Practices
The following are best practices from this chapter:
- Become familiar with SharePoint 2013 design terminology, particularly in how it relates to service application architecture.
- Use the latest version of SQL Server, SQL Server 2012, whenever possible, particularly to take advantage of features such as SQL AlwaysOn, Transparent Data Encryption, and PowerPivot.
- Consider separating the service application roles from the web role servers to improve performance.
- Separate the database role from the SharePoint roles whenever possible to improve performance.
- Take an in-depth look at virtualization technologies, at a minimum for development and test farms, and potentially for production farms.
- Consider best-practice security approaches such as SQL Server TDE for storage security, IPsec and Secure Sockets Layer (SSL) certificates for transport security, and Active Directory Rights Management Services (AD RMS) for data loss prevention.
- Consider database mirroring for the content databases to provide for both high availability and disaster recovery of SharePoint content.
- Remember to purchase and install any necessary third-party web parts, iFilters, backup, and antivirus software, or use some of the Microsoft offerings such as System Center DPM 2013.
- Allocate a significant amount of memory and processor cores to SharePoint servers because they are resource intensive. SharePoint 2013’s resource requirements are much higher than in earlier versions of SharePoint. Start with 12GB RAM and two CPUs for a simple web server.
- Be sure to allocate enough hard drive space for the Search service application roles for the index corpus; allocate 5% to 30% of the size of the data being indexed.
- Use SQL AlwaysOn technologies and network load balancing to scale the SharePoint server environment and provide redundancy.
< Back
Page 12 of 12