The idea (in Sharepoint) is to try and avoid a FULL crawl as much as possible – since it is a resource (CPU) hog – and can bring a server to a standstill.

Earlier, Sharepoint only had two options – FULL crawl and INCREMENTAL crawl. The biggest drawback to incremental crawls was that it would not pick up changes that occurred WHILE it was running.  So – an incremental crawl typically had to be followed (or preceded) by a full crawl.

Recently (2013), Sharepoint addressed this problem by offering another crawling option – CONTINUOUS crawls. These are basically PARALLEL crawls that ensure that all content gets picked up – even if it was inserted during the run of a specific crawl. 

This article describes CONTINUOUS crawls in more detail.

Anuj holds professional certifications in Google Cloud, AWS as well as certifications in Docker and App Performance Tools such as New Relic. He specializes in Cloud Security, Data Encryption and Container Technologies.

Initial Consultation

Anuj Varma – who has written posts on Anuj Varma, Hands-On Technology Architect, Clean Air Activist.

 Twitter Linkedin