[RTFACT-15615] Property search on MSSQL bad performance Created: 08/Jan/18 Updated: 06/Mar/19 Resolved: 09/Dec/18
|Project:||Artifactory Binary Repository|
|Affects Version/s:||4.9.0, 5.8.2|
|Reporter:||Ariel Kabov||Assignee:||Lior Gur (Inactive)|
When running a Property Search using either REST API or AQL, when connected to MSSQL, a query similar to the following is issued:
The following part:
is redundant, as something like this should be added only if the query is limited.
The issue, is that currently this runs with a limit of 'long.MAX_VALUE', which does nothing and only harm in performance.
|Comment by Gal Ben Ami [ 04/Dec/18 ]|
Generally we have problems with the following:
|Comment by Lior Gur (Inactive) [ 06/Dec/18 ]|
I add a flag in ConstantValues : sqlServerQueryBuilderForceAddOffsetToQuery.
when the flag sets to true the generated query will be as before the fix (with offset)
|Comment by Andrei Komarov [ 06/Mar/19 ]|
One report suggested that 'update statistics' might help with faster query execution times.