The InvalidDatabaseSchema rule in Pre-Upgrade Checker for
Windows SharePoint Services 3.0 Service Pack 2 lists the names of the content
databases that have a schema that differs
from the standard Windows SharePoint Services 3.0 content database
schema.
After you run Pre-Upgrade Checker, the InvalidDatabaseSchema
rule lists the names of the content databases that have a schema that differs
from the standard Windows SharePoint Services 3.0 content database
schema. Then, the InvalidDatabaseSchema rule suggests that you detach these
content databases before upgrading.
To
find unexpected items that are discovered in the database, open the
PreUpgradeCheck_
YYYYMMDD-hhmmss-millisecond-random-number.log file, and then
search the lines that begin with the string "[InvalidDatabaseSchema]."
Note The
PreUpgradeCheck_
YYYYMMDD-hhmmss-millisecond-random-number.log
file is located in the following folder:
%COMMONPROGRAMFILES%\Microsoft
Shared\web server extensions\12\LOGS
For more information
about the support policy around changing SharePoint content databases, click
the following article number to view the article in the Microsoft Knowledge
Base:
841057Â
(http://kbalertz.com/Feedback.aspx?kbNumber=841057/
)
Support for changes to the databases that are used by Office server products and by Windows SharePoint Services
NotePre-Upgrade Checker ships in Windows SharePoint Services 3.0
Service Pack 2.Pre-Upgrade Checker is used to assess the server for potential
upgrade issues when you are preparing to upgrade to the next version release of
Windows SharePoint Services
and Microsoft
Office SharePoint Server 2007.
For more information,
click the following article number to view the article in the Microsoft
Knowledge Base:
960577Â
(http://kbalertz.com/Feedback.aspx?kbNumber=960577/
)
List of all Windows SharePoint Services and SharePoint Server Pre-Upgrade Checker knowledge base articles