Netcast

Transcription

1

2 WSS MVP since 2006 Speaker, writer, consultant, Aquarius, President of the Ames Iowa chapter of the Mark Rhodes fan club Personal Blog Company web site Twitter Netcast

3 Why is SQL so important to SharePoint? SQL versions SQL terminology Proper care and feeding of your SQL server and database

4 Used by every version of SharePoint since WSS v2 Entire Farm configuration is stored in SQL All content is stored or is referenced to in SQL Central Admin is a web application rendered out of SQL Most service applications have databases as well Search has at least 4 User Profile has 3 Managed Metadata Secure Store BCS If SQL ain t happy, nobody s happy

5 Each Web Application has at least one content database Most will have multiple content databases A Site Collection must exist entirely in one content database* However, a content database can, and usually does, contain multiple site collections A content database should not be larger than 200 GB Can go larger for specialized databases Be very, very careful

6 Farm SPFarm Servers - SPServer Web Front End, APP Web Applications SPWebApplication Central Admin, Content Databases SPContentDatabase Content Database Site Collections SPSite The Bag Webs SPWeb Portal, Wikis, Blogs, Team, Doc, Workspaces, Search Center Lists Doc Libs, Pages, Events, Discussions, Surveys, Etc Items Files, Calendar items, Contacts, Customers, Images, Custom

7 SQL 2008 R2 SP1 SQL 2012 Must be 64 bit Can use SQL Express for no cost option 10 GB database limit 1 GB of RAM 1 CPU up to 4 cores Hardware and software requirements

8 Standard Enterprise CPUs (sockets) 4 (or 16 cores) OS Max Memory 64 GB OS Max Max Database Size 524 PB 524 PB Mirroring Single threaded, Full Safety Full Clustering 2 nodes OS Max Database Snapshots PowerPivot AlwaysOn Availability Groups Reporting Services X X Walks your dog Bucks $ $$$$$ X X X X

9 Server Physical box. Something you can kick. Also often erroneously used in place of Instance Instance SQL process on a server. Has its own settings, databases and security. A server can have many Instances Database An MDF file and one or more NDF files. Where the data is actually stored. Transaction Log - An LDF file. Used to store transactions before they re written to a database File MDF, NDF or LDF files that store information. Filegroup A file or group of files that store a partition of a database. Role SQL security boundary. Roles have permissions, users and logins go into Roles to get permissions.

10 User s Desktop SharePoint Server SQL Server RAM Transaction log Database File

11 Maintenance Plans are key Can be easily created manually or with a wizard Easily modified after they re created Can include a variety of operations, including backups D=248 Can you Must create yourself as an operator What should you use them for?

12 Corrupt data backs up every bit as well as uncorrupt data Uses T-SQL command DBCC checkdb Can be very disk and CPU intensive Can use PHYSICAL_ONLY switch to shorten time and impact Can run against non-live copies of your databases

13 Three types Full Partial Differential Can back up database and transaction logs Regular transaction log backups keep your hard drives happy Use backup compression to save space and time Don t forget third party solutions RBS complicates this A lot! Really!

14 Fragmented MDF, NDF and LDF files slow SQL down Using the built-in tool may lock databases 3 rd party tools are a better option Pregrow databases to minimize fragmentation

15 Databases get larger over time, it s their job SQL grow operations are slow and will likely result in fragmented databases Your database should always have white space. Always Monitor your databases and pregrow them to maintain whitespace Change autogrow settings to something more reasonable Autogrow is a last resort Consider setting a maximum database size

16 Database size is reduced by dropping unused space. Do not shrink databases unless something drastic has happened Massive web, site collection, or content deletions Abandoning databases You lost a bet Forces databases to grow again later Has a heavy impact on the server Fragments database indexes, which results in slower performance

17 Storage of blobs outside of SQL Bolts in to SharePoint 2013 Increase scale Increase performance Complicates disaster recovery Repeat after me, I will not use the SQL Filestream provider in Production.

18 Create multiple TempDB files Put databases and transaction logs on separate spindles Arrange databases according to speed of drives Change Autogrow Increase the growth rate For databases and logs Consider setting a maximum size Keep your databases under 200 GB, realistically 50 GB Use multiple content databases

19 Do not access your databases in SQL pretend they don t exist Farm backups in SharePoint also do database backups Backup your System databases too Install SQL Server Management Studio on one of your SharePoint servers Or use Query Express

20 Set Max RAM

21 Compression File Location

22 Set MaxDOP = 1

23

24

25 Like a HOSTS file for SQL connections Allows us to move SharePoint to a different SQL without SharePoint knowing Use CLICONFG.EXE to config Must configure for 64 and 32 bit Definitive work on the subject,

26 SharePoint 2013 Hardware and Software requirements Tips for database maintenance Plan for RBS in SharePoint Storage and SQL Server capacity planning Not updated yet for SharePoint

27 Questions?

28 The End! Pester or Visit me at the Rackspace booth