Microsoft FAST Search Server for SharePoint, SA, OLP-NL AEF-00078 Manuel D’Utilisation
Codes de produits
AEF-00078
9
www.microsoft.com/sharepoint
One of the general aims of enterprise search with FAST Search Server 2010 for
SharePoint is to implement sub-second query latencies for all searches. To achieve this,
you must ensure that no query server deals with more than ten million items. You can
achieve this by adding multiple query servers to your farm, and therefore by taking
advantage of the new index partitioning features of FAST Search Server 2010 for
SharePoint. Index partitioning enables administrators to spread the load for queries
across multiple query servers. This is achieved by creating subsets of an index, and
propagating individual subsets to different query servers. FAST Search Server 2010 for
SharePoint uses a hash of each document's ID to determine in which partition the index
entries for a specific document should be stored. At query time, the query object model
contacts each query server needed to satisfy the search so that all results to be returned
to the user are included.
SharePoint is to implement sub-second query latencies for all searches. To achieve this,
you must ensure that no query server deals with more than ten million items. You can
achieve this by adding multiple query servers to your farm, and therefore by taking
advantage of the new index partitioning features of FAST Search Server 2010 for
SharePoint. Index partitioning enables administrators to spread the load for queries
across multiple query servers. This is achieved by creating subsets of an index, and
propagating individual subsets to different query servers. FAST Search Server 2010 for
SharePoint uses a hash of each document's ID to determine in which partition the index
entries for a specific document should be stored. At query time, the query object model
contacts each query server needed to satisfy the search so that all results to be returned
to the user are included.
For more comparison data between the server-side search products from Microsoft, see
Developer Information
All of the products described above provide a unified
. The result is
that if you develop a custom solution that uses the query object model for SharePoint
Foundation 2010, for example, then it will continue to work if you upgrade to SharePoint
Server 2010, or if you migrate your code to FAST Search Server 2010 for SharePoint.
Foundation 2010, for example, then it will continue to work if you upgrade to SharePoint
Server 2010, or if you migrate your code to FAST Search Server 2010 for SharePoint.