ARCHIVING SYSTEM FOR MASSIVE DATABASES USING PRE-COMPUTED DATA LIFECYCLES

• US 20100088284A1
• Filed: 11/07/2008
• Published: 04/08/2010
• Est. Priority Date: 10/06/2008
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: CINA, Miroslav
• Granted Patent: US 8,548,954 B2
• Time in Patent Office: Days
• US Class Current: 707/665
• CPC Class Codes: G06F 11/1461 Backup scheduling policy
• CPC Class Codes: G06F 3/0605 by facilitating the interaction with a user or administrator
• CPC Class Codes: G06F 3/0649 Lifecycle management
• CPC Class Codes: G06F 3/0683 Plurality of storage devices

Abstract

An enterprise management system includes transaction/analytic applications and an archiving system in which data object lifecycles are pre-computed when the data object is created by the transaction application or analytic application. Having pre-computed the data lifecycle via the transaction/analytic applications, an archiving system need not re-determine whether the criteria for archiving are met. When the archiving system is initiated, the archiving system may identify the data objects having lifecycle dates that match the current date and archive them directly.

Claims

1. An enterprise management system, comprising:

a transaction system, comprising a transactional application and data store associated therewith, the transaction system storing business objects comprising business logic, transaction data and a lifecycle date, and

a rule set stored in association with the transaction system to be accessed by the transactional application during creation of business objects, the rule set storing data representing archiving policies for the enterprise management system,

the transactional application to generate and store lifecycle dates in the business object following access to the rule set.

2. The enterprise management system of claim 1, further comprising an archiving system that, upon execution of a batch archive process, compares lifecycle dates of stored business objects to a current date and archives business objects for which the lifecycle date is elapsed.

3. The enterprise management system of claim 2, wherein:

upon calculation of a lifecycle date and storage thereof in a business object, the transactional application stores an identifier of the respective business object in a hash table accessible by the archiving system, and

upon execution of the batch archive process at the current date, the archiving system performs the comparison only for those business objects that the hash table has linked to the current date.

4. The enterprise management system of claim 2, wherein:

upon calculation of a lifecycle date and storage thereof in a business object, the transactional application stores the calculated lifecycle date and an identifier of the respective business object in an entry of archiving index table accessible by the archiving system, and

upon execution of the batch archive process at the current date, the archiving system performs the comparison only for those business objects listed in entries that archiving index table stores in association with the current date.

5. The enterprise management system of claim 1, wherein the accessing of the rule set is triggered by user interaction with the transactional application causing a business object to be created representing a business transaction performed by a proprietor of the enterprise management system.

6. The enterprise management system of claim 1, wherein the transactional system also refers to the rule set and recalculates a lifecycle data pursuant to a transaction that accesses the business object.

8. The enterprise management system of claim 1, further comprising an archiving system that, upon execution of a batch archive process, compares lifecycle dates of stored business objects to a current date and archives business objects for which the lifecycle date is elapsed.

9. The enterprise management system of claim 8, wherein:

upon calculation of a lifecycle date and storage thereof in a business object, the analytical application stores an identifier of the respective business object in a hash table accessible by the archiving system, and

upon execution of the batch archive process at the current date, the archiving system performs the comparison only for those business objects that the hash table has linked to the current date.

10. The enterprise management system of claim 8, wherein:

upon calculation of a lifecycle date and storage thereof in a business object, the analytical application stores the calculated lifecycle date and an identifier of the respective business object in an entry of archiving index table accessible by the archiving system, and

upon execution of the batch archive process at the current date, the archiving system performs the comparison only for those business objects listed in entries that archiving index table stores in association with the current date.

11. The enterprise management system of claim 1, wherein the accessing of the rule set is triggered by user interaction with the analytical application causing a business object to be created representing a business analytic performed by a proprietor of the enterprise management system.

12. The enterprise management system of claim 1, wherein the analytical system also refers to the rule set and recalculates a lifecycle data pursuant to a transaction that accesses the business object.

7. An enterprise management system, comprising:

an analytic system, comprising an analytical application and data store associated therewith, the analytic system storing business objects comprising business logic, analytic data and a lifecycle date, and

a rule set stored in association with the analytic system to be accessed by the analytical application during creation of business objects, the rule set storing data representing archiving policies for the enterprise management system,

the analytical application to generate and store lifecycle dates in the business object following access to the rule set.

13. An archiving method, comprising:

pursuant to a user initiated transaction with an enterprise management system, creating a business object in a computer system representing the transaction, the business object storing logic defining a transaction to be performed, data collected during performance of the transaction and a lifecycle date,

determining, during performance of the transaction, a lifecycle date associated with the business object, and

storing the business object, including the logic, the collected data and the lifecycle date, in a data storage device associated with a transaction system of the enterprise management system,

upon execution of a batch process of an archiving system;

comparing the lifecycle date to a current date, and

if the lifecycle date has elapsed, archiving the business object and removing it from the data storage device associated with a transaction system.

14. The method of claim 13, further comprising:

upon calculation of the lifecycle date and storage of the business object, storing an identifier of the respective business object in a hash table accessible by the archiving system, and

upon execution of the batch process at the current date, identifying business objects linked by the hash table to the current date and performing the comparing and archiving only for those identified business objects.

15. The method of claim 13, further comprising:

upon calculation of the lifecycle date and storage of the business object, storing an identifier of the respective business object in a archiving index table accessible by the archiving system, and

upon execution of the batch process at the current date, identifying business objects linked by the archiving index table to the current date and performing the comparing and archiving only for those identified business objects.

16. The method of claim 13, wherein the archiving comprises copying the business object from the data storage device associated with the transaction system to an archiving storage device and deleting the business object from the data storage device associated with the transaction system.

17. The method of claim 13, wherein the archiving comprises deleting the business object from the data storage device associated with the transaction system.

18. The method of claim 13, wherein the determining comprises:

accessing a stored rule set,

identifying an archiving policy to be used based on a type of business object, and

calculating the lifecycle date according to the archiving policy.

19. The method of claim 13, further comprising recalculating a lifecycle data pursuant to a second user-initiated transaction that accesses the business object.