The SAP HANA Deployment Infrastructure (HDI) uses a container model to manage database development artifacts. Each HDI container, which is essentially a database schema, is associated with two distinct types of users and roles that define its operational modes: design-time and run-time.

Design-time (DT user): This context is for development and deployment. The design-time user has the necessary privileges to deploy artifacts, which involves creating, altering, or dropping database objects within the container.

Runtime (RT user): This context is for consumption and access. The run-time user has privileges to access the deployed objects, such as selecting data from tables or executing procedures, but cannot alter their structure.

This separation is a core security and lifecycle management principle within HDI.

A. Docker: Docker is an operating-system-level containerization technology, not a logical container type specific to the SAP HANA HDI service.

B. Kubernetes: Kubernetes is an orchestration platform for managing containerized applications like those in Docker; it is not an HDI container type.

1. SAP HANA Cloud

SAP HANA Database Deployment Infrastructure (HDI) Reference

Section: "HDI Containers". This document states

"For each HDI container

a set of schemas and a set of special-purpose database users (or roles) is generated... For example

a design-time user and a run-time user."

2. SAP HANA Administration Guide for SAP HANA Platform

Section: "Administering SAP HANA DI (Deployment Infrastructure)". This guide details the technical users created for an HDI container

explicitly defining the roles of the "design-time user" and the "run-time user" for object deployment and external access

respectively.