Enterprise Search is one of the topics that required in every organization but sometimes it doesn’t get enough resources. I don’t mean CPU, memory, etc. but human resources during the plan, deploy and configure the search infrastructure and architecture.

Let me summarize some key components that you need to plan if you’d like to deploy an Enterprise Search for your SharePoint.

Lately I’ve been asked what the implicit phrase matching exactly means. The answer is pretty long so cannot fit into a tweet so I decided to put it into a blog post…

 

As you know, search functions are based on two major components: crawling/indexing and querying. Query server receives the user queries, build the answer based on the indices, and send it back to the user. The result set contains a set of results, ordered by the ranking of each of them (in FAST Search Server for SharePoint 2010 you can change the sorting property). Ranking algorithms can be very complex, but basically they have some common things. For example, the most important factors of a term’ rank are the frequency and location of keywords.