Upload
lars-platzdasch
View
1.070
Download
0
Embed Size (px)
Citation preview
Sprecher:
Lars Platzdasch
LarsPlatzdasch
/Lars_Platzdasch
Larsplatzdasch
Web
www.platzdasch.de
www.3perspektiven.de
Microsoft Certified Solutions Expert: SQL Server Data Platform
Microsoft Certified Solutions Expert: SharePoint
Microsoft Certified IT Professional: SharePoint 2010, Administrator
Microsoft Certified IT Professional: SharePoint 2010, Developer
Microsoft Certified Application Developer: .NET
platzdasch netConsult GmbH & Co. KG | ISV
24/7 Support für SQL / SharePoint
3 Perspektiven GmbH | MBS
20 IT, 18 Jahre SQL Server, 13 Jahre SharePoint
ACHTUNG:
FALLS JEMAND ETWASNACH LESEN MÖCHTE
Hat du Kopp wie Sieb, muttu
auf schreiben ! ( oder … ) Slides sind auf http://www.slideshare.net/larspl , Sway
Konferenz Webseite
( ist voll kommen OK .. ( es ist auch schon 16:15 ++ ;-)
Überblick, Roadmap
SQL Server Konfiguration
SharePoint / SQL Server Basics
SharePoint Topologie
Bereitstellen
AGENDA
2001
SharePoint
Portal Server 2001
2003
SharePoint
Portal Server 2003
2006
Office SharePoint
Server 2007
2009
SharePoint
Server 2010
2012
SharePoint
Server 2013
2016
SharePoint
Server 2016
Cloud-Inspired
Experiences
Cloud and Enterprise
Social
Content
Management
Core
Collaboration
Microsoft
Managed Solutions
Microsoft
Online Services (BPOS)
Office 365
SHAREPOINT RELEASE HISTORY UND ROADMAP
Office 365
Content DB Size
• TB-sized Databases
now Officially
Supported
Site Collections per Content DB
• 100,000 Site
Collections per
Content Databases
List Threshold
• Increased List
Threshold >5000
Items
• No word yet on how
many more…
Max File Size
• Maximum File Size
now 10GB
• No Character
Restrictions – Drag
& Drop files with ‘&’
in them!!!
Indexed Items
• Search scale
doubled to 500
Million items
Coming in 2016…
Coming in 2016…
Coming in 2016…
Coming in 2016…
Coming in 2016…
In 2013…
• Maximum of 10 Million Indexed items per search partition…
In 2013…
• Max 200GB Databases supported in General usage scenarios*
In 2013…
• Max 5000 Site Collections per Content DB
In 2013…
• Maximum 5000 Items per Query
In 2013…
• Max 2GB File Size*
SHAREPOINT 2016 LIMITS NEWS
SQL SERVER KONFIGURATION: WARUM
Top Performance Bottlenecks >1200
Kundeninstallationen
2 davon > 50.000 Users
Verbraucht wurden in dieser Zeit mindestens
min. 5000 Tassen Kaffee
http://pal.codeplex.com/
SQL SERVER KONFIGURATION
SharePoint 2013\2016:
• SQL Server 2008 R2 SP1
• SQL Server 2012 (SP1 for BI)
• SQL Server 2014 SP1 (SP2013 SP1 & April CU)
• SQL Server 2016 CTP 3.1 ff
SSMS nicht auf dem
SQL Server installieren
Dedizierte Instance
SQL Service mit einemManaged Account
Keine besonderenRechte
Named Instance
\Sharepoint
SQL SERVER KONFIGURATION
Collation:
Latin1_General_CI_AS_KS_WS(Case I,Accent S,Kana S,With S, Collation verwenden
Jede CI Collation istsupported
Latin1_XXX_CI_XX
aber ist das eine GuteIdee?
Nach dem Setup keine Änderung möglich!
SQL SERVER KONFIGURATION
Service Account ( SQL Server )
TraceFlag: -T1117 ( GleichmässigerAutoGrow auf allen Files ) < (SQL2014)
TraceFlag: -T1118
( Speicherzuordnung wird optimiert{eight pages from the same extent })
( SQL 2014/2016)
Lock Pages in Memory Privileg ( local Policy )
TraceFlags :
-T845 (STD zusätzlich)
SQL SERVER KONFIGURATION
Service Account ( SQL Server )
- Instant File Initialization
Recht: (SE_MANAGE_VOLUME_NAME )
Volume Maintenance Task. By default, only Local Admins have the access to it.
Lock PageOpen Local Security Policy> Local Policies > User Rights Management and go
to the Perform
SQL SERVER KONFIGURATION
Kein Simple RecoveryMode , AusnahmeConfigDB / Ex AOAG
Disable Boost SQL Server Priority Temp DB auf 10GB
und min 4 Files verteilen, Autogrowth 1GBT-Log Backup alle
15min bis max. 24hContent DBs Pre-Size
Index Maintennance: FRAG <=30% Reorganisation, > Rebuild
SHAREPOINT SQL SERVER BASICS
95% of SharePoint content stored in SQL
Server
Farm Configuration information liegt in configuration db
Central Administration content liegt in einereigenen content db
Fasst jede Service App hat mindest eine DB
Jede Web Applikationhat mindest eine
Content DB
Eine Farm kann durchaus >20 DBs haben
SHAREPOINT SQL SERVER BASICS: ALWAYS ON
Disaster Recovery SQL Server Solution
Potential
Data Loss
(RPO)
Potential
Recovery
Time (RTO)
Automatic
Failover
Readable
Secondaries
AlwaysOn Availability Group - synchronous-commit Zero Seconds Yes 0 - 2
AlwaysOn Availability Group - asynchronous-commit Seconds Minutes No 0 - 4
AlwaysOn Failover Cluster Instance NA Seconds
-to-minutes
Yes NA
Database Mirroring - High-safety (sync + witness) Zero Seconds Yes NA
Database Mirroring - High-performance (async) Seconds Minutes No NA
Log Shipping Minutes Minutes
-to-hours
No Not during
a restore
Backup, Copy, Restore Hours Hours
-to-days
No Not during
a restore
SHAREPOINT SQL SERVER BASICS: ALWAYS ON
-Two AGs
-Content AG with four replicas –Synch and Asynch
-User Profile Sync DBs on separate AG, 2 Synch copies only
-DR farm in remote DC on standby to connect to content DB copy
-DR copy in Azure
SHAREPOINT SQL SERVER BASICS: HA SYNCRON
Database Supported
Admin Content Yes
App Management Yes
BDC Yes
Config Yes
Content Yes
Managed Metadata Yes
PerformancePoint Yes
PowerPivot Not Tested
Project Yes
Search Analytic Reporting Yes
Search Admin Yes
Database Supported
Search Crawl Yes
Search Links Yes
Secure Store Yes
State Service Yes
Subscription Settings Yes
Translation Services Yes
UPA Profile Yes
UPA Social Yes
UPA Sync Yes
Usage(=loggingDB) Yes – NR
Word Automation Yes
SHAREPOINT SQL SERVER BASICS: HA ASYNCRON
Database Supported
Admin Content No
App Management Yes
BDC Yes
Config No
Content Yes
Managed Metadata Yes
PerformancePoint Yes
PowerPivot Not Tested*
Project Yes
Search Analytic Reporting No
Search Admin No
Database Supported
Search Crawl No
Search Links No
Secure Store Yes
State Service No
Subscription Settings Yes
Translation Services Yes
UPA Profile Yes
UPA Social Yes
UPA Sync No
Usage Yes – NR
Word Automation Yes
SP Health Analyzer
SP JOB defragmentiertdie Indexes
Job will
update statistics
AUTO_CREATE_STATISTICS OFF
SHAREPOINT SQL SERVER BASICS
SQL WartungSHAREPOINT SQL SERVER BASICS
Tgl. Full backup
15min LOG Backup
Index Reorg:
Tipp:
Ole Hallgreen ( Backup Solution )
DR Plan?
KeinDR
Plan 60%
DR Plan 40%
DEPLOYMENTS SHAREPOINT 2016
• Multiple-Server Farm• SharePoint Server mit “Front-end” Rolle
• SharePoint Server mit “Application” Rolle
• SharePoint Server mit “Distributed Cache” Rolle
• SharePoint Server mit “Search” Rolle
• SQL Server
• Single-Server Farm• SharePoint Server mit “Single” Rolle
• SQL Server
SHAREPOINT FARM SIZING
Jede Web App sollte mehr ! Alseine ContentDB
haben
Ideal: je Abteilung: IT, HR, FI etcgetrennte
ContentDBs
Backup !!! Bedenken
Quotas -> 200 -250 SCs max.
je DB
Default 2000
250 250 250
SHAREPOINT FARM SIZING
Web Application
200GB 200GB 200GB
Site Collections Site Collections Site Collections
Project
Sites
Department
Sites
250
200GB
Site Collections
HR
SitesMarketing
Sites
750mb X 250 = 187,500mb / 1024 = 183gb
250
200GB
SHAREPOINT FARM SIZING: BEREITSTELLEN
SQL ADMIN
SHAREPOINT ADMIN
SQL : DBs erzeugen, HA
erstellen
Einhängen der PreSized, HA verfügbaren
DBs
Planung
HA/DRWartung
Resources
• Script zur Prüfung neu erstellter SP C DBs’
http://sharepointszu.com/2012/02/17/sql-script-fr-die-erstellung-von-best-practice-sharepoint-datenbanken/
• SQL Server: Minimize Disk I/O
https://technet.microsoft.com/en-us/magazine/jj643251.aspx
• Best practices for SQL Server in a SharePoint Server farm
https://technet.microsoft.com/en-us/library/hh292622(v=office.15).aspx
SYSTEM KONFIGURATION: OS
System Settings:
«Best performance»
Windows Server performance options
Determine page file sizeUse the proper power
planCreate a SQL alias
Factor 1,5 des
RAMS
Sample: 8192 MB
RAM x 1,5 = 12288
MB page file
«High
performance»
instead of
«Balanced»
Create one for
content and
search on every
SP Server
(cliconfg.exe)