Today one of my colleagues was experiencing some problem in the Microsoft Office SharePoint Server 2007 test environment. He started a crawling job last Friday and the job was still running this morning. He found a post with a solution for this problem. The title is “MOSS 2007 crawl never ends”. Click here to see the post.
The solution was to truncate some tables from the “shared_services_ search” database. The post also referred to http://support.microsoft.com/kb/930887/en-us . We solved the problem by truncating the following tables on the “shared_services_ search” database:
TABLES TO BE TRUNCATED (not deleted!!!):
MSSAnchorChangeLog
MSSBatchHistory
MSSChangeLogCookies
MSSCrawlChangedSourceDocs
MSSCrawlChangedTargetDocs
MSSCrawlContent
MSSCrawlDeletedURL
MSSCrawlHistory
MSSCrawlQueue
MSSCrawlURL
MSSCrawlURLLog
MSSDocDeleteList
(Exclude the MSSCrawlHistory table, if you try to truncate it, it will give you a FOREIGN KEY constraint).
You can use this script:
truncate table
go
truncate table
MSSBatchHistory
go
truncate table
MSSChangeLogCookies
go
truncate table
MSSCrawlChangedSourceDocs
go
truncate table
MSSCrawlChangedTargetDocs
go
truncate table
MSSCrawlContent
go
truncate table
MSSCrawlDeletedURL
go
truncate table
MSSCrawlQueue
go
truncate table
MSSCrawlURL
go
truncate table
MSSCrawlURLLog
go
truncate table
MSSDocDeleteList
go
–End of Script
I hope this post will help you.
Like this:
Like Loading...
Related
Published by
isalom
I was born in Barranquilla, Colombia in 1975. When I was 17 I moved to Curacao where I lived 10 years and then move to The Hague, The Netherlands. I speak 4 languages (Dutch, English, Papiamento and Spanish).
I'm a Systems Engineer graduated from The Hague University (http://www.thehagueuniversity.com/). I have been working in IT for over 15 years. Since November 2014 I started www.cenlinea.com a webportal were the focus is to make learning more fun. At Cenlinea we are currently promoting PLAYDIOM a new methodology to learn English. While currently working part-time time at Cenlinea, I am also working as Senior Princiapal Consultant at www.ccgroep.com which helps me to keep up to date with Microsoft SQL Server, which I consider to be one of my favorite things in life as it has changed my life in many ways.
I hope you enjoy my blog and if you want to send a question, just drop me a mail at ignacio.salom@cenlinea.com or ignacio@ccgroep.com
View all posts by isalom
IgnacioSalom.com 
Hello
thanks for your post
we did not met the crawl issue since one month
we have a search DB with currently 1GB
what is the threshold where we shoud purge these tables?
Thanks
best regards
My Search DB is 30 GB. I don’t know what is the threshold to purge these tables. In my case the problem was only one time. Do you experience this problem more often?
I think the first “truncate table” is missing the MSSAnchorChangeLog, which somehow appeared after the –End of Script. When I run this script everything gets truncated ok except for the MSSCrawlHistory. The following error pops up:
Cannot truncate table ‘MSSCrawlHistory’ because it is being referenced by a FOREIGN KEY constraint.
Thank you for your comments. I edited the script according to your remarks. The MSSCrawlHistory will give you indeed a FOREIGN KEY constraint error when trying to truncate it. Just skip that table and you will be able to do the crawling again.