I have a scheduled task that runs once a day updating the index and I now use it more than the Outlook search.

Personally I’ve been using the indexing feature for searching an archive of over 15 years of emails. You can create multiple indexes and indexes can be shared over network drives with other people (searched concurrently) and, most importantly, the searches are sub-second ‘Search-as-you-type’ speed operations. The index isn’t updated unless you specifically update it and the index isn’t loaded unless you try and search it, so there is no performance impact to people who never need to use the indexing functionality. Specify what should be included in the index.Create an index using the Index Manager.That’s because it’s not intended as a Desktop Search replacement instead it’s more for searching large repositories of fairly static data. It won’t do anything until you ask it to. It won’t be running in the background consuming valuable CPU cycles and it won’t be building secret indexes consuming valuable disk space. If you don’t use the feature then you won’t notice it because it’s effectively disabled by default. However, and this is a really important point, it’s not the type of indexing component that’s always running in the background. Yes, I know, I’m still a little surprised myself. So it might seem surprising that I’m now announcing that FileLocator Pro v.8 supports indexing. These drawbacks include …”Īnd I go on to list resource issues, syncing issues, security issues and more. While indexing can certainly improve the speed of searches in certain circumstances there are many drawbacks. “No FileLocator Pro does not use file or content indexes and for very good reasons.

In a FileLocator Pro QA “ Does FileLocator Pro create an index for searching?” I once answered:

It’s been a while coming but… FileLocator Pro 8.0 is now available for immediate download!

Filelocator pro containing text