Problem Note 69850: SQL Server elasticsearch incremental indexing performance might be slower when accessing relationships or transactions that have multiple primary keys
When you incrementally index entities with more than one primary key, the query uses an AND / OR statement to fetch records.
Here is an example: If (IDA = 1 AND IDB = 1) OR (IDA = 2 AND IDB = 2) OR...
You might encounter a performance issue when more than 64 parameters are supplied to queries of this type.
This issue appears to be specific to SQL Server versions earlier than SQL Server 2022.
To circumvent this problem, you must set this consul property:
indexer/indexer.msql.hint.forceSeek = true
For SAS Visual Investigator version 10.7, that property is available with a hot fix that was released on January 26, 2023.
For SAS Visual Investigator version 10.8, that property is available with a hot fix that was released on December 12, 2022.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Visual Investigator (on SAS Viya 3.x) | Linux for x64 | 10.7 | | Viya | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2023-02-07 14:07:55 |
Date Created: | 2023-02-06 10:56:16 |