This article describes an issue where security filters indirectly related to attributes present on a grid using data blending would not apply. For more information, please contact Strategy Technical Support.
CAUSE:
This is a known security defect in Strategy 10.4.x and earlier versions.
ACTION:
This has been fixed in Strategy 10.5 and above. Upgrade to take advantage of the fix.
Starting Strategy 10.5, as part of the security defect fix, performance degradation may be observed in some cases where the security filter application does not reduce the number of rows significantly. It’s because the Security Filter is applied while data is being fetched from the dataset, and the entire table is scanned to apply the security filter, however, the cost of scanning table is not negated by the reduced number of rows as part of the Security Filter application.
This Performance degradation is fixed in Strategy 10.10 and above by not applying the Security Filter while fetching data from the dataset but rather apply later in the data Blending scenarios. However, this behavior can lead to different performance problems where the data that is fetched from the dataset is too large (without Security Filter not being applied just yet), and joining this data to another dataset in Data Blending cases may lead to “Intermediate results rows exceed” governing error.
This erroneous behavior is addressed in Strategy 2019 Update 5 and Strategy 2020 Update 1 by getting back to the same behavior as 10.5. The fix is based on the assumption to apply the security filter as early as possible to reduce the number of rows to do further join with other datasets. This also implies that performance degradation may be observed in some cases where the security filter application does not reduce the number of rows significantly.
Strategy Internal Reference number for this technical note is KB442145 and DE39508.
