Tuning SQL Server for SharePoint Jump StartBill Baer | Senior Product Marketing Manager, MicrosoftBrian Alderman | Chief Executive Officer | MicroTechPoint

Course TopicsTuning SQL Server 2012 for SharePoint 2013 Jump Start01 | Key SQL Server and SharePoint Server Integration Concepts (50

minutes) Dedicated Server or Instance; SQL Database & database files; ldf to mdf checkpoint process; Recovery

model (Simple vs. Full)

02 | Best Practices: SQL Server Database Settings (50 minutes)Model Database; TempDB (Location); Initial size, Autogrowth, and Collation; Recovery model

03 | Server Settings for SQL Server (50 minutes)Default Database File Locations; Memory Settings; MAXDOP

04 | SQL Server and SharePoint Availability (50 minutes)Avoiding large log files; Backups and Location of Backups; SQL Server 2012 AlwaysOn; Best Practices

Module Agenda

• Model & Tempdb Database Settings• Database File Placement • Determining Number of Content Databases

Model & Tempdb Database Settings

Model System Database Settings

• Increase Initial Size Setting• Increase Autogrowth Settings (Use MB Not %)• Cannot Modify Collation on Model DB • Use Full Recovery Model

Full Recovery Model

.LDF

Data

Data

.MDFAdd

Content

Content Database Located on Hard Drive

Checkpoint

Data

Data

Full Recovery Model (Recommended)

Simple Recovery Model

.MDF .LDFAdd

Content

Content Database Located on Hard Drive

Checkpoint

Data

Data

Simple Recovery Model

Tempdb System Database Settings• Configure Tempdb Data Files = No of Proc. Cores• Configure Tempdb Size

−At Least 10% of Total Content DB’s Size or −Size of Largest Table - Whichever Greater

• Tempdb Database Settings−Increase Initial Size Setting−Increase Autogrowth Settings (Use MB Not %)−Use Simple Recovery Model−Place on Different Drive Than Content Databases

DEMOModifying Model DB SettingsCreating Additional Databases

Database File Placement Determining Number of Databases

Recommended Database File Placement• Priority (Fastest to Slowest Drive)

−Tempdb Data and Transaction Log Files−DataBase Transaction Log Files−Search Database Data Files−Content Database Data Files

• Use Multiple Data Files for Content and Search DB’s−Distribute Equally-Sized Data Files Across Separate Disks−Number of Data Files Should Be <= Number of Processor Cores−Multiple Data Files Not Supported for Other DBs

Planning Site Collections and DatabasesNeed 800 Site Collections at 500MB Each

250 250 250 250

Site Collection Site Collection Site Collection

200GB 200GB 200GB

200GB

HRSites

ProjectsSites

SalesSites

StudentSites

Web Application

Site Collection

DEMOConfiguring Content Databases

Summary

• Modify Model Database to Reflect Configuration of New Databases

• Configure Tempdb for Improve Performance• Place Database Files on Recommended Drives• Control Size of Databases Using Quota

Templates and Maximum Site Collection per Database Setting

©2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Office, Azure, System Center, Dynamics and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.