US20090083340A1 - Customizable metadata merging framework - Google Patents

Customizable metadata merging framework Download PDF

Info

Publication number
US20090083340A1
US20090083340A1 US12323062 US32306208A US2009083340A1 US 20090083340 A1 US20090083340 A1 US 20090083340A1 US 12323062 US12323062 US 12323062 US 32306208 A US32306208 A US 32306208A US 2009083340 A1 US2009083340 A1 US 2009083340A1
Authority
US
Grant status
Application
Patent type
Prior art keywords
version
metadata associated
database object
metadata
object
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
US12323062
Other versions
US8103641B2 (en )
Inventor
Rajagopal Baskaran
Jaime E. Singson
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Oracle International Corp
Original Assignee
Oracle International Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F17/00Digital computing or data processing equipment or methods, specially adapted for specific functions
    • G06F17/30Information retrieval; Database structures therefor ; File system structures therefor
    • G06F17/30286Information retrieval; Database structures therefor ; File system structures therefor in structured data stores
    • G06F17/30289Database design, administration or maintenance
    • G06F17/30309Managing data history or versioning
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99941Database schema or data structure
    • Y10S707/99942Manipulating data structure, e.g. compression, compaction, compilation
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99951File or database maintenance
    • Y10S707/99952Coherency, e.g. same view to multiple users
    • Y10S707/99954Version management

Abstract

One embodiment of the present invention provides a system that facilitates merging different versions of a database object. During operation, the system receives metadata associated with a first version of a database object and a second version of the database object. The system then compares metadata associated with the first version with metadata associated with the second version to create a difference report. Next, the system uses the different report to create an action plan that specifies how to merge the metadata associated with the first and second versions of the metadata object.

Description

    RELATED APPLICATION
  • This application is a continuation application of application Ser. No. 10/749,037, Attorney Docket Number OR03-11001, entitled “Customizable Metadata Merging Framework,” by inventors Rajagopal Baskaran and Jaime E. Singson, filed 29 Dec. 2003.
  • BACKGROUND
  • 1. Field of the Invention
  • The present invention relates to metadata that is used to define objects in databases. More specifically, the present invention relates to a method and an apparatus that facilitates merging metadata associated with different versions of objects of a database in a customizable manner.
  • 2. Related Art
  • Databases typically form the backbone of modern electronic business solutions. As business requirements change over time or are modified to meet local requirements, corresponding modifications may need to occur in the structure of an underlying database. These modifications can cause different versions of the same database to diverge over time. This can cause problems when divergent versions of a database need to be subsequently reconciled or updated.
  • Database objects are typically defined using metadata. The properties, attributes, and relationship of a database object with other database objects can be described using the unified modeling language (UML). The structure of metadata can be modeled using UML (Unified Modeling Language) to define a series of classes, associations, and attributes. For instance, a Table is a Class, a Column is a Class, and a Partition is a Class. ‘Name’ is an Attribute that exists for a Table, Column, and a Partition Class. A relationship exists between Table and Column (a table owns a column), and so we say there is an Association between the Table Class and Column Class. An end user typically receives metadata that defines a database object, for example a table, from a solutions provider. After receiving this metadata, the end user can typically customize the metadata to change the structure of the metadata object. For example, an end user may customize the metadata to add an additional column to a table or to change a property of the table.
  • It is possible for different end users to customize the same metadata in different ways. For example, end users in a multi-national corporation located in different jurisdictions may customize metadata to allow a corresponding database to accommodate specific data items required by their local jurisdictions.
  • In some circumstances, it is desirable to merge different versions of metadata. For example, a solutions provider may generate a new version of the metadata to enhance the database object, or management may want the metadata for two or more databases to be merged. This merging process is presently performed manually, and consequently involves a significant amount of time and effort.
  • Hence, what is needed is a method and an apparatus that facilitates merging different versions of a database without the problems described above.
  • SUMMARY
  • One embodiment of the present invention provides a system that facilitates merging different versions of a database object. During operation, the system receives metadata associated with a first version of a database object and a second version of the database object. The system then compares metadata associated with the first version with metadata associated with the second version to create a difference report. Next, the system uses the different report to create an action plan that specifies how to merge the metadata associated with the first and second versions of the metadata object.
  • In a variation of this embodiment, metadata associated with the database objects are represented in Unified Modeling Language (UML).
  • In a further variation, comparing the metadata associated with the first and second versions of the database object involves allowing a user to specify which associations of the database object needs to be compared.
  • In a further variation, comparing the metadata associated with the first and second versions of the database object involves allowing the user to specify how to compare the metadata for each association in the database object.
  • In a further variation, creating the action plan involves allowing a user to select which actions to take in merging the metadata in order to produce merged metadata with the desired properties and attributes.
  • In a further variation, creating the action plan involves examining the difference report to determine what actions to take in bringing the metadata associated with the first version and second versions of the database object into agreement.
  • In a variation of this embodiment, the metadata associated with the first and second versions of the database object can define Oracle database objects like Dimensions, Cubes, Tables, Views, Materialized views, Transformations, and their associated objects. An example of associated objects is that Column, Foreign Keys, and Unique Keys can be associated with table metadata definition. Oracle is a trademark or registered trademark of Oracle International Corporation.
  • In a variation of this embodiment, the action plan can specify a number of actions including creating, updating, and deleting of database objects.
  • BRIEF DESCRIPTION OF THE FIGURES
  • FIG. 1 illustrates a metadata exchange framework in accordance with an embodiment of the present invention.
  • FIG. 2 illustrates the process of creating a difference report from compatible objects in accordance with an embodiment of the present invention.
  • FIG. 3 illustrates the process of creating a difference report from non-compatible objects in accordance with an embodiment of the present invention.
  • FIG. 4 illustrates the process of creating an action plan and a merged object in accordance with an embodiment of the present invention.
  • FIG. 5 illustrates source and target objects in accordance with an embodiment of the present invention.
  • FIG. 6 illustrates a difference report in accordance with an embodiment of the present invention.
  • FIG. 7 illustrates an action plan in accordance with an embodiment of the present invention.
  • FIG. 8 presents a flowchart illustrating the process of merging metadata associated with a first object and a second object in accordance with an embodiment of the present invention.
  • DETAILED DESCRIPTION
  • The following description is presented to enable any person skilled in the art to make and use the invention, and is provided in the context of a particular application and its requirements. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present invention. Thus, the present invention is not limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.
  • The data structures and code described in this detailed description are typically stored on a computer-readable storage medium, which may be any device or medium that can store code and/or data for use by a computer system. The computer-readable storage medium includes, but is not limited to, volatile memory, non-volatile memory, magnetic and optical storage devices such as disk drives, magnetic tape, CDs (compact discs), DVDs (digital versatile discs or digital video discs), or other media capable of storing computer-readable media now known or later developed.
  • The methods and processes described in the detailed description section can be embodied as code and/or data, which can be stored in a computer-readable storage medium as described above. When a computer system reads and executes the code and/or data stored on the computer-readable storage medium, the computer system perform the methods and processes embodied as data structures and code and stored within the computer-readable storage medium.
  • Furthermore, the methods and processes described below can be included in hardware modules. For example, the hardware modules can include, but are not limited to, application-specific integrated circuit (ASIC) chips, field programmable gate arrays (FPGAs), and other programmable-logic devices now known or later developed. When the hardware modules are activated, the hardware modules perform the methods and processes included within the hardware modules.
  • Metadata Exchange Strategy Framework
  • FIG. 1 illustrates a metadata exchange strategy framework 102 in accordance with an embodiment of the present invention. Metadata exchange strategy framework 102 includes metadata change manager 110, metadata exchange strategy 112, and execution engine 114. Metadata change manager 110 provides functions for creating difference reports, such as difference report 108, as described below in conjunction with FIGS. 2, 3, 5, and 8. Metadata exchange strategy 112 provides functions for creating an action plan, such as action plan 113, as described below in conjunction with FIGS. 4, 6, 7, and 8. Execution engine 114 provides functions for executing the action plan as described below in conjunctions with FIGS. 4 and 8
  • Metadata exchange strategy framework 102 accepts source object 104 and target object 106 and creates merged object 108. Source object 104, target object 106, and merged object 108 contain metadata describing respective database objects. Source object 104 and target object 108 are descriptions of the same database object that differ, possibly because their metadata definition may have been updated or customized by different users.
  • Source object 102 and target object 106 are typically Oracle database objects and not just tables and columns (i.e. cubes, transformations, and the like). Also source object 102 and target object 106 may include other objects such as files in a file system or records in a file that have been captured using UML and stored in the database during design time. This is typically achieved by having a table called “file” and a table called “record.” The metadata of external table objects refers to the record metadata in the record table. These are not database objects, but still dictate the structure of some database objects. For example the structure of an external table is dictated by the file and record that it is referring to. Hence, there exists a requirement that external tables have to be merged form the record during design time, although recorded is not a database object. Hence, this is not just restricted to database objects but also to others that are marked in UML and stored in the database as classes, attributes, and associations.
  • Difference Report
  • FIG. 2 illustrates the process of creating a difference report from compatible objects in accordance with an embodiment of the present invention. Metadata change manager 110 receives external tables 202 and 204 and creates a difference report 208, which describes the differences between external tables 202 and 204. For example, external tables 202 and 204 contain metadata describing the same object that differ possibly because one of the external tables is an updated version of the other external table, or because the external tables have been customized by different individuals.
  • Difference Report from Non-Compatible Objects
  • FIG. 3 illustrates the process of creating a difference report from non-compatible objects in accordance with an embodiment of the present invention. In the example illustrated in FIG. 3, a difference report between external table 202 and record 302 is desired. Note that external table 202 may have been originally created from record 302.
  • Adapter 304 first converts record 302 into compatible external table 306. Metadata change manager 110 then receives external tables 202 and 306 and creates a difference report 308, which describes the differences between external tables 202 and record 302, which are ultimately the differences between external table 202 and record 302.
  • Action Plan and Merged Object
  • FIG. 4 illustrates the process of creating an action plan and a merged object in accordance with an embodiment of the present invention. Metadata exchange strategy 112 receives a difference report 208 created by metadata change manager 110. During this process, metadata exchange strategy 112 is used to examine difference report 208 and to create an action plan 404 for merging the two objects used in creating difference report 208.
  • Next, execution engine 114 receives action plan 404. After a user selects which items of action 404 are to be performed, execution engine 114 creates merged object 108.
  • Creation of an action plan requires the user to specify if a merge or a replace plan is preferred. The replace plan means deleting everything form the target the does not have a match in the source, while the merge plan would not allow deletion of anything from the target.
  • After the action plan has been created, the user can customize the action plan to apply the specific actions that are desired. Applying the action plan causes creation, deletion, or updates of the target object. Also, the user has the ability to specify which attributes in the target that need to be3 updated in the event of create or update in the target. The user can also change the values to suit the required needs. This is determined at the time when the user wants to execute the created action plan.
  • Source and Target Objects
  • FIG. 5 illustrates source and target objects in accordance with an embodiment of the present invention. These source and target objects include metadata for table 508 and table 502, respectively, and originated from the same metadata. Source table 508 includes a description 509 of table 508. Additionally, source table 508 is associated with columns 512 and properties 510. Properties 510 include property 2 and property 3, and columns 512 include column 1, column 2, and column 3. Together, table 508, properties 510, and columns 512 describe a corresponding database table.
  • Target table 502 includes a description 503 of table 502. Additionally, target table 502 is associated with columns 506 and properties 504. Properties 504 includes property 1, and columns 506 include column 1 and column 2. Together, table 502, properties 504, and columns 506 describe a corresponding database table. Note that any mapping between columns 506 of table 502 and columns 512 of table 508 is possible. For example, column 1 of columns 506 and column 2 of columns 512 may refer to the same data, while column 2 of columns 506 and column 1 of columns 512 may also refer to the same data.
  • Difference Report
  • FIG. 6 illustrates a difference report 208 in accordance with an embodiment of the present invention. Note that there are many ways to compare different components of the metadata. In this example, tables are being compared by name, columns are being compared by position, and properties are being compared by name.
  • Difference report 208 includes data for the parameters being compared, in this example table name, column position, and properties. The comparison of the table names indicates that the target and source have the same name; therefore the input into the action plan is to update the table.
  • The comparison of the columns indicates that column 1 in the target includes the same data as column 2 in the source and that column 2 in the target includes the same data as column 1 in the source. The input to the action plan is to update the column descriptions. Since column 3 exists in the source but not in the destination, the input to the action plan is to create column 3 in the target.
  • The comparison of the properties indicates that property 1 exists in the target but not in the source, while properties 2 and 3 exist in the source but not in the destination. The action plan for the properties includes deleting property 1 and creating properties 2 and 3. These actions will bring the target into alignment with the source if the user selects all of the actions as described below in conjunction with FIG. 7.
  • Action Plan
  • FIG. 7 illustrates an action plan 404 in accordance with an embodiment of the present invention. Action plan 404 includes actions derived from difference report 208 described above in conjunction with FIG. 6. Each line of action plan 404 includes a checkbox 702, a description of the action 704, and an action 706. A user can select which actions are required by checking the checkbox in column 702. After the user checks the actions, execution engine 114 performs the checked actions.
  • Merging Metadata
  • FIG. 8 presents a flowchart illustrating the process of merging metadata associated with a first object and metadata associated with a second object in accordance with an embodiment of the present invention. The system starts when a first metadata associated with the first version of an object is received (step 802). Next, the system receives the second metadata associated whit the second version of the object (step 804). Note that steps 802 and 804 can occur in the opposite order or simultaneously. If needed, the system converts the second metadata to be compatible with the first metadata (step 806).
  • After receiving the first metadata and the second metadata, the system examines the first metadata and the second metadata to create a difference report (step 808). The system then creates an action plan from the difference report (step 810).
  • Next, the system allows a user to select portions of the action plan to implement by checking checkboxes in the action plan (step 812). Finally, the system uses the selected actions to merge the first metadata and the second metadata to create merged metadata (step 814).
  • The foregoing descriptions of embodiments of the present invention have been presented for purposes of illustration and description only. They are not intended to be exhaustive or to limit the present invention to the forms disclosed. Accordingly, many modifications and variations will be apparent to practitioners skilled in the art. Additionally, the above disclosure is not intended to limit the present invention. The scope of the present invention is defined by the appended claims.

Claims (21)

  1. 1. A computer implemented method to facilitate merging different versions of a database object, comprising:
    receiving metadata associated with a first version of the database object and a second version of the database object;
    creating a difference report by comparing the metadata associated with the first version of the database object with metadata associated with the second version of the database object;
    creating an action plan from the difference report, wherein the action plan specifies how to merge metadata associated with the first version of the database object with metadata associated with the second version of the database object;
    receiving an indication of which actions to take in merging metadata in order to produce merged metadata with desired properties and attributes; and
    facilitating merging the metadata associated with the first version of the database object with the metadata associated with the second version of the object based on the action plan, wherein the first version and second version of the database object include other objects.
  2. 2. The method of claim 1, wherein metadata associated with the first version and the second version of the database object are represented in Unified Modeling Language.
  3. 3. The method of claim 1, wherein comparing metadata associated with the first version and second version of the database object involves customizing which associations to compare.
  4. 4. The method of claim 1, wherein comparing metadata associated with the first version and second version of the database object involves customizing how to compare the first metadata and the second metadata.
  5. 5. The method of claim 1, wherein creating the action plan involves examining the difference report to determine what actions to take in bringing metadata associated with the first version and second versions of the database object into agreement.
  6. 6. The method of claim 1, wherein metadata associated with first and second versions of the metadata object can define database objects, wherein database objects include tables, columns, dimensions, cube, views, materialized views, and external tables.
  7. 7. The method of claim 1, wherein the action plan can specify a number of actions including creating, updating, and deleting database objects, and their properties.
  8. 8. A computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method to facilitate merging different versions of a database object, the method comprising:
    receiving metadata associated with a first version of the database object and a second version of the database object;
    creating a difference report by comparing the metadata associated with the first version of the database object with metadata associated with the second version of the database object;
    creating an action plan from the difference report, wherein the action plan specifies how to merge metadata associated with the first version of the database object with metadata associated with the second version of the database object;
    receiving an indication of which actions to take in merging metadata in order to produce merged metadata with desired properties and attributes; and
    facilitating merging the metadata associated with the first version of the database object with the metadata associated with the second version of the object based on the action plan, wherein the first version and second version of the database object include other objects.
  9. 9. The computer-readable storage medium of claim 8, wherein metadata associated with the first version and the second version of the database object are represented in Unified Modeling Language.
  10. 10. The computer-readable storage medium of claim 8, wherein comparing metadata associated with the first version and second version of the database object involves customizing which associations to compare.
  11. 11. The computer-readable storage medium of claim 8, wherein comparing metadata associated with the first version and second version of the database object involves customizing how to compare the first metadata and the second metadata.
  12. 12. The computer-readable storage medium of claim 8, wherein creating the action plan involves examining the difference report to determine what actions to take in bringing metadata associated with the first version and second versions of the database object into agreement.
  13. 13. The computer-readable storage medium of claim 8, wherein metadata associated with first and second versions of the metadata object can define database objects, wherein database objects include tables, columns, views, dimensions, and cubes.
  14. 14. The computer-readable storage medium of claim 8, wherein the action plan can specify a number of actions including creating, updating, and deleting database objects and their properties.
  15. 15. An apparatus to facilitate merging different versions of a database object, comprising:
    a processor;
    a memory;
    a receiving mechanism configured to receive metadata associated with a first version of the database object and a second version of the database object;
    a difference-report-creating mechanism configured to create a difference report by comparing the metadata associated with the first version of the database object with metadata associated with the second version of the database object;
    an action-plan creating mechanism configured to create an action plan from the difference report that specifies how to merge metadata associated with the first version of the database object with metadata associated with the second version of the database object;
    a receiving mechanism configured to receive an indication of which actions to take in merging metadata in order to produce merged metadata with desired properties and attributes; and
    a merging mechanism configured to facilitate merging the metadata associated with the first version of the database object with the metadata associated with the second version of the object based on the action plan.
  16. 16. The apparatus of claim 15, wherein metadata associated with the first version and the second version of the database object are represented in Unified Modeling Language.
  17. 17. The apparatus of claim 15, wherein comparing metadata associated with the first version and second version of the database object involves customizing which associations to compare.
  18. 18. The apparatus of claim 15, wherein comparing metadata associated with the first version and second version of the database object involves customizing how to compare the first metadata and the second metadata.
  19. 19. The apparatus of claim 15, wherein creating the action plan involves examining the difference report to determine what actions to take in bringing metadata associated with the first version and second versions of the database object into agreement.
  20. 20. The apparatus of claim 15, wherein metadata associated with first and second versions of the metadata object can define tables, columns, properties of tables, and properties of columns.
  21. 21. The apparatus of claim 15, wherein the action plan can specify a number of actions including creating, updating, and deleting tables, columns, or properties.
US12323062 2003-12-29 2008-11-25 Customizable metadata merging framework Active 2025-05-13 US8103641B2 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US10749037 US7469262B2 (en) 2003-12-29 2003-12-29 Customizable metadata merging framework
US12323062 US8103641B2 (en) 2003-12-29 2008-11-25 Customizable metadata merging framework

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US12323062 US8103641B2 (en) 2003-12-29 2008-11-25 Customizable metadata merging framework

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10749037 Continuation US7469262B2 (en) 2003-12-29 2003-12-29 Customizable metadata merging framework

Publications (2)

Publication Number Publication Date
US20090083340A1 true true US20090083340A1 (en) 2009-03-26
US8103641B2 US8103641B2 (en) 2012-01-24

Family

ID=34711014

Family Applications (2)

Application Number Title Priority Date Filing Date
US10749037 Active 2025-08-20 US7469262B2 (en) 2003-12-29 2003-12-29 Customizable metadata merging framework
US12323062 Active 2025-05-13 US8103641B2 (en) 2003-12-29 2008-11-25 Customizable metadata merging framework

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10749037 Active 2025-08-20 US7469262B2 (en) 2003-12-29 2003-12-29 Customizable metadata merging framework

Country Status (1)

Country Link
US (2) US7469262B2 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120166470A1 (en) * 2010-12-22 2012-06-28 Dirk Baumgaertel Systems and methods providing touchscreen report navigation
US20140053091A1 (en) * 2012-08-20 2014-02-20 Microsoft Corporation Data Exploration User Interface
US10001897B2 (en) 2012-08-20 2018-06-19 Microsoft Technology Licensing, Llc User interface tools for exploring data visualizations

Families Citing this family (43)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7469262B2 (en) * 2003-12-29 2008-12-23 Oracle International Corporation Customizable metadata merging framework
US7343356B2 (en) 2004-04-30 2008-03-11 Commvault Systems, Inc. Systems and methods for storage modeling and costing
US8266406B2 (en) 2004-04-30 2012-09-11 Commvault Systems, Inc. System and method for allocation of organizational resources
US8005792B2 (en) * 2004-05-14 2011-08-23 Oracle International Corporation System and method for managing versions of metadata
US7698310B2 (en) * 2004-05-14 2010-04-13 Oracle International Corporation System for allowing object metadata to be shared between cursors for concurrent read write access
US7620644B2 (en) * 2004-10-19 2009-11-17 Microsoft Corporation Reentrant database object wizard
US20060190501A1 (en) * 2005-02-18 2006-08-24 Sandy Massironi System supporting data repository compatibility
US20060277225A1 (en) * 2005-06-07 2006-12-07 Mark Timothy W Converting file system metadata structure while the file system remains available
US7613752B2 (en) 2005-11-28 2009-11-03 Commvault Systems, Inc. Systems and methods for using metadata to enhance data management operations
US20110010518A1 (en) 2005-12-19 2011-01-13 Srinivas Kavuri Systems and Methods for Migrating Components in a Hierarchical Storage Network
US7870355B2 (en) 2005-12-19 2011-01-11 Commvault Systems, Inc. Log based data replication system with disk swapping below a predetermined rate
US8655850B2 (en) 2005-12-19 2014-02-18 Commvault Systems, Inc. Systems and methods for resynchronizing information
US8572330B2 (en) * 2005-12-19 2013-10-29 Commvault Systems, Inc. Systems and methods for granular resource management in a storage network
US7651593B2 (en) 2005-12-19 2010-01-26 Commvault Systems, Inc. Systems and methods for performing data replication
US8930496B2 (en) 2005-12-19 2015-01-06 Commvault Systems, Inc. Systems and methods of unified reconstruction in storage systems
US7606844B2 (en) 2005-12-19 2009-10-20 Commvault Systems, Inc. System and method for performing replication copy storage operations
US8726242B2 (en) * 2006-07-27 2014-05-13 Commvault Systems, Inc. Systems and methods for continuous data replication
US8677091B2 (en) * 2006-12-18 2014-03-18 Commvault Systems, Inc. Writing data and storage system specific metadata to network attached storage device
US20080172400A1 (en) * 2007-01-11 2008-07-17 Microsoft Corporation Techniques to manage an entity model
US20080209007A1 (en) * 2007-02-27 2008-08-28 Tekelec Methods, systems, and computer program products for accessing data associated with a plurality of similarly structured distributed databases
US20080275895A1 (en) * 2007-05-03 2008-11-06 Leroux Daniel D Method, system, and program product for aligning models
US7613745B2 (en) 2007-05-25 2009-11-03 International Business Machines Corporation Method of aligning meta-models
US8140474B2 (en) * 2007-09-13 2012-03-20 Intel Corporation Aggregation of file/directory structures
US8296733B2 (en) * 2007-09-20 2012-10-23 Siemens Aktiengesellschaft Systems, devices, and/or methods for managing program logic units
US8903842B2 (en) * 2007-10-26 2014-12-02 Microsoft Corporation Metadata driven reporting and editing of databases
US8239417B2 (en) * 2008-08-07 2012-08-07 Armanta, Inc. System, method, and computer program product for accessing and manipulating remote datasets
WO2010040174A1 (en) * 2008-10-07 2010-04-15 Zap Holdings Pty Ltd Synchronization of relational databases with olap cubes
US9178842B2 (en) 2008-11-05 2015-11-03 Commvault Systems, Inc. Systems and methods for monitoring messaging applications for compliance with a policy
US8204859B2 (en) 2008-12-10 2012-06-19 Commvault Systems, Inc. Systems and methods for managing replicated database data
US9495382B2 (en) 2008-12-10 2016-11-15 Commvault Systems, Inc. Systems and methods for performing discrete data replication
US8504517B2 (en) 2010-03-29 2013-08-06 Commvault Systems, Inc. Systems and methods for selective data replication
US8504515B2 (en) 2010-03-30 2013-08-06 Commvault Systems, Inc. Stubbing systems and methods in a data replication environment
US8725698B2 (en) 2010-03-30 2014-05-13 Commvault Systems, Inc. Stub file prioritization in a data replication system
US8473925B2 (en) 2010-05-11 2013-06-25 Ca, Inc. Conditional dynamic instrumentation of software in a specified transaction context
US8782612B2 (en) 2010-05-11 2014-07-15 Ca, Inc. Failsafe mechanism for dynamic instrumentation of software using callbacks
US8566800B2 (en) 2010-05-11 2013-10-22 Ca, Inc. Detection of method calls to streamline diagnosis of custom code through dynamic instrumentation
US8572038B2 (en) 2010-05-28 2013-10-29 Commvault Systems, Inc. Systems and methods for performing data replication
US8826227B2 (en) * 2011-06-08 2014-09-02 International Business Machines Corporation Computer aided visualization of a business object model lifecycle
US8752015B2 (en) * 2011-12-05 2014-06-10 Ca, Inc. Metadata merging in agent configuration files
US9411616B2 (en) 2011-12-09 2016-08-09 Ca, Inc. Classloader/instrumentation approach for invoking non-bound libraries
US8892523B2 (en) 2012-06-08 2014-11-18 Commvault Systems, Inc. Auto summarization of content
US20140143248A1 (en) * 2012-11-20 2014-05-22 Martin Gembalzyk Integration to central analytics systems
US9513885B2 (en) 2013-08-22 2016-12-06 Peter Warren Web application development platform with relationship modeling

Citations (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5649200A (en) * 1993-01-08 1997-07-15 Atria Software, Inc. Dynamic rule-based version control system
US6216140B1 (en) * 1997-09-17 2001-04-10 Hewlett-Packard Company Methodology for the efficient management of hierarchically organized information
US6256773B1 (en) * 1999-08-31 2001-07-03 Accenture Llp System, method and article of manufacture for configuration management in a development architecture framework
US20020059299A1 (en) * 2000-07-14 2002-05-16 Frederic Spaey System and method for synchronizing databases
US6415299B1 (en) * 2000-04-12 2002-07-02 Unisys Corp. Method for merging versions of a model in an object oriented repository
US6460055B1 (en) * 1999-12-16 2002-10-01 Livevault Corporation Systems and methods for backing up data files
US6564368B1 (en) * 1998-10-01 2003-05-13 Call Center Technology, Inc. System and method for visual application development without programming
US6675177B1 (en) * 2000-06-21 2004-01-06 Teradactyl, Llc Method and system for backing up digital data
US20040062130A1 (en) * 2002-09-30 2004-04-01 Chiang Ying-Hsin Robert Updating electronic files using byte-level file differencing and updating algorithms
US6766334B1 (en) * 2000-11-21 2004-07-20 Microsoft Corporation Project-based configuration management method and apparatus
US6785421B1 (en) * 2000-05-22 2004-08-31 Eastman Kodak Company Analyzing images to determine if one or more sets of materials correspond to the analyzed images
US20040225682A1 (en) * 2003-05-08 2004-11-11 Microsoft Corporation Preview mode
US20050010919A1 (en) * 2003-06-25 2005-01-13 Oracle International Corporation Approaches for migrating portal objects from a source installation to a target installation
US20050102328A1 (en) * 2003-11-07 2005-05-12 Ring Cameron T. Synchronization and merge engines
US20050144198A1 (en) * 1999-03-05 2005-06-30 Microsoft Corporation Versions and workspaces in an object repository
US6925467B2 (en) * 2002-05-13 2005-08-02 Innopath Software, Inc. Byte-level file differencing and updating algorithms
US7080088B1 (en) * 2002-01-30 2006-07-18 Oracle International Corporation Automatic reconciliation of bindable objects
US7469262B2 (en) * 2003-12-29 2008-12-23 Oracle International Corporation Customizable metadata merging framework

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7343585B1 (en) * 2002-01-30 2008-03-11 Oracle International Corporation Operator approach for generic dataflow designs

Patent Citations (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5649200A (en) * 1993-01-08 1997-07-15 Atria Software, Inc. Dynamic rule-based version control system
US6216140B1 (en) * 1997-09-17 2001-04-10 Hewlett-Packard Company Methodology for the efficient management of hierarchically organized information
US6564368B1 (en) * 1998-10-01 2003-05-13 Call Center Technology, Inc. System and method for visual application development without programming
US20050144198A1 (en) * 1999-03-05 2005-06-30 Microsoft Corporation Versions and workspaces in an object repository
US7711708B2 (en) * 1999-03-05 2010-05-04 Microsoft Corporation Versions and workspaces in an object repository
US6256773B1 (en) * 1999-08-31 2001-07-03 Accenture Llp System, method and article of manufacture for configuration management in a development architecture framework
US6460055B1 (en) * 1999-12-16 2002-10-01 Livevault Corporation Systems and methods for backing up data files
US6704755B2 (en) * 1999-12-16 2004-03-09 Livevault Corporation Systems and methods for backing up data files
US6415299B1 (en) * 2000-04-12 2002-07-02 Unisys Corp. Method for merging versions of a model in an object oriented repository
US6785421B1 (en) * 2000-05-22 2004-08-31 Eastman Kodak Company Analyzing images to determine if one or more sets of materials correspond to the analyzed images
US6675177B1 (en) * 2000-06-21 2004-01-06 Teradactyl, Llc Method and system for backing up digital data
US20020059299A1 (en) * 2000-07-14 2002-05-16 Frederic Spaey System and method for synchronizing databases
US6766334B1 (en) * 2000-11-21 2004-07-20 Microsoft Corporation Project-based configuration management method and apparatus
US7080088B1 (en) * 2002-01-30 2006-07-18 Oracle International Corporation Automatic reconciliation of bindable objects
US6925467B2 (en) * 2002-05-13 2005-08-02 Innopath Software, Inc. Byte-level file differencing and updating algorithms
US20040062130A1 (en) * 2002-09-30 2004-04-01 Chiang Ying-Hsin Robert Updating electronic files using byte-level file differencing and updating algorithms
US20040225682A1 (en) * 2003-05-08 2004-11-11 Microsoft Corporation Preview mode
US20050010919A1 (en) * 2003-06-25 2005-01-13 Oracle International Corporation Approaches for migrating portal objects from a source installation to a target installation
US20050102328A1 (en) * 2003-11-07 2005-05-12 Ring Cameron T. Synchronization and merge engines
US7469262B2 (en) * 2003-12-29 2008-12-23 Oracle International Corporation Customizable metadata merging framework

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120166470A1 (en) * 2010-12-22 2012-06-28 Dirk Baumgaertel Systems and methods providing touchscreen report navigation
US9058365B2 (en) * 2010-12-22 2015-06-16 Sap Se Systems and methods providing touchscreen report navigation
US20140053091A1 (en) * 2012-08-20 2014-02-20 Microsoft Corporation Data Exploration User Interface
US9563674B2 (en) * 2012-08-20 2017-02-07 Microsoft Technology Licensing, Llc Data exploration user interface
US10001897B2 (en) 2012-08-20 2018-06-19 Microsoft Technology Licensing, Llc User interface tools for exploring data visualizations

Also Published As

Publication number Publication date Type
US7469262B2 (en) 2008-12-23 grant
US8103641B2 (en) 2012-01-24 grant
US20050149583A1 (en) 2005-07-07 application

Similar Documents

Publication Publication Date Title
US6407753B1 (en) System and method for integrating entities via user-interactive rule-based matching and difference reconciliation
US7398524B2 (en) Apparatus and method for subtractive installation
US6487556B1 (en) Method and system for providing an associative datastore within a data processing system
US7415484B1 (en) Method and system for modeling of system content for businesses
US6564215B1 (en) Update support in database content management
US6594672B1 (en) Generating multidimensional output using meta-models and meta-outlines
US7107589B1 (en) Infrastructure for the automation of the assembly of schema maintenance scripts
US6411974B1 (en) Method to collate and extract desired contents from heterogeneous text-data streams
US20060230044A1 (en) Records management federation
US20050066059A1 (en) Propagating attributes between entities in correlated namespaces
US20040093559A1 (en) Web client for viewing and interrogating enterprise data semantically
US7735062B2 (en) Software development system and method
US20080140696A1 (en) System and method for analyzing data sources to generate metadata
US20040236796A1 (en) Data importation and exportation for computing devices
US20040243552A1 (en) Method, system, and apparatus for viewing data
US7185317B2 (en) Logical data modeling and integrated application framework
US7797336B2 (en) System, method, and computer program product for knowledge management
US20090077074A1 (en) Apparatus, computer program product, and method for supporting construction of ontologies
US20070245332A1 (en) Method and apparatus to perform an application software migration
US7725501B1 (en) System and method for rapid database application deployment and use
US20060168577A1 (en) Software development system and method
US7127472B1 (en) Data processing method and data processing device
US20020092004A1 (en) Methods and systems for automatically generating software applications
US20110055147A1 (en) Generating extract, transform, and load (etl) jobs for loading data incrementally
US20020147725A1 (en) Method and apparatus for database table definition

Legal Events

Date Code Title Description
CC Certificate of correction
FPAY Fee payment

Year of fee payment: 4