Microsoft KB Archive/329210

= XADM: Initial Indexed Search Runs Slowly =

Article ID: 329210

Article Last Modified on 10/27/2006

-

APPLIES TO


 * Microsoft Exchange Server 5.5 Standard Edition

-



This article was previously published under Q329210





SYMPTOMS
When you modify the search flags of an existing attribute in the Exchange Server 5.5 directory schema to force it to be indexed and then perform a Lightweight Directory Access Protocol (LDAP) query request by using that attribute, you may experience a noticeable delay before the results of that query are returned. However, when you next run the query, the results are returned without this delay.



CAUSE
This problem occurs because when you change the search flags of an existing attribute in the Exchange Server 5.5 schema to force it to be indexed, the directory does not request the index to be built until the next restart of the Microsoft Exchange Directory service.

When the query is performed without first restarting the Microsoft Exchange Directory service, the Exchange 5.5 Jet database engine builds the index when it is first used. This may cause a noticeable delay in the query response time when you have a large Exchange Server 5.5 database.



RESOLUTION
To resolve this problem, restart the Microsoft Exchange Directory:
 * 1) Click Start, point to Settings, click Control Panel, and then double-click Services.
 * 2) In the Service list, click Microsoft Exchange Directory, and then click Stop.
 * 3) Note the dependent services that will also be stopped, and then click OK.
 * 4) When the services are stopped, click Start.
 * 5) Restart the other services that were stopped when you stopped the Microsoft Exchange Directory service, and then click Close.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.



MORE INFORMATION
Although query-response time is affected by the server memory, processor speed, and the hard disk subsystem speed, query-response times should be consistent on each particular server.

A little delay is expected when you first submit a query because the Jet database must obtain the information from the hard disk. Later queries have much faster response times because the query is cached in memory.

NOTE: Exchange Server 5.5 does not cache data between searches, but the Jet database and the underlying operating system do cache this information.

Keywords: kbbug kbpending kbui KB329210

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.