Microsoft Search Server (MSS) was anenterprise search platform fromMicrosoft, based on the search capabilities ofMicrosoft Office SharePoint Server.[1] MSS shared its architectural underpinnings with theWindows Search platform for both the querying engine and the indexer. Microsoft Search Server was once known asSharePoint Server for Search.[2]
Microsoft Search Server was made available asSearch Server 2008, which was released in the first half of 2008. In 2010, Search Server 2010http://www.microsoft.com/enterprisesearch/searchserverexpress/en/us/technical-resources.aspx became available, including a free version, namedSearch Server 2010 Express. The express edition featured the same feature-set as the commercial edition, including no limitation on the number of files indexed; however, it was limited to a stand-alone installation and could not be scaled out to acluster.[3] Arelease candidate of Search Server Express 2008 was made available on November 7, 2007 and was scheduled toRelease to Manufacturing (RTM) in sync with Search Server 2008.
A more detailed comparison of the feature differences between Search Server 2008, Search Server 2010, and Search Server 2010 Express can be found athttp://www.microsoft.com/enterprisesearch/searchserverexpress/en/us/compare.aspx
MSS provided asearch center interface to present the UI for querying. The interface was available as aweb application, accessed using a browser. The query could either be a simple query, or use advanced operators as defined by theAQS syntax. The matched files were listed along with a snippet from the file, with the search terms highlighted, sorted by relevance. The relevance determination algorithm was developed byMicrosoft Research andWindows Live Search.[4] MSS also showed definitions of the search terms, where applicable, as well as suggesting corrections for misspelled terms. Duplicate results were collapsed together. Alerts could be set for specific queries, where the user was informed of changes to the results of a query viaemail orRSS.[5] The search center UI used theASP.NETweb part infrastructure and could be customized using eitherMicrosoft Visual Studio orMicrosoft Office SharePoint Designer. Custom actions could be defined on a per-filetype basis as well.[4]
MSS could index any data source as long as anindexing connector for the data source was provided.[5] The indexing connector included protocol handlers, metadata handlers andiFilters to enumerate the data items in the source and extract metadata from the items in the data source. If the file type in the source had a correspondingiFilter, then it was used to extract the text of the file for full text indexing as well. The handlers and iFilters MSS used are the same as used bySharePoint,Microsoft SQL Server andWindows Search as well.[4] The data sources that were to be indexed were identified by theirURIs and had to be configured prior to indexing. The indexer updated the search index as soon as an item is indexed (continuous propagation) so that the items can be queried against even before the indexing crawl was complete. MSS could also federate searches to other search services (includingSharePoint andweb search servers) that supported theOpenSearch protocol.[5] Federated locations could beserialized to a.fld file.[4]
The administration UI, which was also presented as a web application, could be used to review statistics such as most frequent queries, top destination hits, click through rates etc., as well as fine tune relevancy settings,[5] indexing policies (including inclusion and exclusion filters) and schedules, and set up a cluster of the servers.[4] It could also be used to back up either the configuration state or the search indices.ACLs could also be defined to limit the search result according to the rights of the user initiating the query.
| People |
| ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Products |
| ||||||||||
| Company |
| ||||||||||
| Campaigns |
| ||||||||||
| Criticism | |||||||||||
| Litigation |
| ||||||||||
| Acquisitions |
| ||||||||||
