| SharePoint 2010 introduced FAST Search
|| Search remembers what you have previously searched and clicked and displays these values as query suggestions at the top of the results page.
|Comprehensiveenterprisesearch with the ability to use Boolean operators to create search queries. For example: search for: cats AND dogs. Best bets” can be defined to force certain results to the top of search results.
||Improvements in user experience Best bets now called Promoted Results.
|Different Installation for SP2010 and FAST Search for SharePoint 2010
||Single installation in SharePoint 2013.
Wildcard search available. For example, as search for ho* would find homes, horses, houses, etc. Faceted search refiners to easily narrow results based on metadata.
Results show number of times a document has been viewed. Results pages allows you to page through PowerPoint presentations without leaving the search results page.
|WSS Search, Microsoft Search Server, Search Server Express
||Different offering for Search
||SharePoint Server Search and SharePoint Foundation search.
|Multiple crawl components on a single server but each component was associated with only one crawl database.
||Crawl components has been replaced by crawl roles in SP2013. ALL crawler roles talk to ALL crawl databases. So whenever there is content to crawl, every crawl server in the farm can work on it.
|Search Admin DB was storing the security information (ACL information).
||Search Admin DB is not storing any ACL information now. It is storing with index itself in case of SP 2013.
|Anonymous crawling was not supported into SP2010 for HTTP Site
Anonymous crawling is available in SP2013 for http sites. One click to “view in library.”
|SSA Admin can only create “Crawled “ and “Managed” properties available to the entire farm.
||Capability to do limited schema management down to site collection admins. , site collection admins can create custom crawled and managed properties that are only used in their site collection!The managed properties that can be created are limited – meaning they cannot be refinable or sortable and it only supports a text data type.
|In SP 2010, scopes can only be created by search service admin.
||Site and Site Collection admin can configure result sources for a site collection. There is no need of search service admin to intervene into this.
|This functionality was not available in SP2010.
||Indexing : Remote SharePoint Source
||A new feature to index “remote SharePoint Source” is available in SP2013 in which we can crawl a “remote SharePoint Source” available in remote SharePoint Farm in different geo locations using “oAuth Trust” which removes the issue of “kerbaros” authentication between he farms.
|In SP2010 we had pipeline extensibility, which let you write custom code to use in the transformation of crawled content before it got added to the index.
||Content Processing Customization
||In SharePoint 2013 the pipeline extensibility model is gone, but it has been replaced with a new web service callout feature. It is invoked via triggers, which you create and are based on the value of different managed properties.
|In SP2010, you could pick certain crawl components to crawl a particular URL
||Host Distribution Rules
||Host can be distributed across multiple crawl databases. The new distribution happens on the basis of Content DB Id rather than host URL.