Hierarchal data management

• US 20060206507A1
• Filed: 02/16/2006
• Published: 09/14/2006
• Est. Priority Date: 02/16/2005
• Status: Abandoned Application

• Current Assignee: Ziyad M. Dahbour
• Original Assignee: Ziyad M. Dahbour
• Inventors: Dahbour, Ziyad M.
• Application Number:
  US11/357,617
• Publication Number:
  US 20060206507A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/288 Entity relationship models
• CPC Class Codes: G06F 16/9024 Graphs; Linked lists G06F16/9027 takes precedence

Abstract

A hierarchal data management system for a storage device includes an entity relationship discover to generate meta data from a business object, a file manager to create a partition based on the metadata, a data mover to generate a logical partitioning key and to store the logical partitioning key in the metadata for the partition. The file manager includes a data management policy to define a data class and a storage policy to map the data class to the storage device to form a partition table.

Claims

1. A hierarchal data management system for a storage device, comprising:

an entity relationship discover to generate meta data from a business object;

a file manager to create a partition based on said metadata; and

a data mover to generate a logical partitioning key and to store the logical partitioning key in said metadata for said partition, said file manager including a data management policy to define a data class and a storage policy to map said data class to said storage device to form a partition table.

2. The hierarchal data management system of claim 1, further comprising a data mover configured to convert a table of said business object to a partition table corresponding to said partition.

3. The hierarchal data management system of claim 1, further comprising a data subsetter configured to generate a reduced in size copy of said partition table.

4. The hierarchal data management system of claim 1, wherein the data management policy includes transparent access and secure access to data and said secured access and said transparent access is managed by an access layer.

5. The hierarchal data management system of claim 1, further comprising a migrator configured to mitigate and convert a legacy system to the hierarchical data management system.

6. The hierarchal data management system of claim 1, further comprising a re-organizer configured to analyze said metadata and re-organized a portion of said metadata.

7. The hierarchal data management system of claim 1, further including a partition mover configured to move said partition to a different tier of said storage device.

8. The hierarchal data management system of claim 7, wherein said partition mover is configured to move said partition to a different level of said storage device in accordance with said storage policy.

9. The hierarchal data management system of claim 1, wherein said data class and storage policy are configured to map data to either the partition table or another partition table responsive to a date of the data.

10. The hierarchal data management system of claim 1, wherein said data class and storage policy are configured to map data to either the partition table or another partition table responsive to how frequently the data is accessed.

11. A method for forming a hierarchal data management system for a storage device, comprising the steps of:

generating meta data from a business object;

creating a partition based on said metadata;

generating a logical partitioning key and storing the logical partitioning key in said metadata for said partition;

forming a data management policy to define a data class; and

defining a storage policy to map said data class to said storage device to form a partition table.

12. The method of claim 11, further comprising converting a table of said business object to a partition table corresponding to said partition.

13. The method of claim 11, further comprising generating a reduced in size copy of said partition table.

14. The method of claim 11, further comprising obtaining transparent access and secure access to data and said secured access and said transparent access is managed by an access layer.

15. The method of claim 11, further comprising migrating and converting a legacy system to the hierarchical data management system.

16. The method of claim 11, further comprising analyzing said metadata and re-organizing a portion of said metadata.

17. The method of claim 11, further including moving said partition to a different tier of said storage device.

18. The method of claim 17, wherein said partition mover moves said partition to a different level of said storage device in accordance with said storage policy.

19. The method of claim 11, wherein the storage policy is configured to map data to different partition tables responsive to a date of the data.

20. A system comprising:

a first database partition stored on a first storage device and configured to store data, the first data being within a first date range;

a second database partition stored on a second storage device and configured to store second data, the second data being within a second date range, the first storage device having a faster physical access time than the second storage device, the second date range being prior to the first date range;

a global data table comprising the first database partition and the second database partition, the first database partition and the second database partition being transparent to a user;

partition meta data including a logical partitioning key configured for determining if data should be stored in alternatively the first database partition or the second database partition, the logical partition key being further configured for controlling the visibility of the first data and the second data to a user; and

a data management policy configured for using the first database partition and the second database partition to archive the second data without removing the second data from the global data table.