Skip to Content
Sep 22, 2020 at 02:56 PM

CAP CDS Multitenancy (cds-mtx) + Rollout DB Changes



we are using cds-mtx (as described by Andrew Lunde in his blog Getting your head into Cloud Application Programming model multitenancy

Basically, on/offboarding subscription tenants works like this:

  • onboarding a subscription tenant creates the DB schema and deploys the artifacts (table definitions, initial data)
  • offboarding the tenant deletes that schema including all the data

Now having that in place, we face the next challenge:

Is there a way how an update to the data model can be deployed to all subscription tenants without destroying the data (e.g. adding a new entity and/or service, which means adding new db tables and views)