1. Boring is stable, stable is good - best practices in practice
Alexander Arvidsson
Boring is stable, stable is good - best practices in practice

3. Image copyright: https://www.autoevolution.com
@arcticdba

4. Principal Solutions Architect at Atea
Presenter / blogger / podcaster
Star Wars fan
@arcticdba

6. Consider using the unattended file
Patching goes without saying

7. Antivirus Hyper-threading Memory Instances Power gMSA @arcticdba
Never use Antivirus
@arcticdba

8. Antivirus Hyper-threading Memory Instances Power gMSA
SE can use 16 *cores* - difference between vm and bare metal

9. Antivirus
Hyper-threading
Memory
Instances
Power
gMSA

10. Standard Edition max RAM: 64GB Server RAM: 96GB
Procedure Cache
Connection context
Buffer Cache
System-level data structures
Log caches
max server memory
@arcticdba

11. Antivirus Hyper-threading Memory Instances Power gMSA @arcticdba
Power settings
@arcticdba

12. Antivirus Hyper-threading Memory Instances Power gMSA @arcticdba
One or several instances, think about networking
@arcticdba

13. Antivirus Hyper-threading Memory Instances Power gMSA @arcticdba
@arcticdba

14. Alignment is most often no longer an issue

15. Stripe size
Disk layout
IFI
@arcticdba

16. SQL Server will use anything between 512bytes up to 8M (columnstore)
SQL Server will use anything between 512bytes up to 8M (columnstore). Also use /L for format or –UseLargeFRS paraeter for the Format-Volume powershell cmdlet (CheckDB failing error 665) NTFS large file record segments.
@arcticdba

17. Bob Ward Summit 2014
@arcticdba

18. Stripe size
Disk layout
IFI
@arcticdba

19. C:\ (OS) D:\ (SQL Server) E:\ (Data) F:\ (Log) S:\ (Backup) T:\
(TempDB)
Perhaps slap E and F together?
Sparse files för checkdb
Max 500GB LUNs enligt IBM
@arcticdba

20. Stripe size
Disk layout
IFI
@arcticdba

21. Mention security aspect
@arcticdba

22. Mention security aspect

23. Mention security aspect

24. SQL
Again, patching is a no-brainer

25. Trace flags Lock pages in memory SQL Mail Max/minmemory DAC
DBATools
SQL Mail
Max/minmemory
DAC
MAXDOP
& cost threshold
Optimize for
ad-hoc
Backup compression
TempDB
DB file settings
Query Store
Operators & alerts
Agent config
Maintenance (jobs)
Trace Flags
1117, 1118, 2371 (stats), 2562 (checkdb), 2549(checkdb), 4199 (optimizer enhancements)
LockPages
Jonathan Kehayias has a great blog post with both sides of the argument and lots of interesting information:
DBATools
setup install-module dbatools
SQL Mail
Set it up
Memory
max/min, visa kalkylatorn
Test-DbaMaxMemory
DAC
Maxdop/cost
Start with 40-50, explain OLTP
MAXDOP
Adhoc
Dynamics/AX - do not turn on
Backup compression
TempDB
If not =>2016 set the files
File growth in general
VLOGs
DB file settings
Edit MODEL
Growth never in percent
Query store
ON, open query store
Operators & alerts
Set them up
AgentConfig
Failsafe, mail profile, etc.
Maintenance
Ola
All jobs have failure s
Create a DBA database
Install-DbaMaintenanceSolution -SqlInstance RES Database DBA -BackupLocation “Z:\SQLBackup” -CleanupTime 72
@arcticdba

26. DOCUMENT
(no, seriously, do it)
@arcticdba

27. (you heard the man, do it)
BASELINE
(you heard the man, do it)
@arcticdba

28. AUTOMATE
(don’t do boring)
@arcticdba

29. TRAIN
(shit happens)
@arcticdba

30. @arcticdba

31. http://www.arcticdba.se/?page_id=3488 Alexander Arvidsson
@arcticdba
Image copyright: Autoglitz