What SQL DBAs need to know about SharePoint
Download as PPTX, PDF5 likes6,820 views
This document discusses what SQL DBAs need to know about implementing and managing SharePoint databases. It covers topics such as the SQL implementation challenges in SharePoint, recommended database configuration including storage, sizing, and high availability options. It also discusses maintenance best practices for SharePoint databases such as monitoring, integrity checks, index maintenance and shrinking databases. Upcoming enhancements in SharePoint 2010 that improve SQL integration are also mentioned.
Ad
More Related Content
What's hot (20)
Similar to What SQL DBAs need to know about SharePoint (20)
Ad
More from J.D. Wade (20)
Ad
Recently uploaded (20)
What SQL DBAs need to know about SharePoint
- 1. What SQL DBAs need to know about SharePointJD Wade, MCITPSharePoint ConsultantHorizons ConsultingTwitter: http://twitter.com/jdwadeBlog: http://wadingthrough.com
- 2. Why, oh why, oh why?
- 3. Single Platform – Power and Challenge!CorporateWebPresenceSingle Business Productivity Platform leading to common: End-user Experience
- 4. Rich Integrated Capabilities
- 5. Toolset and Development
- 6. Deployment and ManagementEmployeePortalKnowledgeManagementPortalRegulatoryComplianceRepositoryUsersSalesDivisionPortalCustomSAPFront-EndBusinessIntelligenceDashboardR&DCommunityGenevaOfficeSiteExtranetCollabSiteTeam “ABC”SiteProject“X” SiteWeekly IssueTrackingMeetingCorporateTeamsDepartmentsEmpowerment
- 7. SQL ImplementationCommonly Perceived GapsSharePoint tables are too wide, wraps rowsSharePoint manages its own (NVP) indexesSharePoint adds force-order, query hintsMissing indexes for common operationsExcessive use of Dynamic queriesNo SQL Referential Integrity OR key constraintsDBCC with data loss not supportedMissing integration of Back-up/Restore
- 8. Why are DB Changes Not Supported?Single data platform for all workloadsWorkloads with conflicting platform needsChange for one may adversely affect anotherUpgrade and Servicing expects solid DB contractApp logic is heavily dependent on DB specificsApp enforces constraints and integrity!Mostly Read
- 10. Search and structured queriesCorpWebPresenceUsersRead Writes
- 11. Office Documents
- 12. Organization and ad-hoc queriesTeam Collab SiteEmpowerment
- 13. Storage
- 14. Storage5 Key Points to Consider…App ServerApp ServerApp ServerSQL Server1HBAHBA2345tempdb tempdb T-logDB T-logsContent DBsSearch DB
- 15. StorageOptimizing SQL Server I/O SubsystemEnsure correct HBA driver and firmware versionsUse SQLIO.exe to measure I/O performanceConfigure correct NTFS Allocation Unit Size64K best; default (4K) can result in a 30% perf hitTo view: chkdsk <drive_letter>Ensure correct Windows “Sector Alignment”Incorrect setting can result in up to 50% perf hitUse diskpart to check and set alignment64K most common. Windows 2008 aligns sectors by defaultFree space on NTFS partition should be > 25%
- 16. StorageDatabase ConfigurationRecommended database file placement priority (fastest to slowest drive)tempdb data and t-log filesDb transaction log filesSearch db data filesContent db data filesIn a heavily read-oriented portal site, prioritize data over logs.Place tempdb, Content db and t-logs on separate LUNsUse multiple data files for Content and Search dbsDistribute equi-sized data files across separate disks# of data files should be <= # of processor coresMultiple data files are not supported for other dbsPlace SharePoint Search crawl and query processing tables on separate spindles
- 17. StorageDatabase SizingSite Collections > 15GB, use SQL BackupsLimit Content DBs to 100 GB (soft limit)If larger consider differential backups using SQL or DPMSize SQL Server data files appropriatelyPre-allocate data file to cover anticipated size of Content dbRely on SQL ‘Autogrow’ only as a catastrophic insurance policySet SQL ‘Autogrow’ to fixed value appropriate for size of dbUse dedicated database for large Site Collections (> 50GB)Configure tempdb data files = No of proc coresConfigure tempdb to be at least 10% (25% preferred) of total Content db size, or the size of the largest table - whichever is greater
- 18. Configuration
- 21. ConfigurationProcessorsDeploy on 64-bit, especially if >1000 users, or >100 GB of dataUse 64-bit SQL Server if using 64-bit OSIA-64 only supported on db tier, not on app tier
- 22. Configuration MemorySet ‘Max Server Memory’SQL Max Memory = TotalPhyMem - (NumOfSQLThreads * ThreadStackSize) - (1GB * CEILING(NumOfCores/4)) - (Any mem required for ‘other’ apps) NumOfSQLThreads = 256 + (NumOfProcessors*- 4) * 8 ThreadStackSize = 1 MB on x86 2 MB on 64-bit (x64) 4 MB on 64-bit (IA64)On 64-bit use LPiM privilege for SQL Server accountIf using SQL Std edition need following CU + trace flagCU2 for SQL Server 2008 SP1 (KBA 970315)CU4 for SQL Server 2005 SP3 (KBA 970279)* If NumOfProcessors > 4, else 0.
- 23. ConfigurationUse SQL Server connection aliasSimplifies redirecting WFEs to a different dbinstanceDo not modify SPT schemaNo new columns or indexes permittedUse SharePoint tools to index columns
- 24. ConfigurationTest use of MAXDOP = 1Separate instance for SharePoint DatabasesSet Fill Factor to 70SharePoint ignores Model Autogrow settings
- 25. Maintenance
- 26. MaintenanceMonitor SQL Server performance regularlyCheck integrity of the database routinelyDBCC CHECKDBCan use REPAIR_REBUILD option to fix errors (not always possible)REPAIR_ALLOW_DATA_LOSS not supportedTime consuming operation, run during non-peak hoursFor very large DBs consider using option MAXDOP=1Defragment physical filesMaintain farm account as DBO for moves/restores
- 27. MaintenanceFragmentationContent and Search dbs most susceptibleRebuild / Reorganize indexes to eliminate fragmentationReorganize index when fragmentation between 10-70%Rebuild index when fragmentation > 70%Existing index options used before the rebuild operation are not restored. Issue resolved in SQL Server 2005 SP2 and higherUse sys.dm_db_index_physical_stats to measureMore accurate than DBCC SHOWCONTIG, often reports higher fragmentation numbersAuto-defrag only available in MOSS 2007 SP2 and for Content dbs but may need manual defragmentationDatabase Maintenance for SharePoint white paper
- 28. MaintenanceShrinking Database SizeOnly shrink Content databases, not othersOnly perform if free space > 50% (after content reorg)Do not perform as part of maintenance planAllocate 10-20% growth allowance when determining target size
- 29. High AvailabilityHigh availability options supported:Failover Clustering (local & stretch clusters)Database mirroring (Sync & Async)Log Shipping often used in conjunction to provide disaster recovery
- 30. High AvailabilityDatabase Mirroring ConfigurationsDB Mirroring within farm(Synchronous)DB Mirroring across farms(Asynchronous)
- 31. High AvailabilityDatabase MirroringNeeds to be individually configured for each SPT dbRequires Full Recovery modelBoth Synchronous and Asynchronous modes supportedSynchronous DBM mode with witness server recommended for high availabilityTransfer SPT logins from Primary to Mirror serverScript available in KBA 918992DB Mirroring SQL end-points should be encrypted when channel is not secured by other means
- 32. High AvailabilityDatabase MirroringOnly supported on SQL Server Standard and Enterprise editionsStandard edition only supports Synchronous mirroringOn Standard edition 1 redo thread per db; on enterprise edition 1 redo thread per db per 4 coresWitness server can run on SQL ExpressSeveral improvements in SQL Server 2008 DBMLog stream compressionAutomatic Page RepairPending send buffers limit increased from 3 to 64
- 33. High AvailabilityAsynchronous MirroringAsynchronous DBM can be used to provide redundancy for Content dbs across farmsDoes not guarantee consistencyDBs that cannot be Async mirroredConfiguration & Central Admin Content dbsContain location specific references, must be rebuild at mirror siteSSP dbs only if using SearchSearch requires sync between SSP dbs, Search db, and index (index file cannot be mirrored)
- 35. SQL 2008 R2SharePoint IntegrationImproved Reporting Services in SharePoint integrated modeEasier installExtract data from SharePoint 2007 or 2010 listsSSRS is reporting engine for SharePoint Access Services reportingPowerPivot for SharePoint“SSAS in SharePoint integrated mode”
- 36. SharePoint 2010Support for RBS using SQL FilestreamRestore items directly from SQL databaseAvePoint add-onSupport for SQL Mirroring built-inAccess ServicesPerformancePoint built-in
- 37. Q & A
- 38. SourcesPrimary slide content with modifications from:SharePoint Conference 2009SPC319: SQL Server Best Practices for SharePoint DeploymentsBurzinPatel, Senior Program ManagerMicrosoft CorporationDatabase Maintenance for SharePoint white paperhttp://technet.microsoft.com/en-us/library/cc262731.aspx