Best Practices in SharePoint Deployment and Management

1
(No Transcript)
2
Best Practices in SharePointDeployment and
Management

• Presented by
• JD Wade, SharePoint Consultant, MCTSHorizons
  Consulting, Inc.
• Mail jd.wade_at_hrizns.com
• Blog http//www.wadingthrough.com
• Twitter http//twitter.com/JDWade

3
Agenda
Infrastructure
Governance
Development
4
Infrastructure
5
Maintain as a Platform

• More than an Application
• Patch/Update more than SharePoint
• Patch Regularly At least Quarterly
• Fixes Problems Before They Occur
• Prepares For Cases That Are Opened
• Users Latency is Effected by Multiple Components

6
Server Configuration

• Disable Loopback Check Security Feature on
  SharePoint servers(MS KB 896861 Two Methods to
  Disable)
• IIS Thread Patch (MS KB 946517)
• .Net Framework 3.5 SP1
• 64 Bit
• OS Partition (30GB-32 bit, 40GB-64 bit)
• Ensure 25 free space on NTFS partitions
• PowerShell 1.0
• Gigabit Ethernet Connections

7
SharePoint Software

• Updated to Service Pack 2
• June 2009 Cumulative Update preferred(August
  soon)
• Use Cumulative Update Server-Packages
• Use Multiple Service Accounts
• Know When to Use Kerberos

8
SharePoint Backups

• Test Recovery
• Set Service Level Agreements (RTO, RPO)
• Backup SharePoint as prescribed

9
SQL Server

• Lifeblood of SharePoint Farm
• Cluster to Ensure Availability
• Use SQL Aliases
• Pre-size and pre-construct files
• Watch Auto Growth settings
• Simple versus Full Backups
• Defragment data files

10
SQL Server Storage

• RAID 10 provides better throughput than RAID 5
• Separate databases and logs onto separate
  spindles to scale up
• Sector Align Disk Partitions
• Format data and log file LUNs to 64KB allocation
  units
• Database files need random read and write
  optimization
• Log files need sequential read and write
  optimization
• Heavy read only environments should focus on
  database files

11
SQL Server TempDB

• Ensure adequate throughput use separate
  spindles
• Size database to 25 of largest database in the
  instance
• Divide into equal data files based on of cores
  in SQL Server

12
SQL Server Priorities

• TempDB
• Database Log Files
• Search Databases
• Content Databases

13
Governance
14
Governance

• Unique to Every Organization
• Balance IT Control with User Empowerment
• Get Executive Sponsorship
• Adoption is What Counts
• Establish an Information Architecture
• Setup Structure with Most Important Items at the
  Top
• Establish Roles and Responsibilities
• Loosen Rules as There is More collaboration

15
Collaboration Sizing

• 15GB Maximum Site Collections
• 100GB Content Databases for effective performance
  (25GB if effective)
• Expect file server data to grow 1.2x - 1.5x going
  into SharePoint
• Ensure Information Architecture has multiple site
  collections
• For larger deployments
• One site collection per content database
• Break content database into multiple data files
  equal to of cores in SQL Server
• Put data files onto separate spindles for every
  more performance

16
Development
17
Development

• Use Solutions
• Do Not Use Site Templates (STP)
• Decide between GAC and BIN
• Use Data Connectors and SSO Database
• Determine Customization Tools (Designer is Free
  Now)
• Choose Versioning Methods Early
• Use Source Control
• Use Multiple Environments
• Procedure/Tool for Moving Solutions Between
  Environments
• Keep Environments Alike
• Create Virtual and Automated Developer Instances

18
Code
Staging
Dev
Production
Content
19
Appendix

• Governance Resource Center for SharePointhttp//t
  echnet.microsoft.com/en-us/office/sharepointserver
  /bb507202.aspx
• Database Maintenance for SharePoint
  Whitepaperhttp//technet.microsoft.com/en-us/libr
  ary/cc262731.aspx
• Working with TempDB in SQL Server
  2005http//technet.microsoft.com/en-us/library/cc
  966545.aspx

20
Questions?

• Presented by
• JD Wade, SharePoint Consultant, MCTSHorizons
  Consulting, Inc.
• Mail jd.wade_at_hrizns.com
• Blog http//www.wadingthrough.com
• Twitter http//twitter.com/JDWade

21
(No Transcript)