ecktwo wrote
Before turning the search scheduler back on, try re-indexing manually once and see how long that takes.
Ok.. I've done it on the 441 db now with this result:
|
SearchCommonWords
|
dbo
|
8/10/2006 5:30:14 PM
|
PRIMARY
|
369
|
|
SearchIndexer
|
dbo
|
8/10/2006 5:30:14 PM
|
PRIMARY
|
1
|
|
SearchItem
|
dbo
|
8/10/2006 5:30:14 PM
|
PRIMARY
|
4
|
|
SearchItemWord
|
dbo
|
8/10/2006 5:30:14 PM
|
PRIMARY
|
65
|
|
SearchItemWordPosition
|
dbo
|
8/10/2006 5:30:14 PM
|
PRIMARY
|
0
|
|
SearchWord
|
dbo
|
8/10/2006 5:30:15 PM
|
PRIMARY
|
0
|
I'm confused why there are still a few records listed for SearchIndexer, SearchItem and SearchItemWord (I understand SearchCommonWords is not part of this). I'm mainly confused that when I click to examine the contents of these items, there are no records listed.
Is that possibly a clue to the duplicate key errors that occur and caused this whole mess? Some sort of buggy data hiding in there perhaps?
I'll do a manual index right now and time it - There are a few portals on here, but not a lot of pages so I don't expect much. I've got minimum word length 3 and common words and numbers included.
Result: 2 minutes. Now I'll check the tables and see what happened:
|
SearchItem
|
dbo
|
8/10/2006 5:30:14 PM
|
PRIMARY
|
508
|
|
SearchItemWord
|
dbo
|
8/10/2006 5:30:14 PM
|
PRIMARY
|
17530
|
|
SearchItemWordPosition
|
dbo
|
8/10/2006 5:30:14 PM
|
PRIMARY
|
41001
|
|
SearchWord
|
dbo
|
8/10/2006 5:30:15 PM
|
PRIMARY
|
6147
|
That's less than was there before. hopefully it got rid of the buggy bits. I'll re-enable the scheduled task but set it for a once-daily run instead of the 30 minutes it defaults to.
Thanks for the advice.. and any further comments are still keenly observed!
Rob