EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

Performance & Sizing Homepage


Stefan Zepeda

Salesforce Solutions Architect • Strategy


Performance is a combination of speed and scale. Speed is important because it affects the user experience. Speed is typically measured as user wait time or response time. Scale is important because it determines how many people can submit requests or reports to an analytics platform, how many reports can be supplied by the system, and how much data can be accessed.

Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.

ka0PW0000001JO3YAM_0EM4W0000029Yw6.jpeg

Server Enhancements in Update 2
With the release of the secure text input feature in, Strategy 2021 which secures all major text inputs from a consumption point of view, transaction services are one of the major remaining items that were not part of the previous scope.  Currently, when a user submits a transaction on a transaction services document, the SQL submitted is not secured via parameterized query, which is the most effective way to prevent SQL injection today. 
In 11.2.1 we introduced and enabled by default I-Cube health check for Incremental refresh, which prevents the crashed IServer to provide wrong data during the cube data query by dossier or other reports. However, when such corruptions were detected during incremental refresh, a log would be created only on the local disk and MSTR would have no clue it happened unless the customer escalated the issue to support. With this new feature, we leverage crash reporter functionality and upload their cube corruption logs to Backtrace automatically so that MSTR can proactively identify and address instances of cube corruption during incremental refresh.
In Update 2, we also focused on the improvement of the object migration workflow and ensuring Metadata Integrity. We fixed numerous defects and ran a defect pattern review to harden server operations in these scenarios.
 
 


Comment

0 comments

Details

Knowledge Article

Published:

April 7, 2017

Last Updated:

March 21, 2024