I saw the KB article named "Improving the Speed of Within-Folder Searches" and was wondering if this is going to come out as a hotfix and be included with newer installations? Is there any reason you wouldn't want to implement this?
Question
Question
Is the "Improving the Speed of Within-Folder Searches" KB Going to be a hotfix?
Answer
It might make within-folder searches that are searching folders with very few entries run more slowly. I'll update the KB to reflect this potential tradeoff.
Replies
Is this still relevant to version 11? I have a situation where the within folder search is necessary but way too slow. Initial tests of this DB update don't show much of a difference, unfortunately.
For reference, it's nearly 400,000 records all within one folder, which we just dropped into a subfolder (all records) so that opening the main, root-level folder only shows a single folder rather than loading up everything. And I know, all that in one folder makes me twitchy, but that's where we are currently.
Looping in @████████
What kinds of values are you searching for?
Exact match advanced searches without wildcards are with very few exceptions blisteringly fast (on the order of tens of milliseconds of SQL execution time). Adding any wildcards to searches on large potential result sets increases the query times by around three orders of magnitude.
Sorry, I realize I was missing a bit of context. Doing just a template search is super quick. They generally browse to a root-level folder and run a Quick Search, with Within Folder defaulted to on.
Combining template search with Within Folder makes it slower, and using the Quick Search logic combined with Within Folder is unusable. Take the screenshot below. Finding those 21 results within the folder of 400,000 (which isn't huge in the grand scheme of things) takes 45 seconds. Turning off Within Folder brought back only a few more (24 results total) and takes less than 5 seconds.
Strange. Neither Miruna nor I have an immediate idea of why that would be. If you'd like to pursue this, you can open a case with LFC Support (which will need to go to Dev) and we might be able to get back to you sometime post-Empower.
Well, one thing I've found is that our PROD SQL Server is somehow still the original release of 2014 even though DEV and TEST SQL Servers are SP3. So maybe that's causing some issues? We'll be updating to SQL 2019 in the near future, but I'm not sure just how near that is.
Don't forget to update the Compatibility Level of your Laserfiche databases to the latest available after upgrading SQL Server versions. Also, SQL Server 2022 will be reaching General Availability relatively soon, so maybe wait for that.