Database growth does not always mean business growth. Forgotten backups, tables that were never purged, temporary objects or pending housekeeping can also consume capacity, something that under RISE can end up showing up in your costs.
SAP Basis specialists · RISE/ECS experience · 15+ years of SAP experience
When a database approaches its limits, expanding capacity looks like the obvious next step. But the question worth asking first is: what is actually growing?
Runward analyzes capacity and growth trends to identify where storage is being consumed and what technical options exist before assuming you need more.
During the analysis of one environment, we found a residual table tied to a failed client copy that had never been purged.
Result specific to one case. Results depend on the conditions of each environment.
It was not an isolated case: in another environment we found old backups, forgotten SUM directories and kernel backups that were still taking up storage. Individually these can look like small operational details, but accumulated over the years they can turn into capacity the company ends up paying for.
SAP manages important components of the platform under RISE. That does not mean every piece of data, table, object and decision about what lives in the database is SAP's responsibility. Runward helps identify and manage that boundary.
Let's talk about how you are tracking growth and capacity across your SAP systems today.