SharePoint Best Practices. Presented By: Mark Weinstein

Transcription

1 SharePoint Best Practices Presented By: Mark Weinstein

2 Installing SharePoint 32 or 64 bit? Which SharePoint version? WSS or MOSS? When installing SharePoint, be sure to select the Advanced method of installation instead of Basic Create and use separate service accounts for SharePoint and it s services

3 Web Server Requirements Component Processor Memory Disk Network Platform Software Requirements Minimum processor speed of 2.5GHz required. Dual processors with speeds of at least 3GHz recommended. 64 bit processors optional but highly recommended. Minimum 1GB of RAM required. 4GB or more RAM recommended. Minimum 3GB of free disk space required. File system must be NTFS formatted. Minimum 100 Mbps server server connections required. 1Gbps server server connections highly recommended. Windows Server 2003 operating system required. Service Pack 1 (SP1) or later required. IIS 6.0 must be enabled. Microsoft.NET Framework 3.0 must be installed. ASP.NET 2.0 must be enabled.

4 Database Server Requirements Component Processor Memory Disk Network Platform Software Requirements Minimum processor speed of 2.5GHz required. Dual processors with speeds of at least 3GHz recommended. 64 bit processors optional but recommended. Minimum 2GB of RAM required. Minimum 4GB of RAM recommended. Calculate required disk space as 120% of planned content capacity, excluding any additional space required for your RAID configuration. Minimum 100 Mbps server server connections required. 1Gbps server server connections recommended. Windows Server 2003 operating system required. Service Pack 1 (SP1) or later required. Microsoft SQL Server 2000 (SP3a or later) required. Microsoft SQL Server 2005 (SP1 or later) recommended.

5 WSS Server Roles Web Front End Servers Database Servers Search Servers SharePoint Server Roles Index Servers Query Servers Application Servers

6 Application Server Requirements The minimum hardware requirements for an application server are identical to those for a front end Web server. However, you should be aware that different application server roles place different demands on your server farm infrastructure. The following list describes some of these demands: The index server role is highly processor intensive. The disk hardware should be optimized for writing, and a RAID 10 disk configuration is recommended for the optimal combination of fast write speed and disk redundancy. The query server role is memory intensive, as the server will load as much of the index as possible into memory. The disk hardware should be optimized for fast I/O times on disk read operations.

7 Application Server Requirements Excel Services is processor intensive and potentially memory intensive depending upon your Excel Services caching configuration and usage. The Business Data Catalog creates demand on the processor, memory, and network when accessing LOB systems. Based on how your organization deploys and uses the Business Data Catalog, you may need hardware above the minimum recommended requirements.

8 Top Sites, Subsites, and Site Collections

9 Best Practices for Sites Limit the number of levels for sites Consolidate related data to sites within the same site collection Consider a 3 or 4 click rule. If it takes more than 3 or 4 clicks to get to your data, it may be buried too deep

10 Storage Considerations Remember: EVERYTHING in SharePoint is stored in your SQL database! Data in SharePoint has a 20% overhead. Example: 1Mb file = 1.2Mb file in SharePoint Double disk space is required in order to defragment and optimize databases as well as recover databases in the event of a disaster.

11 Defining a Permissions Model When defining a permissions model for your project, there are several things to consider: Who needs access to the site? Should functionality be limited to different types of users? Will you limit access at the site or the data level? Should you use inherited or unique permissions?

12 The Permissions Hierarchy SharePoint Users/Groups Permissions Levels Individual Permissions

13 Security and Permission Considerations If possible, set permissions high in your site hierarchy to take advantage of inheritance. When needed, break security permissions as low in your site hierarchy as possible. Whenever possible, use Active Directory security groups to simplify SharePoint administration.

14 List and Library Considerations If possible, avoid using folders in libraries Determine whether your list or library requires version control. If not, disable it. Limit views of list items and files to <2000 items at a time to prevent slowdown. Set unique permissions for lists and libraries if necessary, otherwise, they will inherit permissions by default.

15 PLAN! PLAN! PLAN! There is no substitute for proper planning! Design a hierarchy that supports growth. Use a security model that is easy to maintain. Limit the ability for users to create sites and subsites and delegate these responsibilities to supervisors and department heads. Remember, SharePoint will grow like a weed if you let it! If necessary, you can use quotas to keep database sizes reasonable.

16 SharePoint Best Practice Analyzer The Microsoft Best Practices Analyzer for SharePoint creates detailed reports to help administrators achieve greater performance, scalability, and uptime. s.aspx?familyid=cb944b27 9d6b 4a1f b3e1 778efda07df8&displaylang=en

17 Thank You! We will begin the Q&A momentarily