SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm currently doing a Full Crawl on my SharePoint server. It's been running for about 5 hours. It's adding items to the 'success' column of the crawl History.

This is after doing an Index reset, and it's the first Full Crawl on this site.

My question: Is this normal? Should I stop the crawl?


share|improve this question
Have you configured any crawler impact rules? – SPDoctor Mar 26 '12 at 15:50
I have not set any crawler impact rules. This I will look into. Thanks! – Dann Bohn Mar 26 '12 at 16:16

The performance of search will depend on a few things

Size of target being crawled, bigger it is the longer it'll take, naturally. Also, the performance of the target, if pages are loading slowly, search will run slower.

Your farm infrastructure: services per server and server performance. How is your farm setup? Is search running on its own server or shared with other services? How many users are actively on your sites? What's the hardware specs of the servers running search? These are some of the considerations for performance of search.

I'd recommend running a full crawl when user traffic is lowest, and server resources are most available, usually late night, early morning, not during a system backup.


share|improve this answer
Thanks for the input! The farm is very small, one DB server, and one App server with maybe 3 users at any one time. I'm still developing this thing so I haven't rolled it out to the entire group. I recently moved the DB off of the app server and onto a DB server. I didn't move any of the databases except for the content database, I re-installed SharePoint then attached the content database. I've been having issues with search authenticating and on Friday finally nailed it, I opted to reset the Index before doing a full crawl to "start fresh" The content Database is very small still.. – Dann Bohn Mar 26 '12 at 13:49
Yes, my full crawl lasts about 14 hours. I have to do this on the weekends. – Mike Mar 26 '12 at 14:10
Thank You, Mike. This is the first time I've got it to successfully crawl everything, so it's going much slower than my previous unsuccessful attempts! – Dann Bohn Mar 26 '12 at 16:45

It depends on so many factors. Server configuration, amount of data to index specific settings for the content sources/scopes. Be very careful though when setting your content sources. I once had a client set their search to follow links. They had linked to their internet site and then had links from that to other sites. When they finally asked me to take a look it had been running for 90 hours, they were in the process of indexing Amazon.

share|improve this answer
Thanks for the advice. I don't have it set to follow links, just to read complex URLs. It's still crawling along. It may be because the system only has 1 core on 1 CPU in our VM Environment – Dann Bohn Mar 27 '12 at 13:06

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.