Date post: | 30-Dec-2015 |
Category: |
Documents |
Upload: | august-wright |
View: | 225 times |
Download: | 1 times |
What SharePoint AdminsShould Know About SQL Server
Victor IsakovDatabase Architect / Trainer
Interactive Theatre
AIT005
Victor IsakovDatabase Architect / Trainer
Interactive Theatre
Victor Isakov
Database Architect | Trainer
[email protected]@victorisakovwww.linkedin.com/in/victorisakov
SQL Server Solutionswww.sqlserversolutions.com.au
Email:Blog:Twitter: LinkedIn:
Victor Isakov
Victor Isakov is a Database Architect / Trainer who enjoys a reputation of being one of the most knowledgeable subject matter experts on SQL Server and related technology. Victor has provided consulting and training services around the world for over 15 years. Victor Isakov has authored a number of books on SQL Server and worked with Microsoft to develop the SQL Server exams and certification.
SQL Server / Business Intelligence / SharePoint TrainingSQL Server / Business Intelligence / SharePoint ConsultingPerformance Tuning / TroubleshootingSQL Server Infrastructure Reviews (“Health-checks”)Solution Architecture Design / Review
Abstract
The performance, reliability and availability of your SharePoint farm depends on SQL Server. Therefore it is important for SharePoint Administrators to understand how to best configure and administer the SQL Server instances used by SharePoint. In this session Victor Isakov (MCA, MCM, MCT, MVP) will present on what SharePoint Admins should know about SQL Server so that they can maximize performance, minimize data loss and correctly administer SQL Server within their SharePoint farm.
Reliability
Database Recovery ModelsDatabase Consistency Checks
BTW: Don’t perform database backups to same disk where database is located…
Database Recovery Models
SIMPLEFULLBULK LOGGED
Make sure you understand associated risk!Importance
Impacts Backup StrategyImpacts Disk Capacity Planning
Assess the SharePoint database(s) default recovery model
Database Consistency Checks
DBCC CHECKDBChecks the logical & physical integrity of all database objectsNo need to run CHECKALLOC, CHECKCATALOG, CHECKTABLE
OptionsPHYSICAL_ONLYDATA_PURITY
Repair options are last resortREPAIR_REBUILDREPAIR_ALLOW_DATA_LOSS
Hardware Considerations
CPUsProcessor subsystem will NOT be the bottleneck in most systemsSQL Server 2012 is licensed by cores
MemoryKey to performance in SQL Server
StorageTier 1 / Tier 2 / Tier 3Capacity planning storage is key
SQL Server Configuration
sp_configureMaximum Degree of Parallelism
MAXDOP = 1
Max Server MemoryMin Server Memory
Encourage you to deploy a standard build/ Standard Operating Environment (SOE)
SQL Server Services
Auto restart SQL ServerAuto restart SQL Server Agent
Ensure that the SQL Server Agent service starts automatically
SQL Server Agent Mail
Enable email integrationAbility to be notified when SQL Server Agent jobs succeed / fail / complete
Database Configuration
Recovery ModelFile Placement
Content Databases are key for most deploymentsAll documents are serialized through transaction logHave a strategy around the number of content databases
Relationship between Document Libraries / Site Collections
File Placement
Place transaction logs on separate LUNsPerformanceRecoverability
Place SharePoint databases on separate disk subsystems
ContentSearch
What is RBS?
SQL RBS Client Library
Provider Library X
BLOB Store X
Relational Access
• A down-loadable, add-in component that can be registered for a SharePoint farm
• Store for all BLOBs added to the content DBs where the Provider is set Active
• Customers can choose BLOB store Providers
Provider Library Y
Provider Library Z
BLOB Store Y
BLOB Store Z
RBS Maintainer
Provider Library
Provider API
SharePoint Object Model
ContentDatabase
SQL Server
ConfigDatabase
Remote BLOB Storage (RBS) Victor Isakov
A Typical RBS Workflow – Save document
SharePoint Web FE
SharePoint Object Model
Relational Access
1. Save Request
3. Save BLOB
4. Write BLOB
5. Return BLOB Id
6. Save Metadata & BLOB ID
7. Back to User
BLOB Store
ContentDatabase
SQL Server
ConfigDatabase
2. Enforce Biz Logic
BLOB Store Provider Library
RBS Client Library
Remote BLOB Storage (RBS) Victor Isakov
A Typical RBS Workflow – Read document
SharePoint Web FE
SharePoint Object Model
Relational Access
1. Open Document
4. Read BLOB
5. Read BLOB
6. Return BLOB
3. Get BLOB Id
7. BLOB Data to User
BLOB Store
ContentDatabase
SQL Server
ConfigDatabase
2. Enforce Biz Logic
BLOB Store Provider Library
RBS Client Library
Remote BLOB Storage (RBS) Victor Isakov
Availability
Disaster Recovery IS NOT High AvailabilitySQL Server Options
ClusteringLog ShippingDatabase MirroringAvailability Groups
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.