Skip to content

SharePoint 2010 Search Features that are deprecated in SharePoint 2013

As SharePoint search technology evolves, improves, incorporating FAST search components into a single SharePoint Server 2013 search architecture. Alongside comes with changes to features that were of limited usage or were merged with new search capabilities. This post summarises the key deprecated search features in SharePoint Foundation 2010, SharePoint Server 2010 and FAST Search Server 2010 for SharePoint.

  1. SharePoint Foundation 2013 based on the same search implementation as SharePoint Server.
  2. FAST Search web crawler merged into one SharePoint Server 2013 crawler.
  3. Query health reports and crawl health reports branched out of Search Administration reports.
  4. ‘Best Bets’ now labelled as ‘Promoted Results’.
  5. ‘Result sources’ replace scopes and federated locations.
  6. Web-based interface to show the current status of the topology BUT change the topology by using Windows PowerShell.
  7. Custom word breaker dictionaries gone, you can only create one language-independent dictionary.
  8. Diacritical marks such as accents automatically respected when matching query terms with terms in the thesaurus. In SP2010 it was explicitly specified in <diacritics_senstive> element of thesaurus file.
  9. Thesaurus replacements not supported. All entries in the thesaurus are expansions, and the original term is not removed from the query – to improve search relevance!
  10. Search Query web service deprecated – use the CSOM or REST based web service instead to serve stand-alone client applications
  11. RSS link on the results page gone! – replaced by the Search Alerts link because Claims authentication doesn’t support most RSS readers.
  12. Configuration of stemming in registry not supported. (query for “security” could be expanded to include documents that refer to “securing”, “securely” and so on)
  13. Complex search queries by SQL syntax not supported, instead use FAST Query Language (FQL) and Keyword Query Language (KQL) syntax for custom search solutions.
  14. Shallow refiners not supported but FAST search unified only improved Deep Refiners supported.
  15. FAST Search Database & Lotus Notes Connector replaced with Business Data Catalog connectors due to Connector framework combined with Business Connectivity Service (BCS) framework.
  16. FQL operators are aligned with SharePoint KQL syntax.
  17. FAST Anti-phrasing, offensive content filtering, substring search not supported.
  18. Cannot extract person names and locations from documents by using FAST predefined extractors (based on extraction rules) – use custom extractors (based on custom dictionaries).
  19. FAST: Can’t add a test item to the index (via DocPush test and diagnostic command-line tool).

For further details and reasoning, please check Microsoft TechNet

Chirag Patel @techChirag

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: