S/4HANA Strategy & the Basis Role

In RISE with SAP, why does the basis administrator role survive even though SAP manages the technical stack?

Why do businesses that want to keep SAP support have to move to SAP S/4HANA, and by when?

A customer running S/4HANA asks whether they can keep their existing Oracle or DB2 database — what's the answer and why?

What makes SAP HANA able to run on massive data volumes without the I/O bottlenecks of a traditional disk database?

Why can't you install SAP HANA on just any server you like?

In HANA hardware sizing, what goes wrong if you underestimate vs overestimate, and which factor is hardest to get right?

Moving S/4HANA onto IaaS (AWS/Azure/GCP), which responsibilities pass to the provider and which stay with you?

What does RISE with SAP bundle, and what kind of offering is it?

How does S/4HANA Cloud private edition differ from public edition in lifecycle and control?

In the 'intelligent enterprise' model, what's the difference between O data and X data, and what connects them?

Under RISE with SAP, SAP takes responsibility from the hypervisor up to the basis layer — so what work still needs in-house or partner resources?

In RISE, system copies are automated via SAP Landscape Management — so what still falls to the basis administrator?