Discussion Locked

Any info on Server 2003 Indexing Service

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am looking for some advice on something that I am having difficulty finding information on. I was given the task of researching whether or not we should use Indexing Service for Windows Server 2003. What performance issues arise because of it if any, but the things I cant find are advice from other people that have tried it, or what other people think of this service. Please let me know if you have any insight on this.

3 replies

by bfilmfan

Unless the server is a file server or web server, I would recommend that you turn off Indexing Service.

by rs

I'm looking for the same information. I heard that if you are searching the file server (that have indexing service running) from a different machine (ie your workstation or a Terminal Server session) then you do not see the benefit of the Indexing service. The problem I have is that users doing a search from Terminal Server to filstore (without Indexing Service) uses heaps of CPU cycles on the Terminal Server. I'm told that turning on Indexing won't actuallyhelp the situation... do you know if thats correct?

Also, have you found any good sources of Indexing Service documentation?

thanks

by dthede

Here we are 3-1/2 years later and user-level documentation on the ci (content indexer) is still very poor. The Help files are some help...(!), but there appears to be no help as to how to best manage the indexer, and how to deal with its extremely peculiar behavior over long periods of time. Just when I think I undestand how this thing works, say after a couple of weeks of dependable operation, some goofy thing happens with it, and I realize I don't know jack.

This discussion is closed to new replies.