Customizing Full-Text Indexing
Customizing Full-Text Indexing
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.
You can add properties to participate in Full-Text Indexing and add or remove noise words that are excluded in a search.
Note Non-Searchable Properties cannot be full-text indexed because they are calculated.
Adding Properties
If you are familiar with adding keys to the Microsoft® Windows® registry, you can set up other properties to be full-text indexed in addition to the urn:schemas:httpmail: Namespace properties listed in Full-Text Indexing. You create a text file containing a list of properties that you want to be full-text indexed and then refer to this file by the following string in the registry:
HKEY_LOCAL_MACHINE\Software\Microsoft\Search\1.0\ExchangeParameters\SchemaTextFilePathName
To add properties for full-text indexing
Caution If you use the Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using the Registry Editor incorrectly. Use the Registry Editor at your own risk.
Create a text file of a list of properties that you want to be full-text indexed. The full name for each property must be on a separate line.
- For properties created via ADO, OLEDB, or WebDAV, use the property name.
- For MAPI named properties (those created using Microsoft Outlook® forms), use the property set GUID (for example, PS_MAPI, PS_PUBLIC_STRINGS or a user-defined value) and the property name: https://schemas.microsoft.com/mapi/string/{propset GUID}/property-name. For example, if you had a property named "myproperty" in the PS_MAPI property set, you would use: https://schemas.microsoft.com/mapi/string/{00020329-0000-0000-C000-000000000046}/myproperty.
- For standard MAPI properties, the form to use is: https://schemas.microsoft.com/mapi/proptag/value. For example, the property PR_DISPLAY_NAME that has a property tag 0x3001001E would be https://schemas.microsoft.com/mapi/proptag/0x3001001E.
Note The href Field and displayname Field cannot be full-text indexed.
More information can be found in the https://schemas.microsoft.com/mapi/ Namespace topic.
Start the Registry Editor by entering regedt32 at a command prompt.
Activate the HKEY_LOCAL_MACHINE window.
Navigate to the key Software\Microsoft\Search\1.0.
If it does not already exist, add a key under 1.0 with the name ExchangeParameters.
If it does not already exist, add a string value under ExchangeParameters with the name SchemaTextFilePathName. The SchemaTextFilePathName string should contain the path to the text file of properties, such as E:\Exchsrvr\fulltextprops.txt.
Close the Registry Editor.
The properties will be full-text indexed the next time full-text indexing is run as configured in the Exchange System Manager.
Editing Noise Words
Noise words are words that the MSSearch engine excludes from a full-text search, such as "but" and "or". Noise word files are in the \Program Files\Common Files\System\MSSearch\Data\Config folder on the Microsoft Exchange 2000 server. There are noise words for different languages, and the English noise word is noise.eng.
You can add or remove noise words in these files. The changes won't take effect until the next time Full-Text Indexing is run.
Send us your feedback about the Microsoft Exchange Server 2003 SDK.
This topic last updated: December 2002
Build: June 2007 (2007.618.1)
© 2003-2006 Microsoft Corporation. All rights reserved. Terms of use.