In-memory database for multi-tenancy

摘要

An in-memory database server hosting a tenant of a multi-tenant software architecture can receive a definition of a custom data field that is unique to an organization having isolated access to the tenant. The custom data field can extend a standard table defined by central metadata stored at a system tenant of the multi-tenant software architecture. Tenant private metadata that includes the definition can be stored in memory accessible only to the tenant. A tenant-dependent table that includes the custom data field can be formed, for example by retrieving central metadata defining the standard table from the system tenant and adding the custom data field using the definition. The tenant-dependent table can be presented for access via a database client at the organization. Related systems, articles of manufacture, and computer-implemented methods are disclosed.

主权项

1. A computer program product comprising a non-transitory machine-readable medium storing instructions that, when executed by at least one programmable processor, cause the at least one programmable processor to perform operations comprising:
receiving, at an in-memory database server hosting a tenant of a multi-tenant software architecture, a definition of a custom data field that is unique to an organization having isolated access to the tenant, the custom data field extending a standard table defined by central metadata stored at a system tenant of the multi-tenant software architecture; storing, in the in-memory database server rather than in a disk-based storage, tenant private metadata comprising the definition, wherein the tenant private metadata is only accessible to the tenant, wherein the in-memory database server is hosted on a virtual machine of a host computer system, wherein the in-memory database comprises an in-memory column engine that uses a column format for storage and an in-memory row engine that uses a row format for storage, the in-memory row engine being configured to exchange an intermediate row result with the in-memory column engine by providing the intermediate row result materialized as a complete row, and the in-memory column engine being configured to exchange an intermediate column result with the in-memory row engine by exposing the intermediate column result using an iterator interface; forming a tenant-dependent table comprising the custom data field, the forming comprising retrieving, from the system tenant, central metadata defining the standard table and adding the custom data field using the definition; and presenting the tenant-dependent table for access via a database client at the organization.