Field note / 23 January 2012
A correction on SharePoint, SQL fill factor and index rebuilds
A confident recommendation can travel further than the evidence behind it. This note is about the repair.
Database tuning advice often arrives as a rule: change this value, rebuild that index, and performance will improve. The rule may be based on a narrow test, a different workload or a misunderstanding of what the setting controls. When the evidence changes, the advice should change with it.
Fill factor is a good example. It affects how much free space is left on a page when an index is built. That can reduce page splits for some write patterns, but it also increases the size of the index and the work required to read it. There is no universal value that suits every SharePoint database.
Separate the symptom from the setting
Start with the observed workload. Identify the slow operation, the query plan and the storage response. Then ask whether index maintenance is relevant to that operation. A rebuild may improve a report while doing nothing for the write path that users actually notice.
Record the baseline, the change and the result. If a recommendation came from a trusted source, still test it against your data. A correction is not an embarrassment; it is the normal way technical guidance improves.
The short list
Checks worth running
- Measure the workload before changing an index setting.
- Check whether the change affects reads, writes or both.
- Keep the before and after evidence with the farm record.
The useful lesson is methodological. Treat database tuning as an experiment with a baseline, not as a set of slogans to apply everywhere.
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: Server memory configuration (opens in a new tab)How SQL Server allocates memory and how the maximum server memory setting is applied.
- Microsoft Learn: Soft NUMA in SQL Server (opens in a new tab)Background on SQL Server NUMA configuration for large processor layouts.
- Microsoft Learn: SQL Server security (opens in a new tab)Authentication, permissions and protection features in the database engine.
- Microsoft Learn: SharePoint administration (opens in a new tab)Operational guidance for service settings, site management and the modern admin experience.
- Microsoft Support (opens in a new tab)Support articles, troubleshooting steps and product help from Microsoft.
- 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: 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: Always On availability groups (opens in a new tab)Architecture and operational overview for SQL Server high availability groups.
- Microsoft Learn: SharePoint documentation (opens in a new tab)The starting point for current SharePoint administration, development and hybrid guidance.
- 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.