SlideServe
Menu
Préférences
© SlideServe · v2026

Tuning SQL Server for SharePoint Jump Start

lamont avatar
14 diapositives · 402 Views · Jul 26, 2014

Tuning SQL Server for SharePoint Jump Start. Bill Baer | Senior Product Marketing Manager, Microsoft Brian Alderman | Chief Executive Officer | MicroTechPoint. Course Topics. Module Agenda. Avoiding Large T-Log Files Backups; Location, Location, Location Enable SQL Server AlwaysOn

Tuning SQL Server for SharePoint Jump Start - slide 1
01 / 14Tuning SQL Server for SharePoint Jump Start
1 / 17

Télécharger la présentation

Tuning SQL Server for SharePoint Jump Start
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation
  1. Tuning SQL Server for SharePoint Jump Start Bill Baer | Senior Product Marketing Manager, Microsoft Brian Alderman | Chief Executive Officer | MicroTechPoint

  2. Course Topics

  3. Module Agenda • Avoiding Large T-Log Files • Backups; Location, Location, Location • Enable SQL Server AlwaysOn • Verify Integrity of Databases • SQL Server for SharePoint Best Practices

  4. Simple Recovery Model Content Database Located on Hard Drive .MDF .LDF Data Add Content Checkpoint Data Simple Recovery Model

  5. Full Recovery Model Content Database Located on Hard Drive .MDF .LDF Data Data Add Content Checkpoint Data Data Full Recovery Model (Recommended)

  6. Preventing Ginormous T-Logs Tuesday Wednesday Sunday Monday .ldf .ldf .ldf .mdf .ldf .mdf .mdf .mdf Differential Full Backup Differential Differential (3) (2) Backup Log DB_Nameto D:\SQLBackups\Weekly_T_Log.Bak with INIT Backup Log DB_Nameto D:\SQLBackups\TempBackup.Bak (1) (4) .ldf .mdf Lose .mdf file of database on Thursday at 4:00pm

  7. Backups; Location, Location, Location • Local Copy for Quick Recovery • Same Room, Same Floor, Same Building, Same City? • Remote Copy for Large Disasters • Same County, Same State, Same Geographical Location?

  8. SQL Server 2012 AlwaysOn • Requires Windows Server Failover Clustering • Builds on SQL Server Mirroring • Not a Replacement for Database Backups • Components • Availability Groups • Availability Databases • Availability Replicas • Availability Modes • Failover Types

  9. Verify Integrity of Databases • DBCC CheckDB • Check REPAIR_REBUILD Option to Fix Errors (Not Always Possible) • REPAIR_ALLOW_DATA_LOSS Not Supported • Time Consuming Operation, Run During Non-Peak Hours • For Very Large DBs consider using option MAXDOP=1

  10. SQL Server for SharePoint Best Practices

  11. SQL Server for SharePoint Best Practices • Dedicated SQL Server / Instance • Modify Tempdb and Model System Database Settings • Create Multiple TempDB Files on Multiple Disks • Spread Data Files and Transaction Log Files Across Multiple Physical Drives or Locate on RAID 5/10 • Use Database Autogrowth Sparingly (Insurance Policy) • Reduces Fragmentation • Improves Performance

  12. SQL Server for SharePoint Best Practices • Create SQL Server alias • Content Databases < 200 GB • Avoid shrinking database files • Check database integrity with DBCC CHECKDB • Monitor disk seconds per read/write (<20ms) • Defragment SQL Server drives containing content database files • Perform regular backups of database and transaction logs

  13. Summary • Avoid Ginormous T-Logs by Performing Regular T-Log Backups • Have Multiple Copies of Your Backups • Configure AlwaysOn for High Availability • Verify Integrity of SQL Server Databases • SQL Server for SharePoint Best Practices