# US 10,120,886 B2 · Database integration of originally decoupled components > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,120,886 B2 - Document ID: US10120886B2 - Status: Granted - Kind: B2 - Application number: 14/798,461 - Filed: 2015-07-14 - Published: 2017-01-19 - Granted: 2018-11-06 - Earliest claimed: 2015-07-14 - Assignees: Sap SE - Applicants: Sap SE - Inventors: Peter Eberlein; Volker Driesen - Web page: https://patentgrep.com/patent/US10120886B2 ## CPC - G06F 16/211: {Schema design and management} - G06F 16/258: {Data format conversion from or to a database} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract A first component originally has a persistency decoupled from a persistency of a second component. The second component requires a table from the persistency of the first component. The first component is assigned a first database schema and the second component is assigned a second database schema. A table link is created in the second database schema of the second component, wherein the table link refers to the required table from the first database schema of the first component. ## Claims ### Claim 1 A computer system to integrate persistency of multiple components deployed in different database schemas, comprising: a memory to store a program code; a processor communicatively coupled to the memory, the processor configured to execute the program code, to: upon deploying a first component from a plurality of components, create a first persistency of the first component assigned to a first database schema; upon deploying a second component from the plurality of components, create a second persistency of the second component assigned to a second database schema, wherein the first persistency is in a decoupled state from the second persistency; read metadata of the first component to identify one or more first required tables required by the first component from the second database schema; read metadata of the second component to identify one or more second required tables required by the second component from the first database schema; create a first table link database object residing in the first database schema and a second table link database object residing in the second database schema, wherein the first table link exposes for access from the first database schema a first set of fields of the one or more first required tables stored in the second database schema, and wherein the second table link exposes for access from the second database schema a second set of fields of the one or more second required tables stored in the first database schema; and integrate the first persistency of the first component assigned to the first database schema and the second persistency of the second component assigned to the second database schema, wherein the integration of the first persistency and the second persistency provisions removing name collisions between a plurality of database objects stored in the first database schema and the second database schema. ### Claim 2 (depends on 1) The computer system of claim 1, wherein the first table link and the second table link include a type of access associated with a corresponding exposure of a corresponding components. ### Claim 3 (depends on 1) The computer system of claim 1, wherein the deployed first component is configured to be run in a first runtime environment and the second component is configured to be run in a second runtime environment, wherein the first runtime environment is different from the second runtime environment. ### Claim 4 (depends on 1) The computer system of claim 1, further comprising: based on the integration, create a first database object to join a first table stored in the first database schema with the one or more first required tables stored in the second database schema via the first table link. ### Claim 5 (depends on 4) The computer system of claim 4, wherein the first database schema and the second database schema are associated with an in-memory database. ### Claim 6 (depends on 1) The computer system of claim 1, wherein the first persistency and the second persistency are selected from a group consisting of calculation views, analytical views, stored procedures, database triggers, and database functions. ### Claim 7 A computer implemented method to integrate persistency of multiple components deployed in different database schemas, comprising: upon deploying a first component from a plurality of components, creating a first persistency of the first component assigned to a first database schema; upon deploying a second component from the plurality of components, creating a second persistency of the second component assigned to a second database schema, wherein the first persistency is in a decoupled state from the second persistency; reading metadata of the first component to identify one or more first required tables required by the first component from the second database schema; reading metadata of the second component to identify one or more second required tables required by the second component from the first database schema; creating a first table link database object residing in the first database schema and a second table link database object residing in the second database schema, wherein the first table link exposes for access from the first database schema a first set of fields of the one or more first required tables stored in the second database schema, and wherein the second table link exposes for access from the second database schema a second set of fields of the one or more second required tables stored in the first database schema; and integrating the first persistency of the first component assigned to the first database schema and the second persistency of the second component assigned to the second database schema, wherein the integration of the first persistency and the second persistency provisions removing name collisions between a plurality of database objects stored in the first database schema and the second database schema. ### Claim 8 (depends on 7) The computer implemented method of claim 7, further comprising: based on the integration, creating a first database object to join a first table stored in the first database schema with the one or more first required tables stored in the second database schema via the first table link. ### Claim 9 (depends on 7) The computer implemented method of claim 7, wherein the first persistency and the second persistency are selected from a group consisting of calculation views, analytical views, stored procedures, database triggers, and database functions. ### Claim 10 (depends on 7) The computer implemented method of claim 7, wherein the first table link and the second table link include a type of access associated with a corresponding exposure of a corresponding components. ### Claim 11 (depends on 7) The computer implemented method of claim 7, wherein the deployed first component is configured to be run in a first runtime environment and the second component is configured to be run in a second runtime environment, wherein the first runtime environment is different from the second runtime environment. ### Claim 12 (depends on 7) The computer implemented method of claim 7, further comprising: based on the integration, create a first database object to join a first table stored in the first database schema with the one or more first required tables stored in the second database schema via the first table link. ### Claim 13 A non-transitory computer readable medium storing instructions, which when executed by a processor of a computer, cause the computer to perform operations, comprising: upon deploying a first component from a plurality of components, create a first persistency of the first component assigned to a first database schema; upon deploying a second component from the plurality of components, create a second persistency of the second component assigned to a second database schema, wherein the first persistency is in a decoupled state from the second persistency; read metadata of the first component to identify one or more first required tables required by the first component from the second database schema; read metadata of the second component to identify one or more second required tables required by the second component from the first database schema; create a first table link database object residing in the first database schema and a second table link database object residing in the second database schema, wherein the first table link exposes for access from the first database schema a first set of fields of the one or more first required tables stored in the second database schema, and wherein the second table link exposes for access from the second database schema a second set of fields of the one or more second required tables stored in the first database schema; and integrate the first persistency of the first component assigned to the first database schema and the second persistency of the second component assigned to the second database schema, wherein the integration of the first persistency and the second persistency provisions removing name collisions between a plurality of database objects stored in the first database schema and the second database schema. ### Claim 14 (depends on 13) The non-transitory computer readable medium of claim 13, wherein the first table link and the second table link include a type of access associated with a corresponding exposure of a corresponding components. ### Claim 15 (depends on 13) The non-transitory computer readable medium of claim 13, wherein the deployed first component is configured to be run in a first runtime environment and the second component is configured to be run in a second runtime environment, wherein the first runtime environment is different from the second runtime environment. ### Claim 16 (depends on 13) The non-transitory computer readable medium of claim 13, further comprising: based on the integration, create a first database object to join a first table stored in the first database schema with the one or more first required tables stored in the second database schema via the first table link.