Overview
This article explains how to estimate the recommended size of the 360Eyes database so you can plan storage capacity before deployment.
Calculation Formula
Recommended 360Eyes DB size (GB) = B4 * B7 / 3 + B8 * (B5 / 10 + B4 / 3)
Excel version: =B4*B7/3+B8*(B5/10+B4/3)
Input Definitions
| Variable | Description |
|---|---|
| B4 | Allocated size of the CMS database repository (tables + indexes), in GB. |
| B5 | Allocated size of the Audit database repository (tables + indexes), in GB. |
| B7 | Number of CMS snapshots you want to keep. CMS snapshots include BO metadata such as users, groups, security, universes, and reports. |
| B8 | Number of Impact Analysis snapshots you want to keep. Impact Analysis snapshots (UNIVERSE, CRYSTAL, DESKI, DESKI_INFOVIEW, WEBI) store object content and usage information from audit data. Enter the number of snapshots of the same type to keep. If retention differs by type, use the maximum value. |
How to Calculate
- Collect B4 and B5 values in GB from your current SAP BO environment.
- Define your snapshot retention policy (B7 and B8).
- Apply the formula exactly as written.
- Round the result up and add a safety margin for growth.
Example
- B4 = 25 GB
- B5 = 80 GB
- B7 = 6
- B8 = 4
Calculation:
25 * 6 / 3 + 4 * (80 / 10 + 25 / 3)
= 50 + 4 * (8 + 8.33)
= 50 + 65.32
= 115.32 GB
Recommended provisioning in this example: at least 116 GB, plus additional buffer based on expected growth.
Recommendations
- Use consistent units (GB) for all inputs.
- Recalculate after major SAP BO content growth or retention changes.
- Plan extra headroom for temporary peaks during snapshot processing.