Deleting Records In A Multi-Level Storage Architecture

• US 20160042016A1
• Filed: 08/14/2015
• Published: 02/11/2016
• Est. Priority Date: 04/30/2012
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Faerber, Franz, Lee, Juchang, Schreter, Ivan
• Granted Patent: US 9,740,715 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: G06F 16/215 Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
• CPC Class Codes: G06F 16/217 Database tuning G06F16/2282 takes precedence; database performance monitoring G06F11/3409
• CPC Class Codes: G06F 16/221 Column-oriented storage; Management thereof
• CPC Class Codes: G06F 16/23 Updating
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity

Abstract

Deleting a data record from the second level storage or main store is disclosed. A look-up is performed for the data record in the first level storage, where the data record is defined by a row identifier. If the row identifier is found in the first level storage, a look-up is performed for an updated row identifier representing an update of the data record in the second level storage and the main store, the update of the data record being defined by an updated row identifier. If the updated row identifier is found in the second level storage, an undo log is generated from the first level storage to invalidate a row identifier of the row identifier. A flag is generated representing an invalid updated row identifier, and a redo log is generated to restore the data record in the first level storage.

Claims

1-12. -12. (canceled)

13. A method to direct comprising:

determining whether an updated row identifier representing an update of a data record is present in a second level storage of a unified table architecture of an in-memory database having a multi-level storage architecture, the multi-level storage architecture comprising a first level storage structure to store incoming data requests in a logical row format as data records and the second level storage structure to encode and store the data records in a logical column format, the determining occurring in response to finding a row identifier for the data record in a table of the first level storage; and

,

generating an undo log to invalidate the row identifier defining the data record in the table in the first level storage or generating, by one or more processors, a redo log to restore the data record in the first level storage, the generating of the undo log occurring in response to the determining that the updated row identifier is present in the second level storage and the generating of the undo log occurring in response to determining that the updated row identifier is not present in the second level storage;

wherein the determining and the generating are performed by one or more processors.

14. The method in accordance with claim 13, wherein generating the undo log from the first level storage further comprises generating a flag representing an invalid updated row identifier.

15. The method in accordance with claim 13, further comprising recovering the data record in the first level storage during a restart if the updated row identifier is not yet persisted in a savepoint in the multi-level storage architecture.

16. The method in accordance with claim 15, further comprising generating a second invalid updated row identifier during the restart.

17. The method in accordance with claim 13, wherein the generating of the undo log comprises generating an undo log entry and writing the undo log entry into a transaction undo log for a transaction comprising deletion of the data record.

18. The method in accordance with claim 13, wherein the generating of the redo log comprises generating a redo log entry and writing the redo log entry into a database redo log for the database.

19. The method in accordance with claim 13, further comprising modifying visibility information for the table before writing an undo log entry into a transaction undo log for a transaction comprising deletion of the data record.

20. The method in accordance with claim 19, wherein if the transaction aborts, executing an undo operation to roll back the change to the visibility information for the table.

21. A computer implemented method comprising:

determining whether an updated row identifier representing an update of a data record is present in a second level storage of a unified table architecture of an in-memory database having a multi-level storage architecture, the multi-level storage architecture comprising a first level storage structure to store incoming data requests in a logical row format as data records and the second level storage structure to encode and store the data records in a logical column format, the determining occurring in response to finding a row identifier for the data record in a table of the first level storage; and

,

generating an undo log to invalidate the row identifier defining the data record in the table in the first level storage or generating, by one or more processors, a redo log to restore the data record in the first level storage, the generating of the undo log occurring in response to the determining that the updated row identifier is present in the second level storage and the generating of the undo log occurring in response to determining that the updated row identifier is not present in the second level storage;

wherein the determining and the generating are performed by one or more processors.

22. The method in accordance with claim 21, further comprising recovering the data record in the first level storage during a restart if the updated row identifier is not yet persisted in a savepoint in the multi-level storage architecture.

23. The method in accordance with claim 22, further comprising generating a second invalid updated row identifier during the restart.

24. A system comprising:

at least one programmable processor;

a non-transitory, machine-readable medium storing instructions that, when executed by the at least one processor, cause the at least one programmable processor to perform operations comprising;

determining whether an updated row identifier representing an update of a data record is present in a second level storage of a unified table architecture of an in-memory database having a multi-level storage architecture, the multi-level storage architecture comprising a first level storage structure to store incoming data requests in a logical row format as data records and the second level storage structure to encode and store the data records in a logical column format, the determining occurring in response to finding a row identifier for the data record in a table of the first level storage; and

,

generating an undo log to invalidate the row identifier defining the data record in the table in the first level storage or generating, by one or more processors, a redo log to restore the data record in the first level storage, the generating of the undo log occurring in response to the determining that the updated row identifier is present in the second level storage and the generating of the undo log occurring in response to determining that the updated row identifier is not present in the second level storage.

25. The system in accordance with claim 24, wherein generating the undo log from the first level storage further comprises operations for generating a flag representing an invalid updated row identifier.

26. The system in accordance with claim 24, wherein the operations further comprise recovering the data record in the first level storage during a restart if the updated row identifier is not yet persisted in a savepoint in the multi-level storage architecture.

27. The system in accordance with claim 26, wherein the operations further comprise generating a second invalid updated row identifier during the restart.

28. The system in accordance with claim 24, wherein the unified table memory is implemented in an in-memory database system.

29. The system in accordance with claim 24, wherein the generating of the undo log comprises generating an undo log entry and writing the undo log entry into a transaction undo log for a transaction comprising deletion of the data record.

30. The system in accordance with claim 24, wherein the generating of the redo log comprises generating a redo log entry and writing the redo log entry into a database redo log for the database.

31. The system in accordance with claim 24, wherein the operations further comprise modifying visibility information for the table before writing an undo log entry into a transaction undo log for a transaction comprising deletion of the data record.