How search features are affected by upgrade
Applies To: Office SharePoint Server 2007
This Office product will reach end of support on October 10, 2017. To stay supported, you will need to upgrade. For more information, see , Resources to help you upgrade your Office 2007 servers and clients.
Topic Last Modified: 2016-11-14
In Microsoft Office SharePoint Portal Server 2003, all search settings were stored in the registry, except for scopes and best bets which were stored in the content database. During an in-place or gradual upgrade to Microsoft Office SharePoint Server 2007, most search settings are upgraded, with the following exceptions:
Index files are not upgraded. They will be re-created when the server or farm is crawled for the first time. After upgrading to Office SharePoint Server 2007, you must perform a full crawl of any content you want to index.
Scopes are not upgraded. You must re-create search scopes after upgrading to Office SharePoint Server 2007. For more information, see the "Manage Search Scopes" topic in the SharePoint Central Administration Help system.
Search alerts are not upgraded. You must re-create portal search alerts after upgrading to Office SharePoint Server 2007. For more information, see the "Configure search-based alerts" topic in the Office SharePoint Server 2007 Central Administration Help system.
Any filters, word breakers, and thesaurus files that you have installed are not upgraded. These files are version-dependent, and you must install new versions of these files, as available.
For more information about how search works in Office SharePoint Server 2007 and what to plan for when moving to Office SharePoint Server 2007, see Plan search (Office SharePoint Server).
Note
If you have shared services, when you upgrade the parent portal, the settings from the parent portal's servers are added to the upgraded Search database.
Because the search settings are stored in the registry and not in the database, if you choose a database migration approach to upgrade, none of the search settings are upgraded; you must manually reconfigure search in the new environment.
The following table lists the settings for search in SharePoint Portal Server 2003 and what happens to these settings during and after the upgrade process.
| SharePoint Portal Server 2003 search setting | SharePoint Portal Server 2003 scope | What happens during upgrade | Office SharePoint Server 2007 setting | Office SharePoint Server 2007 scope |
|---|---|---|---|---|
Default Content Access Account and Default Content Access Account Password |
Central Administration |
The account and password are copied over to the shared service provider (SSP) database. These were farm-wide settings in SharePoint Portal Server 2003 and were stored in the registry for all index servers in the farm. In Office SharePoint Server 2007, these settings are stored in the SSP database instead. |
Default Content Access Account Default Content Access Account Password |
Shared Services Provider (SSP) Administration |
"This Portal"/"Non-Portal" content sources |
Portal Administration |
All settings are upgraded. |
Default content source |
Shared Services Provider |
Custom content sources |
Portal Administration |
Settings are migrated from the SharePoint Portal Server 2003 registry to the Office SharePoint Server 2007 registry. |
Content sources |
Shared Services Provider |
Rules |
Portal Administration |
Rules are upgraded in the following order: portal rules, then non-portal rules, and then other rules. After upgrade, the administrator must resolve any conflicts by using the Shared Services Provider interface. |
Rules |
Shared Services Provider |
Best bets |
Portal Administration |
The best bets are copied from the Site_Serv database to the SSP database. |
Best bets |
Site |
Schema |
Portal Administration |
The schema is upgraded and changes from JET to SQL Server database format. |
Schema |
Shared Services Provider |
Site hit frequency rules |
Central Administration |
Site hit frequency rules are upgraded. |
Site hit frequency rules |
Central Administration |
Custom search pages with custom search Web Parts |
Any |
These continue to work without, any changes, after the upgrade. The query object model is still functional. |
Custom search pages with custom search Web Parts |
Any |
Schedules |
Portal Administration |
Schedule information is copied into the content sources. |
Content sources |
Schedules |
Additional notes about upgrading and search:
In a gradual upgrade, where the SharePoint Portal Server 2003 and Office SharePoint Server 2007 portals run side-by-side, and the configuration is inter-farm shared services, both the SharePoint Portal Server 2003 and Office SharePoint Server 2007 crawlers will be running side-by-side as long as child portals are not yet upgraded to Office SharePoint Server 2007. After all portals are upgraded to Office SharePoint Server 2007, you must manually turn off the SharePoint Portal Server 2003 crawler. For more information, see Perform a gradual upgrade with shared services.
In Office SharePoint Server 2007, there is only one index per farm, rather than multiple indexes with aggregated results as in SharePoint Portal Server 2003. When you upgrade, the indexes are stored on the job server, and the configuration settings from other indexes in the farm are pulled into the SSP database; however, the other index machines are no longer used.
The SharePoint Portal Server 2003 administrative object model has been deprecated in Office SharePoint Server 2007. This means that any custom applications that rely on the SharePoint Portal Server 2003 administrative object model will have to be rewritten to use the new object model in Office SharePoint Server 2007.
The Query object model and the Web service are backward-compatible in Office SharePoint Server 2007. This means that any custom applications built using those should continue to work without any modifications.
The SQL syntax is supported for search in Office SharePoint Server 2007.
SharePoint Portal Server 2003 required the Windows Task Scheduler service and used this service to manage crawl schedules. Office SharePoint Server 2007 uses the SharePoint Timer Service to perform this function instead and no longer requires the Task Scheduler service. If you are not using the Task Scheduler service for other scheduled tasks, you can stop this service after you have completed the upgrade process.
Download this book
This topic is included in the following downloadable book for easier reading and printing:
See the full list of available books at Downloadable content for Office SharePoint Server 2007.