February 25, 2014 at 9:48 am
Is it a best practice to disable "Allow files on this drive to have contents indexed" on NTFS drives used by SQL for its data, log, tempdb, etc?
In what I've read it seems to be a best practice for Filestream objects and Flash storage drives. We don't currently use Filestream objects or have Flash drives.
Are there any benefits or drawbacks to disabling this feature on an NTFS drive connected to SAN LUNs under mount points?
February 25, 2014 at 10:02 am
Unless you've changed the default file type options for the search indexer, it would only index the properties of the file (assuming it's an indexed location), which is trivial in terms of overhead. Only a small number of file types (doc, docx etc.) have their contents scanned. Definitely worth disabling if you have Filestream enabled and a large number of files, but for general data volumes, it's not going to have a noticeable overhead.
February 25, 2014 at 10:06 am
That makes sense, thanks for the info.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply