Field note / 9 July 2011
Content database sizing after SharePoint 2010 SP1
A support limit is not a performance target. The gap between the two is where most sizing arguments begin.
SharePoint 2010 service pack 1 changed the conversation about content database size. A larger database became supportable in more scenarios, but the number did not remove the reasons for splitting content across databases. Manageability, backup windows and recovery scope still matter.
The useful sizing question is not simply how large a database can be. It is how long a backup takes, how much data must be restored for one site and how much change the platform can absorb during maintenance.
Size for recovery, not only storage
Measure the growth rate and the backup throughput together. A database that fits comfortably on disk may still exceed the available recovery window. A smaller database with a slow restore can be worse than a larger one with a tested process.
Use site collections as the unit of ownership. If one collection grows much faster than its neighbours, splitting it into its own database may simplify backup and delegation. Document the reason for each database boundary so a future migration does not undo the design by accident.
The short list
Checks worth running
- Measure growth rate, backup duration and restore time as one set.
- Confirm the support position for the exact service pack level.
- Record the ownership and reason for each content database boundary.
The support number is a ceiling, not a plan. A good design starts with recovery requirements and works backward to the database layout.
Outside reading
Reference shelf
Official documentation and independent community reading for the subjects in this note.
- Microsoft Learn: SQL Server documentation (opens in a new tab)Official reference material for database engine configuration, performance and recovery.
- Microsoft Learn: SharePoint administration (opens in a new tab)Operational guidance for service settings, site management and the modern admin experience.
- Microsoft Learn: SharePoint documentation (opens in a new tab)The starting point for current SharePoint administration, development and hybrid guidance.
- Microsoft Support (opens in a new tab)Support articles, troubleshooting steps and product help from Microsoft.
- Microsoft Learn: Server memory configuration (opens in a new tab)How SQL Server allocates memory and how the maximum server memory setting is applied.
- Microsoft Learn: Always On availability groups (opens in a new tab)Architecture and operational overview for SQL Server high availability groups.
- Microsoft Tech Community (opens in a new tab)Community discussion, product announcements and practical posts from Microsoft teams.
- Microsoft Learn Q&A (opens in a new tab)A community question and answer space hosted by Microsoft.
- SharePoint Stack Exchange (opens in a new tab)An independent question and answer community for SharePoint practitioners.
- Microsoft Learn: Azure Architecture Center (opens in a new tab)Reference architectures and design guidance for resilient cloud workloads.
- Microsoft Learn: Windows Server documentation (opens in a new tab)Current guidance for Windows Server roles, networking, storage and management.
- Microsoft Download Center (opens in a new tab)Official downloads for Microsoft tools, updates and supporting packages.
- Microsoft Learn: SharePoint search (opens in a new tab)Documentation for search architecture, crawling and result management.
- Microsoft Learn: PowerShell documentation (opens in a new tab)Language reference, cmdlet documentation and guidance for repeatable automation.
- PowerShell Gallery (opens in a new tab)A public repository for PowerShell modules and scripts. Review package provenance before use.