Your SlideShare is downloading. ×
SharePoint and SQL Server Database Management
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

SharePoint and SQL Server Database Management


Published on

If you are an DBA or and Systems Administrator at an organisation where SharePoint has been deployed you may wonder why it needs so many databases. This session covers what these are and what you …

If you are an DBA or and Systems Administrator at an organisation where SharePoint has been deployed you may wonder why it needs so many databases. This session covers what these are and what you should be doing to look after them.

This session will outline the SharePoint 2010 architecture and what planning you'll need to do to keep SharePoint performing by ensuring that your exsisting SQL server deployments can cope with SharePoint demands.

Published in: Technology

1 Like
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Chandima KulathilakeMCTS/MVP (SharePoint)
  • 2. Chandima – aka “Chan” @chandimak ontwitterSolutions Architect @ Knowledge Cue- SharePoint Consulting in New ZealandStarted with SharePoint 2001... It‟s beena great journey SharePoint MVP since
  • 3. Help with strategy and planning forSharePointSense making for large enterprise projectsPre RFP stage expectation settingSharePoint best practices/ “real world”balancing actConsulting and deployment supportMicrosoft certified SharePoint experts@knowledgecue on
  • 4. Introduction to SharePoint 2010Introduction to how SharePoint uses SQL Planning for the SQL databasesSP2010 Deployment Planning Guidelines
  • 5. SharePoint Server 2010 64-bit only Requires 64-bit Windows Server 2008 or 64-bit Windows Server 2008 R2 Requires 64-bit SQL Server 2008 SP1 or SQL Server 2008R2 SQL Server 2005 + SP3 and CU (64bit)
  • 6. WFE – Some changes, mostly optimizationApp Server – Many changesSQL – Some changes, heavy optimization Web Tier Application Tier SQL TierSum total is:Architecture is familiar, but there are many moredesign choices now2010 is far more flexible than 2007 (yet complex)
  • 7. User ExcelAccess Services Search Profiles CalcBusiness Data CatalogExcel Services BDCManaged Metadata Service VisioPeople WAC 3rdSearch Service Application party ServiceSecure Store ServiceState ServiceUsage and Health data collection http://itweb/ http://hrweb/Visio Graphics ServiceWeb Analytics Service ApplicationWord Conversion Service Application
  • 8. No longer a separate SSP web site SA‟s managed via central adminPick and choose your service apps (SA) If you don‟t need a service app, don‟t add itWeb apps can consume SAs on anindividual basis Each web app can use any combination of all available SA‟sDeploy multiple instances of the same SA Just give each one a unique nameReuse SA instances across multiple webapps in farm
  • 9. User User Excel Search Calc Search Profiles Profiles SSP BCS Excel Visio BDC Calc WAC 3rd party Service http://itweb/ http://hrweb/ http://itweb/ http://hrweb/Corp Farm Corp Farm MOSS 2007 Model SP2010 Model
  • 10. Enterprise FAST Search Visio Graphics Search PerformanceWord Automation Web Analytics Access Services Point Functional Services Business DataOffice Web Apps Excel Services User Profiles Connectivity Structural Services App Discovery Managed and Load Security Token Secure Store Metadata Balancing Foundation Services
  • 11. Service Applications with their own DB: Search (3) User Profile (3) Managed Metadata Secure Store State Service (2*) aspnet_sessiondb Business Data Connectivity Web Analytics (2) Performance Point Usage and Health data collection Word Automation
  • 12. Service Application Database * Relative SizeUsage and Health Data Collection Service Application Usage Extra LargeBusiness Data Connectivity (BCS) Service Application Business Data Connectivity SmallApplication Registry Service Application Application Registry SmallSharePoint Foundation Subscription Settings Service Subscription Settings SmallSearch Service Application Search Administration MediumSearch Service Application Crawl Extra LargeSearch Service Application Property Large > Extra LargeWeb Analytics Service Application Reporting Extra LargeWeb Analytics Service Application Staging MediumState Service Application, Visio Service Application, InfoPath State Medium > LargeForms ServicesUser Profile Service Application Profile Medium > LargeUser Profile Service Application Synchronization Medium > LargeUser Profile Service Application Social Tagging Small > Extra LargeManaged Metadata Service Application Managed Metadata MediumSecure Store Service Application Secure Store SmallWord Automation Service Application Word Automation Services SmallPerformancePoint Service Application PerformancePoint Small
  • 13. Many more databases to manage Most service applications will have their own database People service has 3, Search can have multiple crawl and property store databasesSnapshot management You can force snapshots during backup Content Deployment will support working off snapshotsUnattached content database restore Browse through a content database that isn‟t joined to a farm to find content to restoreRemote Blob Storage API Replaces External Blob Storage (EBS) from SharePoint 2007 Supports file stream providers for external storage
  • 14. SharePoint content/configuration settingsare stored in SQL databases A deployment may have multiple content databases A site collection must exist completely in a single content database A content database may have multiple site collectionsService applications get their own contentdatabases
  • 15. How does that GUID stuff happen?
  • 16. Plan before youInstall...As DBA you cancreate the DB‟sbefore the install(Give proper names)
  • 17. Service account for SQL ServicesSharePoint Setup AccountSharePoint Farm Service Account Used by the CA web site application pool
  • 18. SharePoint Setup Account (Used to setupSP2010) dbcreator public securityadminRest of it is applied per ServiceApplication/Managed account viaprovisioning
  • 19. Created when a new SharePoint webapplication is createdContainer for all site specific data Site Collections Lists Libraries etc
  • 20. Establish target sizes Plan to put one or more site collections in dedicated databases Avoid more than 250 site collections in a single database Max content databases per web app : 100 Number of site collections per content database keep it less than 250*
  • 21. Number of documents = DAverage size of documents = SNumber of List items = LNumber of versions = V (must be abovezero)10KB = Constant for Meta data valuesDB Size = ((D x V) x S) + (10KB X (L + (V x D)))
  • 22. Input ValueNumber of documents (D) 200,000Average size of documents (S) 250KBList items (L) 600,000Number of non-current versions (V) 2 (Assuming most number of versions allowed is 10) Database size = (((200,000 x 2)) × 250) + ((10 KB × (600,000 + (200,000 x 2))) = 110,000,000 KB or 105 GB
  • 23. Content Database Size per DatabaseInstanceRecommendation  50-100 GIG: It‟s allabout your SLA. If something goes down,how long can you be offline for?Backup and Restore take time in two ways: Backup: The larger the database the longer the backup. Restore: The larger the database the longer the restore process.
  • 24. Quotas at Web App > Site Collection levelAutogrow at DB levelCan pregrow the content databases
  • 25. Make sure that your Business engages withyou for the next SharePoint deploymentUnderstand your storage and HighAvailability solutions and what it means interms of $$$ and sense to provide that
  • 26. 2005? 2008?32 bit or 64 bit?Standard or Enterprise2005 > 2008 is recommended2008 R2 is best (as they say)
  • 27. SP3 is required when using SQL 2005 Major improvements in maintenance wizard Data Compression Analysis Services improvements
  • 28. Enterprise offers the following advantages Full SQL 2005 functionality (DB+AS+IS+RS) Supports more than 4 CPUs Support for up to OS Max RAM Database Partitioning Online restore Active failover for mirrorsComparison chart of all the versions at
  • 29. Use a custom maintenance plan to performthe following maintenance tasks againstSharePoint databases: Check database integrity > DBCC CHECKDB Impacts performance (safe to run at low load times) Reorganize indexes Reduce size of database files > DBCC SHRINKFILE Monthly or quarterly as part of maintenance
  • 30. Don‟t include DBCC SHRINKDATABASE asan auto step in your plansDBCC SHRINKFILE is the way to go forSharePoint Kimberly Tripp –
  • 31. Content databases (Very Important)Databases required for Service applicationsSearch databasesConsider use of System Centre DataProtection Manager
  • 32. Backup Can be done as part of maintenance plan. Three types Full Partial Differential Can use built in software or third party. Redgate, Quest software allow for database compression and encryption. Results in smaller backups Could also result in faster backups, if drive speed is the bottleneck
  • 33. Clean up History Cleans up old information from Maintenance Plans, SQL Agents and Backup and Restore Operations Leave as many jobs as you‟d like T-SQL is shown in propertiesMaintenance plans can be altered via the UISet up maintenance plans for differentintervals; daily, weekly, monthly, quarterly,etc.
  • 34. Should you shrink databases or logs? Database size is reduced by dropping unused space. Uses T SQL command DBCC SHRINKFILE instead of DBCC SHRINKDATABASE Do not shrink databases unless something drastic has happened Massive site or content deletions Removing site collections from old content databases Abandoning databases Has a heavy impact on the serverDatabases grow, it is what they doGrow operations can be slow in SQL and will likely result ina fragmented database fileCreate database with enough space for one year‟s worthof growth Used Space Size on Disk Size on Disk 120GB 100GB Free Space
  • 35. For example, if your SQLserver name is„SQLSERVER1‟, usesomething like „SPSQL‟ toconnect, and have DNSpoint to the proper serverlocation. This makes itMUCH more flexible.
  • 36. SOURCE (32bit) FARM A DESTINATION (64bit) FARM BTier C – Phase 3 x86 (MOSSWEB1) x86 (MOSSWEB2) x64 (SPWEB1) (SPWEB2) x64Tier B – Phase 2 x86 (MOSSAPP1) x64 (SPAPP1)Tier A – Phase 1 x86 (SQL) x64 (SQLSERVER08)
  • 37. Web Front End GoodServers (WFE) Dual/Quad Core Processors 4GB for WFE (Virtualised) 8GB for APP (Virtualised) Application 8-12GB for SQL < Dedicated Servers (WFE) Suitable for typical medium size organisation in NZ (200-500 users) DatabaseBackend (Shared) • Collaboration sites • Project Sites • Intranet
  • 38. Web Front End BetterServers (WFE) Dual/Quad Core Processors 4GB for WFE (Virtualised) 6>8GB for APP Application 8-12GB for SQL on a cluster or log Servers (WFE) shipping Can support more than 1000 users DatabaseBackend (Shared)
  • 39. NLB Best (Large high availability)Web Front End Quad Core ProcessorsServers (WFE) 8GB for WFE x 2 8>12GB for APP x 2 Application 16>32GB for SQL on a cluster with Servers (WFE) log shipping/mirror 10k users Database Backend (Dedicated)
  • 40. Web /App Server Mostly like this…Virtualised all in Slow perf one box! Ad-hoc backups No planning Mixed expectations Database Dissatisfied users/business Backend(Shared with lots of other apps)
  • 41. Mike Watson –
  • 42. SQL and SharePoint page on TechNet will put a link and do a summary of this talkon my blog