Sap Ag

Sap Se

Tobias Wenner

Dirk Debertin

Andreas Blumenthal

Christian Stork

Andrey Engelko

Dietmar Theobald

Wieland Hoprich

Kerstin Hoeft

Torsten Ziegler

Frank-Martin Haas

Andrea Neufeld

Ralf Kuersch

Thomas Raupp

Christian Fecht

Jemin Tanna

Matthias Schwarz

Rainer Schweigkoffer

Ulrich Koch

Klaus Daschakowsky

Cornelia Haase

Harald Kuck

Christian Hansen

Hartwig Brand

Carsten Dietze-Selent

Peter Goebbels

Uwe Hommel

Jens Otto

Michael Schafft

Guenther Drach

In one general aspect, a computer system can include instructions stored on a non-transitory computer-readable storage medium. The computer system can include a logging table generator configured to generate a logging table corresponding with an original table targeted for an upgrade, and a control table generator configured to generate a control table configured to store a version identifier for changes logged in the logging table. The computer system can include a change recorder configured to receive an indicator of a change to a record of the original table during execution of at least a portion of the upgrade of the original table, and a key recorder configured to store in the logging table a primary key identifying the record of the original table and the version identifier stored in the control table.

Change data capturing during an upgrade

Techniques for optimizing a software application include receiving, at a local computing system, a query from an application for data stored on a database table, the query including a context defined by a name of the database table; comparing the context of the query to a context of a predefined query scenario; based on the context of the query matching the context of the predefined query scenario, retrieving data stored on a secondary database replicated from data stored on a main database; and passing the retrieved data from the secondary database to the application.

Optimizing software applications

According to some embodiments, a programming language in an application server may access different database server implementations, wherein the programming language accesses content of database tables via work areas derived from the database tables. A database table may be mapped to a work area such that each column in the database table is mapped to a corresponding component of the work area (having a default component type based on the column type of the associated column). It may be determined that a particular column in the database table is to store large object data content, and a new mapping to a work area may be defined such that a particular column maps to a corresponding component having a component type other than the default component type.

Systems and methods for mapping large object data content in a database table to a work area

According to some embodiments, a programming language in an application server may include access to different database server implementations, wherein the programming language accesses content of database tables via work areas derived from the database tables. A database table, having columns to store content, each column being associated with a column type, may be mapped to a work area such that, at a database server, each column in the database table is mapped to a corresponding component of the work area, the corresponding component having a default component type based on the column type of the associated column in the database table. It may be determined that a particular column in the database table is to store large object data content, and, in response to the determination, a new mapping to a work area may be defined such that the particular column maps to a corresponding component having a component type other than the default component type.

Systems and method for mapping large object data content in a database table to a work area

In an embodiment, a database interface performs a three-step optimistic database access. The database interface initially performs an optimistic read of a database object. The database object is checked for consistency after the optimistic read. If the database object is inconsistent, a first pessimistic read is performed with an isolation level that does not guarantee consistency (e.g., with an isolation level of committed read). The database object is checked again for consistency after the first pessimistic read. If the database object is inconsistent, a second pessimistic read is performed with an isolation level that may guarantee consistency (e.g., with an isolation level of repeatable read).

System and method for an optimistic database access

A system and method for synchronizing distributed table buffers is disclosed. A node may contain a synch manager and a table buffer having a synch identifier. The synch manager may use the synch identifier to coordinate updates to the table buffer. The updates to the table buffer may be performed in an asynchronous and/or a synchronous manner.

System and method for synchronizing distributed buffers when committing data to a database

Growing community of inventors

Nussloch, Germany

Tobias Wenner