XSTR: Poor Performance with Advanced Find Custom Property Query (281736)

MORE INFORMATION

The following document was the reference for the indexing: Apply the section that describes how to improve the performance. This is an update to the MSDN information located at the following Microsoft Web site:

Customizing Full-Text Indexing

You can add properties to participate in full-text indexing and add or remove noise words that are excluded in a search.

Adding Properties

WARNING: If you use 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 Registry Editor incorrectly. Use Registry Editor at your own risk.

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 httpmail namespace properties listed in Full-Text Indexing. You create a text file of properties that are referred to in the registry by the following key: To add properties for full-text indexing:

1. Create a text file of a list of properties that you want to be full-text indexed. The full name for each property must on a separate line. As described here, the form of the name to be used depends on the type of property.
   • For properties created by ADO, OLEDB, or WebDAV, use the property name.
   • For MAPI-named properties (such as those created by using Microsoft Outlook forms), use the following format comprised of the property set GUID (such as PS_MAPI, PS_PUBLIC_STRINGS, or a user-defined value), and the property name:

     http://schemas.microsoft.com/mapi/string/{propset GUID}/property-name

     For example, for a property named myproperty in the PS_MAPI property set, use:

     http://schemas.microsoft.com/mapi/string/{00020329-0000-0000-C000-000000000046}/myproperty

   • For standard MAPI properties, the format to use is:

     http://schemas.microsoft.com/mapi/proptag/value

     For example, for the PR_DISPLAY_NAME property that has a property tag 0x3001001E, use:

     http://schemas.microsoft.com/mapi/proptag/0x3001001E

     NOTE: The DAV:href and DAV:displayname properties cannot be full-text indexed.
2. Start Registry Editor by typing regedt32 at a command prompt.
3. Click the HKEY_LOCAL_MACHINE window.
4. Locate the Software\Microsoft\Search\1.0 subkey.
5. If it does not already exist, add a key under 1.0 called ExchangeParameters.
6. Under Exchange Parameters, add a value with the name SchemaTextFilePathName, a data type of REG_SZ, and a string value of the path to the text file of properties, such as "E:\Exchsrvr\Fulltextprops.txt".
7. Quit Registry Editor. The properties will be full-text indexed the next time full-text indexing is run as configured in Exchange System Manager.

Editing Noise Words

Noise words are words that the search 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 Exchange 2000 server. There are noise words for different languages, and the English noise word file is Noise.eng. You can add or remove noise words in these files. The changes do not take effect until the next time full-text indexing is run.