manual

7 www.microsoft.com/sharepoint
• Features
• Site definitions
• Language packs
It will also expose potential issues, including:
• Large lists
• Data orphans
• CAML views and CAML content types
• Modified content databases that have improper schemas
• Missing upgrade dependencies
All of this information will be collected and then output into an .htm file you can view
from your browser. This process is read-only. It does not change your environment, so
you can run it often, not only before upgrading but also just to check the general health
of your environment. Any automatic fixing of your environment will occur at upgrade
time and not during pre-upgrade scanning.
If you are already running SharePoint Server 2010 and would like to check whether your
content databases are Office SharePoint Server 2007 or SharePoint Server 2010
databases, you can use a Windows PowerShell cmdlet. The cmdlet Test-
SPContentDatabase can be run against the databases of either version. It will test a
specific database referenced against a specific Web application. It identifies current or
potential issues, such as:
• Data orphans
• Missing site definitions
• Missing features
• Missing assemblies
This cmdlet is meant to complement the pre-upgrade checker report and is also read-
only, preventing any disruption of your data while you are testing for issues.
Upgrade Methods
There are two primary methods for upgrading from Office SharePoint Server 2007 to
SharePoint Server 2010: in-place and database attach. The in-place method is used to
upgrade an existing Office SharePoint Server 2007 server to SharePoint Server 2010, and
the process can be restarted as necessary if issues arise. While the database attach