Sap Se

Eun Kyung Chi

Taesik Yoon

Jaeyun Noh

SungGun Jung

Yuchon Yi

Heeyeon Jo

Techniques and solutions are provided for executing database triggers. In particular, disclosed techniques allow for the creation of database triggers with multiple insert statements. For a trigger that includes first and second insert statements, first and second tables are created, respectively for the first and second insert statements, that each include a sequence column. At least the first insert statement references a sequence that is incremented during trigger execution. The sequence columns of the first and second tables have a number of elements corresponding to a number of times a given insert operation will execute as a result of a database operation that satisfies the conditions of the trigger. The first and second insert operations are executed using the respective first and second tables.

Trigger execution for triggers having multiple insert operations

In some embodiments, a method receives a query to retrieve data from a source table and insert the data into a target table and allocates a size of memory. A portion of the data from the source table is retrieved based on the size of memory and stored in the memory. Then, the method stores the retrieved portion of the data stored in the memory into the target table and continues to retrieve portions of data from the source table in increments based on the size of memory, store the retrieved portions of data in the memory, and store the retrieved portions of data from the memory in the target table until the data from the source table has been inserted into the target table.

Pipelined database query processing for insert query

Technologies are provided for using a multi-user execution plan cache to process database queries. A database query processor can be configured to store execution plans in a multi-user execution plan cache. The query processor can determine whether an execution plan is shareable by multiple database users. If the execution plan is shareable, it can be stored in the cache in association with a sharing user identifier. When a database query is received, the query processor can determine that the query can be performed using the cached execution plan. If the cached execution plan is shareable, the database query can determine whether the cached execution plan is valid for a database user associated with the received database query. If the cached execution plan is valid for the database user, the query processor uses the cached execution plan to perform the query for the associated database user.

Growing community of inventors

Seoul, South Korea

Eun Kyung Chi