Here is a SQL query to see the partial matches attribute:

select * from trustee_attr where attr_name = '[Settings]SearchPartialMatches'
and attr_val like 'Yes'

I do not know if it would be appropriate to replace the attribute in the SQL table directly.

As for your first and third questions, I'm not sure I understand what you are asking. Turning off these options improve performance. There is not a separate set of options that have better performance but the same results, otherwise those would be used be default.

It is recommended to have Fuzzy search turned off unless you explicitly need to perform a fuzzy search because the more flexible a search is, the more time and resources it takes to complete, and the more "noise" (irrelevant documents) you will have in your results.

Similarly, "Resolve Shortcuts" (referred to as "Include Shortcuts in Search Results" in the paper) is not typically necessary but will take up more server resources and slow down searches. Resolve shortcuts is necessary if a user is performing a search where they can see the shortcut but not the document, and they are searching on the document's metadata (such as fields) or text. "Resolve Shortcuts" would be useful, for example, if the repository was set up using Transparent Records Management.