Server Fault is a question and answer site for system and network administrators. 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 was recently looking over the settings for a server (Windows 2003 SP2) that is used exclusively as the DB host for a Sql Server 2005 install that is used on a website. I saw that for all three drives on the machine (one for system/program files, one for data and one for logs) the Indexing Service was turned ON.

In my experience (mostly with desktop, not server setups), the performance hit of the indexing service doing its job has always cost much more in terms of performance than any speed gains in finding files (for me, turning it off has always resulted in a big performance gain).

So is there any reason why this should be turned on for a Sql Server Box (or any server, for that matter)? Assume that no tables use Full Text Indexing (would that make a difference)?

share|improve this question
up vote 3 down vote accepted

No reason you typically need Indexing Service enabled on a Sql Server 2005+ server, even if you are using FTS (in Sql 2005 and beyond, Sql uses it's own indexing service, MSFTESQL or Sql Service FullText Search). I thought the service itself was by default disabled on Server 2003+ anyhow? Naturally, regardless of what is checked for each LUN/folder on your server, if the service is stopped, it ain't gonna index.

share|improve this answer

Try going through the Security Configuration Wizard, it will help you establish the role of the server and turn off unneeded services and so fourth. It should well know what MSSQL2005 is and tune it for that and you can always roll back the changes.

share|improve this answer

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.