SAP Analytics Cloud – Private Versions Statistics and Analysis
Private Versions Statistics and Analysis will be general available with Wave 2022.21 and 2022.Q4 QRC Release.
How will it be deployed?
It will be deployed automatically into the side navigation under System > Performance.
It will also be deployed automatically into Files > System > Common > SAC Content.
Alongside with the Story you will find the underlying Model VERSION_STATISTICS_BASE.
What is the purpose of the Private Versions Statistics and Analysis?
As part of the ongoing project SAC Content which helps administrators to answer various questions in regards to performance, housekeeping, usage and many more we introduce the new Story Private Versions Statistics and Analysis. It helps administrators and support to get an overview of the private versions that have been created in the SAP Analytics Cloud Tenant.
Please check the existing content for the big picture and learn how you can use the content:
The information helps the administrators in both performance and housekeeping.
It aims to address potential performance issues caused by users who are currently working with planning models. We want to highlight the biggest models that are currently in use. This information enables you to make version creators aware of their versions size and the potential high memory consumption they might cause.
If a public version is in edit mode, a private version will also be created that allows you modify the data without interfering with the original version until it has been saved and thus, published. This edit mode suggests you work on the public data directly but you’re working on a copy, a private version of the data container that is only visible for you. It is called “public edit mode”. This kind of private versions created invisible during a public edit mode are known sources for potentially high memory consumption and expensive query processing because of the big amount of data. Whenever a user edits a public version, the whole data in the model is copied into an internal private version since the whole dataset needs to be prepared for potential modification. This is a common root cause for very big private versions.
To avoid this, we introduced the concept of planning areas last year. Please check the following blog post to check if you can apply it in your scenarios:
The new Private Versions Statistics and Analysis help you to identify the scenario above and other large versions.
This content will be extended with the next releases. Please stay tuned.