Field note / 16 August 2010
Choosing a SharePoint 2010 upgrade path on a napkin
A decision tree is useful when it makes the trade offs visible before the project has committed to a method.
The upgrade conversation often begins with a preferred method rather than a requirement. Someone has used a database attach before, so the project plans another one. Someone else prefers an in place upgrade because it seems shorter. The method is chosen before the constraints are on the table.
A better starting point is a small decision tree. Does the existing farm have a clean configuration that can be carried forward? Is the hardware staying? How much downtime is available? Can the content be tested with a representative copy? The answers narrow the options quickly.
Separate the method from the risk
An in place upgrade can be appropriate when the environment is healthy and rollback is not a significant concern. A database attach path gives more control and a cleaner target, but it needs a new farm, a tested content copy and more planning. Neither method removes the need for a rehearsal.
Record the assumptions behind the decision. If the farm has unknown customisations or a large content estate, the cheaper path may become the expensive one. The decision tree should show where more testing would change the answer.
The short list
Checks worth running
- List downtime, hardware, customisation and rollback constraints first.
- Test with a representative content copy, not a sample of clean sites.
- Record the assumptions that would cause the decision to be revisited.
The upgrade method is a consequence of the environment, not a preference. A simple tree helps the team argue about constraints instead of defending a favourite tool.
Outside reading
Reference shelf
Official documentation and independent community reading for the subjects in this note.
- 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 Learn: SQL Server documentation (opens in a new tab)Official reference material for database engine configuration, performance and recovery.
- 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: PowerShell documentation (opens in a new tab)Language reference, cmdlet documentation and guidance for repeatable automation.
- Microsoft Download Center (opens in a new tab)Official downloads for Microsoft tools, updates and supporting packages.
- Microsoft Learn: Windows Server documentation (opens in a new tab)Current guidance for Windows Server roles, networking, storage and management.
- Microsoft Security Response Center (opens in a new tab)Security advisories, update guidance and vulnerability response information.
- SharePoint community on Reddit (opens in a new tab)An independent discussion space for administrators, developers and users.
- Microsoft Learn: SharePoint search (opens in a new tab)Documentation for search architecture, crawling and result management.
- PowerShell Gallery (opens in a new tab)A public repository for PowerShell modules and scripts. Review package provenance before use.
- Microsoft Learn: Server memory configuration (opens in a new tab)How SQL Server allocates memory and how the maximum server memory setting is applied.