0
After i saw that the Search indexer service eats all my performance on my C: drive, i just want it to stop so i disabled the service but it seems like this did not stop it. Together with the Search Protocol host it starts again and again. I moved the SearchDatabase to another SSD of mine to release some pressure from my windows drive, but it still eats around 20% CPU on idle.
So why did the Service starts even when i set it to disabled? Does this might connect to the SQL2016 service as i know it will use the Windows Search service if possible. This was no problem in the older editions of SQL server as a Pre-16 edition simply did not use the service. Did that changed?
Best wishes JPB