IixssoQuery::OptimizeFor property

[Indexing Service is no longer supported as of Windows XP and is unavailable for use as of Windows 8. Instead, use Windows Search for client side search and Microsoft Search Server Express for server side search.]

Controls whether queries are optimized for better performance or for a greater number of hits.

This property is read/write.

Syntax

HRESULT put_OptimizeFor(
  [in]          BSTR val
);

HRESULT get_OptimizeFor(
  [out, retval] BSTR *val
);

Property value

Specifies a string that has the following syntax:

"performance" | "recall" [, "hitcount" | "nohitcount" ]

These components have the following effect:

"performance" | "recall"

The default is "recall". If "performance", Indexing Service first collects the maximum number of hits and then eliminates hits that don't meet the scope or security requirements.

Note

Optimizing for performance may result in less than the expected number of hits for queries in which scope checks or security checks remove hits.

 

"hitcount" | "nohitcount"

The defaults is "nohitcount". This controls whether to request the Hitcount property, which represents the total number of hits matching the query, from the ADO query property collection. This property is a custom property supported by the OLE DB provider, accessed through the query object property set.

The "hitcount" and "nohitcount" options are not implemented for Indexing Service for Windows. It is used exclusively in the implementation of Indexing Service for Microsoft Site Server.

Remarks

If you choose the performance option, scope and security trimming are deferred until after the maximum number of hits is collected. If the option is set to recall, the result set trimming occurs while executing the query. The default is to optimize for recall.

For Web clients, the query string variable URLs associated with this property is op.

In former releases of Indexing Service, this property replaces the .idq parameter CiDeferNonIndexedTrimming.

Requirements

See also

IixssoQuery