US20060242160A1 - Method and apparatus for transporting data for data warehousing applications that incorporates analytic data interface - Google Patents
Method and apparatus for transporting data for data warehousing applications that incorporates analytic data interface Download PDFInfo
- Publication number
- US20060242160A1 US20060242160A1 US09/877,370 US87737001A US2006242160A1 US 20060242160 A1 US20060242160 A1 US 20060242160A1 US 87737001 A US87737001 A US 87737001A US 2006242160 A1 US2006242160 A1 US 2006242160A1
- Authority
- US
- United States
- Prior art keywords
- data
- record
- source
- key
- dimension
- 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
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/283—Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP
-
- Y—GENERAL 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
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99942—Manipulating data structure, e.g. compression, compaction, compilation
-
- Y—GENERAL 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
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99943—Generating database or data structure, e.g. via user interface
Definitions
- the present invention relates to database systems. More particularly, the present invention pertains to an apparatus and method for transporting data for a data warehousing application.
- Extracting raw data from one or more operational databases and transforming it into useful information is the function of data “warehouses” and data “marts.”
- data warehouses and data marts the data is structured to satisfy decision support roles rather than operational needs.
- the corresponding source data from an operational database is filtered to remove extraneous and erroneous records; cryptic and conflicting codes are resolved; raw data is translated into something more meaningful; and summary data that is useful for decision support, trend analysis or other end-user needs is pre-calculated.
- the data warehouse is comprised of an analytical database containing data useful for decision support.
- a data mart is similar to a data warehouse, except that it contains a subset of corporate data for a single aspect of business, such as finance, sales, inventory, or human resources. With data warehouses and data marts, useful information is retained at the disposal of the decision-makers.
- the time and cost for defining and programming such that the data is suitable for use as input to a data warehousing application is particularly problematic for companies that use multiple different operational databases. More particularly, the process of defining and programming for data transport must be repeated for each different operational database. That is, for example, if a company has both a SAP database and an Oracle database, the process of defining and programming for data transport must be performed for both databases and the process is unique to each database.
- What is needed is a method and apparatus that allows for transporting data such that the data can be used in data warehousing applications.
- a method and apparatus is needed that meets that above need and that takes advantage of the standardization of database components.
- a method and apparatus is needed that reduces the time required to define and program data transport for data warehousing applications.
- the present invention provides a method and apparatus that meets the above needs.
- the present invention includes a method and apparatus for transporting data for a data warehousing application. More particularly, the present invention introduces a method and a data transport process architecture that uses standardized structures of different types of source databases to achieve source-specific configuration for extraction, transformation, and loading in a data warehousing application.
- a system includes an analytic business component that translates operational data from data source having a standardized data structure.
- the system also includes a staging area for storing the translated data.
- the system includes a source adapter that is coupled to the staging area.
- An analytic data interface couples to the source adapter and receives the data having a common structure and transforms the data for loading into a data warehouse.
- data is extracted from one or more source containing data having a standard data structure and is translated into data that contains meaningful business terms.
- the translated data is then stored.
- the analytic business component is operable for extracting data from the source, translating the extracted data and for storing the translated data into a staging area.
- the translated data is then processed to obtain data having a common structure.
- a source adapter processes the translated data to obtain data having a common structure.
- an analytic data interface receives the data having a common structure and transforms the data for loading into a data warehouse.
- the data can then be loaded into a data warehouse.
- the analytic data interface includes a graphical user interface that makes it easy to configure and customize how business data is loaded into an analytic applications system such as a data warehouse.
- the analytic data interface includes a simplified abstraction layer for the data warehouse administrator, allowing the warehouse administrator to configure how data is loaded into the analytic applications in a fraction of the time it takes to configure these capabilities programmatically as occurs in prior art systems.
- most of the complex technical problems are solved prior to data entering the analytic data interface. In many instances, these technical problems are solved without any required configuration or analysis by the warehouse administrator. This greatly simplifies the task of loading data into a data warehouse, saving significant expense and time.
- the benefits are particularly apparent for companies that use multiple different operational databases. More particularly, there is no need to define and program for data transport for each different operational database.
- the warehouse administrator needs only define and program for data transport a single time using the graphical user interface of the analytic data interface.
- the present invention provides a method and apparatus that allows for transporting data such that the data can be used in data warehousing applications.
- the present invention provides a method and apparatus that takes advantage of the standardization of database components.
- the present invention provides a method and apparatus that reduces the time required to define and program data transport for data warehousing applications.
- FIG. 1 illustrates an exemplary computer system used as part of a data warehousing system in accordance with one embodiment of the present invention.
- FIG. 2 illustrates an exemplary architecture that includes a server in accordance with one embodiment of the present invention.
- FIG. 3 illustrates an exemplary architecture that includes an analytic data interface in accordance with one embodiment of the present invention.
- FIG. 4 shows a method for transporting data to a data warehousing application in accordance with one embodiment of the present invention.
- portions of the present invention are comprised of the computer-readable and computer executable instructions which reside, for example, in computer system 10 used as a part of a data warehousing system in accordance with one embodiment of the present invention. It is appreciated that system 10 of FIG. 1 is exemplary only and that the present invention can operate within a number of different computer systems including general-purpose computer systems, embedded computer systems, and stand-alone computer systems specially adapted for data warehousing applications.
- Computer system 10 includes an address/data bus 12 for conveying digital information between the various components, a central processor unit (CPU) 14 for processing the digital information and instructions, a main memory 16 comprised of volatile random access memory (RAM) for storing the digital information and instructions, a non-volatile read only memory (ROM) 18 for storing information and instructions of a more permanent nature.
- computer system 10 may also include a data storage unit 20 (e.g., a magnetic, optical, floppy, or tape drive) for storing vast amounts of data, and an I/O interface 22 for interfacing with peripheral devices (e.g., computer network, modem, mass storage devices, etc.).
- a data storage unit 20 e.g., a magnetic, optical, floppy, or tape drive
- I/O interface 22 for interfacing with peripheral devices (e.g., computer network, modem, mass storage devices, etc.).
- the software program for performing the transport process can be stored either in main memory 16 , data storage unit 20 , or in an external storage device.
- Devices which may be coupled to computer system 10 include a display device 28 for displaying information to a computer user, an alphanumeric input device 30 (e.g., a keyboard), and a cursor control device 26 (e.g., mouse, trackball, light pen, etc.) for inputting data, selections, updates, etc.
- a display device 28 for displaying information to a computer user
- an alphanumeric input device 30 e.g., a keyboard
- a cursor control device 26 e.g., mouse, trackball, light pen, etc.
- computer system 10 may be coupled in a network, such as in a client/server environment, whereby a number of clients (e.g., personal computers, workstations, portable computers, minicomputers, terminals, etc.), are used to run processes for performing desired tasks (e.g., inventory control, payroll, billing, etc.).
- clients e.g., personal computers, workstations, portable computers, minicomputers, terminals, etc.
- desired tasks e.g., inventory control, payroll, billing, etc.
- FIG. 2 illustrates an exemplary computer network upon which an embodiment of the present invention may be practiced.
- Operational databases 210 , 220 , and 230 store data resulting from business and financial transactions, and/or from equipment performance logs. These databases can be any of the conventional RDMS systems (such as from Oracle, Informix, Sybase, Microsoft, Ariba, SAP, Web Logs, etc.) that reside within a high capacity mass storage device (such as hard disk drives, optical drives, tape drives, etc.).
- Databases 250 and 260 are the data warehouses or data marts that are the targets of the data transportation process.
- server 240 performs data transport operations. That is, in the present embodiment, data from databases 210 , 220 , and 230 is extracted, transformed, and loaded by server 240 into databases 250 and 260 .
- server 240 includes multiple microprocessors and data warehousing related software that operates in conjunction with an installed operating program such as, for example, Windows, NT, UNIX, etc.
- FIG. 3 shows an embodiment of the present invention that includes Analytic Business Components (ABCs) 12 - 14 that extract data from sources of data (e.g. databases 2 - 3 and web logs 4 ).
- sources e.g. databases 2 - 3 and web logs 4 .
- sources typically contain data in the form of relational tables, Enterprise Resource Planning (ERP) objects, or flat files.
- ERP Enterprise Resource Planning
- Analytic business components 12 - 14 also translate operational data from each source of data into meaningful business terms. These business terms are then stored in staging areas 22 - 24 .
- Staging areas 22 - 24 hold data received from analytic business components 12 - 14 .
- staging areas 22 - 24 consolidate data from disparate systems.
- the staging area denormalizes data where necessary, preparing it for storing in a data warehouse. More particularly, data is cleansed and remains formalized, tables from different databases are joined, and a refresh policy is carried out.
- staging areas 22 - 24 provide a structure that is flexible to allow for user configuration.
- the only structures that are not configurable are the primary key columns.
- staging areas 22 - 24 are not organized by subject area, and are not customized for viewing or reporting by end users.
- the staging area tables consist of all fields required by the analytic data interface 5 , including all extension fields.
- the default database for the staging area is oracle. However, at implementation, the database type can be changed.
- staging areas 22 - 24 provide for quick and efficient data extract. This minimizes the time required for loading the database, allowing for a smaller operational window.
- staging area prepares the data consistently for loading into the analytic data interface from various sources.
- source adapters 32 - 33 convert source-specific terminology into analytic data interface terminology.
- Source adapters are provided for each source with the exception of web logs, which do not require any further source-specific conversion.
- source adapters 32 - 33 combine extract-specific staging area objects into the analytic data interface 5 .
- source adapters 32 - 33 combine staging area objects to match up the inputs and their interrelationship as required by the analytic data interface 5 .
- Analytic data interface 5 transforms data for loading into data warehouse 6 for use in applications 8 .
- the analytic data interface cleans data by enforcing commonalties in dates, names and other data types that appear across multiple systems and prepares it for the source-independent data warehouse.
- analytic data interface 5 includes a graphical user interface that makes it easy to configure and customize how business data is loaded into an analytic applications system such as a data warehouse 6 .
- Analytic data interface 5 includes a simplified abstraction layer for the data warehouse administrator, allowing the warehouse administrator to configure how data is loaded into the analytic applications in a fraction of the time it takes to configure these capabilities programmatically as occurs in prior art systems.
- most of the complex technical problems are solved prior to data entering the analytic data interface. Often these technical problems are solved automatically by the preconfigured programming of the analytic business components without any required configuration or analysis by the warehouse administrator. This greatly simplifies the task of loading data into a data warehouse, saving significant expense and time.
- analytic business components 12 - 14 , source adapters 32 - 33 , and analytic data interface 5 are implemented as maplets within the warehouse designer.
- staging areas 42 - 43 exists as targets in the warehouse designer.
- An analytic applications system is illustrated that includes data warehouse 6 , operational data store 7 and applications 8 . It is appreciated that the method and apparatus of the present invention is well adapted for transporting data to any of a number of different types of analytic applications systems. For example, the present embodiment in well adapted for transporting data to an analytic applications system that includes a data mart and analytic applications systems having different structures and configurations.
- data warehouse 6 includes a bus architecture and dimensional data models with conformed dimensions and facts for star schema analysis of data.
- data warehouse 6 includes support for slowly changing dimensions with effective dates for type II slowly changing dimensions.
- data warehouse 6 includes pre-packaged dimensions (e.g. time, time of day, IP addresses, etc.), and provision for intelligent extension fields, normalized measures, aggregate tables, and analytic fields with additional complex measures.
- data warehouse 6 is packaged as targets in a warehouse designer.
- Operational data store 7 consolidates and stores references data for loading into data warehouse 6 .
- operational data store 7 retains customized, source-specific-fields that will not exist in data warehouse 6 such as reference data to help standardize other formats (e.g. zip codes, currency conversion rates, and product-code to product-name translations).
- applications 8 include data warehousing applications.
- applications 8 include pre-packaged analytic tools that provide queries and reports for evaluating business performance such as, for example, applications built on the Power CenterTM data integration platform made by Informatica Corporation of Palo Alto, Calif.
- applications 8 include programs that allow for drill-down capability, drill-up capability and drill-across capability.
- applications 8 allow for the performance of more detailed analysis using a multi-dimensional approach (slice-and-dice capability).
- applications 8 include a user interface with web analytic capabilities that allows for generating standard reports and that includes ad-hoc query tools (that allow for drag and drop of measurements and dimensions to create custom reports).
- applications 8 are pre-configured with some aggregate tables on commonly used dimensions and facts. However, these default aggregate tables can be changed based on specific business needs. Aggregate tables contain pre-calculated pre-stored summaries that are stored in the data warehouse to improve query performance.
- FIG. 4 shows a method 400 for transporting data for a data warehousing application.
- method 400 is performed by server 240 of FIG. 2 which includes some or all of the components of computer 1 of FIG. 1 .
- the structure of FIG. 3 is used to perform method 400 .
- data is extracted from one or more source containing data having a standard data structure.
- data is extracted from databases 210 , 220 , and 230 by server 240 .
- analytic business components 12 - 14 are operable to extract data from data sources 2 - 4 . More particularly, analytic business component 12 extracts data from database 2 . Similarly, analytic business component 13 extracts data from database 3 and analytic business component 14 extracts data from web logs 4 .
- step 402 is performed by server 240 of FIG. 2 .
- analytic business components 12 - 14 of FIG. 3 translate the data extracted in step 401 in order to produce translated data that contains meaningful business terms. More particularly, analytic business component 12 translates data from database 2 . Similarly, analytic business component 13 translates data from database 3 while analytic business component 14 translates data from web logs 4 .
- analytic business components 12 - 14 are source-specific. That is, each analytic business component is adapted to extract and translate data from a specific type of database standard data structure.
- database 2 is an Ariba database
- analytic business component 12 is an analytic business component for an Ariba database.
- database 3 is a SAP database
- analytic business component 13 is an analytic business component for a SAP database.
- database 4 includes web logs
- analytic business component 14 is an analytic business component adapted to extract and translate web logs.
- the translation process hides the complexity of the source systems (e.g. databases 2 - 3 and web logs 4 ).
- analytic business components 12 - 14 perform joins in the data source that help to present the data in simple business terms.
- the analytic business components 12 - 14 present the source fields in form that is understandable to the user. For example, for SAP, business components 12 - 14 provide English descriptions.
- analytic business components 12 - 14 can be customized at implementation to provide additional business abstractions over and above those business abstractions preprogrammed into analytic business components 12 - 14 . Moreover, analytic business components 12 - 14 encapsulate extraction logic as they move data from its source.
- the translated data is then loaded into staging areas as shown by step 403 .
- the translated data is loaded into staging areas stored on server 240 .
- the translated data is loaded into staging areas 22 - 24 . More particularly, analytic business component 12 loads translated data into staging area 22 . Similarly, analytic business component 13 loads translated data into staging area 23 and analytic business component 14 loads translated data into staging area 24 .
- the translated data is processed to obtain data having a common structure.
- server 240 is operable to process the translated data to obtain data having a common structure.
- step 404 converts source-specific terminology into analytic data interface terminology.
- staging area objects are combined to match up the inputs and their interrelationship as required by the analytic data interface 5 .
- Data indicators and data indicator flags are configured based on the data. Physical deletions are performed and a delete flag is set to provide a common way to flag a record to be deleted. In addition, data type conversion and source-related clean up are performed. Also, unique key identification is configured based on the source and its data to take care of problems arising from the fact that the number of keys differ in each source. In the present embodiment, the set of rows that will be put in the data warehouse is also determined.
- source adapters 32 - 33 are operable for processing the translated data within staging areas 22 - 23 to obtain data having a common structure. More particularly, source adapters 32 - 34 convert source-specific terminology into analytic data interface terminology. Source adapters are provided for each source with the exception of web logs, which do not require any further source-specific conversion. In the present embodiment, source adapters 32 - 33 combine extract-specific staging area objects into the analytic data interface 5 . In the present embodiment, source adapters 32 - 33 combine staging area objects to match up the inputs and their interrelationship as required by the analytic data interface 5 .
- source adapters 32 - 33 set the delete flag. More particularly, because each source handles deletes differently, there is a need to provide a uniform delete flag to the analytic data interface. To meet this need, source adapters 32 - 33 handle physical deletions and delete indicators and provide a common way to flag a record to be deleted.
- source adapters 32 - 33 handle data type conversions. More particularly, because the same concepts are represented differently in each source, there is a need to provide data type conversion.
- source adapters 32 - 33 publish the structure of each field and convert the data type using a consistent approach.
- source adapters 32 - 33 handle any source-related clean up.
- source adapters 32 - 33 configure unique key identification based on the source and its data. This takes care of problems arising from the fact that the number of keys differ in each source.
- the data having a common structure is transformed into a format suitable for loading into an analytic applications system such as a data warehousing application.
- the data having a common structure is transformed into a format suitable for loading into a data warehouse as shown by step 405 .
- server 240 is operable to transform the data having a common structure into a format suitable for loading into a data warehouse.
- step 405 includes consolidation of business concepts into integrated structures that are suitable for querying and reporting.
- source definitions differences are normalized into a single, common definition.
- step 405 includes, for example, code lookup (e.g. currency conversion, unit of measure conversion and code to description field resolution), data-driven updates, intelligent expansion fields, dimension table specific features, fact table specific features, key resolution, key generation, and “bad” data flagging.
- code lookup e.g. currency conversion, unit of measure conversion and code to description field resolution
- data-driven updates e.g. currency conversion, unit of measure conversion and code to description field resolution
- intelligent expansion fields e.g. currency conversion, unit of measure conversion and code to description field resolution
- dimension table specific features e.g. currency conversion, unit of measure conversion and code to description field resolution
- key resolution e.g., key resolution, key generation, and “bad” data flagging.
- the user can also insert, update, or reject a determination.
- analytic data interface 5 is operable to transform data received from source adapters 32 - 33 and staging area 24 into a format suitable for loading into a data mart.
- analytic data interface 5 provides complex transformation logic that integrates data in two ways. First, business concepts are consolidated across an entire value chain into integrated structures that are suitable for querying and reporting.
- the analytic data interface 5 provides complex transformation logic that normalizes source definitions differences into a single, common definition.
- Some of the transformation logic performed in the analytic data interface 5 include codes lookup (e.g. currency conversion, unit of measure conversion and code to description field resolution) and data-driven updates.
- the analytic data interface includes dimension table specific features (e.g. surrogate key generation, slowly changing dimension support, and support for effective dates), fact table specific features (e.g. support for exchange rate lookup and support for dimension key lookup), key resolution, key generation, “bad” data flagging.
- dimension table specific features e.g. surrogate key generation, slowly changing dimension support, and support for effective dates
- fact table specific features e.g. support for exchange rate lookup and support for dimension key lookup
- key resolution e.g. support for exchange rate lookup and support for dimension key lookup
- key generation e.g., “bad” data flagging.
- the analytic data interface allows a user to insert, update, or reject a determination.
- analytic data interface 5 includes slowly changing dimension logic for tracking historically important data.
- a historically significant attribute is one that you want to retain for your records, even if subsequent records show that a change has been made.
- records within analytic data interface 5 can be configured using two different types of slowly changing dimension categories: historically insignificant attributes (Type 1 slowly changing dimensions) and historically significant attributes (Type 2 slowly changing dimensions).
- Type 1 slowly changing dimensions the data field is simply overwritten.
- type 1 slowly changing dimensions does not maintain history, it is the simplest and fastest slowly changing dimension.
- Type 1 slowly changing dimension is used when the old value of the changed dimension is not deemed important or of interest to track, or is a historically insignificant attribute. For example, a user may want to use type 1 when changing incorrect values in a field.
- Type 2 slowly changing dimensions create a new record. This is the most common slowly changing dimension because it allows the user to track history. The old record allows for pointing to all history prior to the change, and the new record points to all history after the change. Because each change generates a new record, old and new records allow for partition history exactly.
- state name in a supplier table is a type 2 slowly changing dimension
- a new, current record is generated upon changes to the state in which a supplier is located in. The previous value remains a record, and the new current record is a separate record.
- the slowly changing dimension logic of the present invention gives four types of records that are stored in the staging area, new records, changed records with data that is not historically tracked, changed records having historical significance, and changed records having historical significance, and changed records whose changes have no significance of any kind.
- a new customer key is used for the old sales record while the old customer key continues to be used for the new record.
- the old customer key continues to be used for the new record.
- a predetermined alphanumeric character is used to indicate a need for data cleansing. That is, because most analytic data interface fields are mapped to fields in the transaction system, be it Ariba, ORMS or SAP, some fields may not be populated with values. For instance, a row in the supplier table may have information on a supplier's address, but may have no value in the supplier's region field. If a report is run on supplier prices by region, the suppliers for whom region information is missing would normally be excluded. However, analytic data interface 5 provides a feature to identify all occurrences of missing values. In the present embodiment the identifier for missing values is a question mark (“?”).
- the question mark is a sign that the organization's data needs to be “cleansed.”
- Cleansing the data in this case involves drilling into the category marked as “?” to learn, perhaps the supplier names or numbers within that group.
- the data warehouse administrator can then correct each of those suppliers by entering in the regional information on the back end.
- the logic for populating null fields is in the analytic data interface 5 . More particularly, the analytic data interface looks for columns that are both linked to a character data type and that are null, and populates them with a “?.” It is appreciated that the use of a character such as a question mark is simply the default setting to represent missing data.
- the present invention is well adapted for using a different character or multiple characters.
- analytic data interface 5 Because the data input into analytic data interface 5 has a common structure, there is no need to process data from each data source independently. More particularly, the data received at analytic data interface 5 has already been translated to obtain meaningful business terms (step 402 ) and has been processed to obtain data having a common structure (step 404 ). Therefore, the data from different sources (e.g. databases 2 - 3 and web logs 4 ) can be treated as a single data source for the purpose of transformation (step 405 ).
- sources e.g. databases 2 - 3 and web logs 4
- the analytic data interface includes a graphical user interface
- it is easy to configure and customize how business data is loaded into an analytic applications system such as a data warehouse.
- the analytic data interface includes a simplified abstraction layer for the data warehouse administrator
- the warehouse administrator can configure how data is loaded into the analytic applications in a fraction of the time it takes to configure these capabilities programmatically.
- the task of configuring data is greatly simplified.
- the present invention greatly simplifies the process of loading data into a data warehouse, saving significant expense and time.
- the benefits are particularly apparent for companies that use multiple different operational databases. More particularly, there is no need to define and program for data transport for each different operational database.
- the warehouse administrator needs only define and program for data transport a single time using the graphical user interface of the analytic data interface.
- maplets (reusable objects that represent a set of transformations) are used for code lookup, for address lookup, and for extraction. Also, maplets are used to identify all business locations and identify all business hierarchical structures.
- the transformed data is loaded into an analytic applications system such as a data warehousing application.
- the data is loaded into a data warehouse as shown by step 406 .
- the data is loaded into target databases 250 - 260 which can be databases of a data warehouse.
- the data is loaded into data warehouse 6 .
- data is also loaded into operational data store 7 .
- Applications 8 then extract data from data warehouse 6 and operational data store 7 for performing analysis.
- staging area 32 will contain data from an Ariba database that has been translated in order to include meaningful business terms
- staging area 33 will contain data from an SAP database that has been translated in order to include meaningful business terms
- staging area 34 will contain data from web logs that has been translated in order to include meaningful business terms.
- source adapter 32 will be an Ariba source adapter and source adapter 33 will be a SAP source adapter while no source adapter is required for data from web logs 4 .
- source adapter 33 will be a SAP source adapter while no source adapter is required for data from web logs 4 .
- the data from each of sources 2 - 4 is provided to analytic data interface 5 , the data can be treated as a common data source for the purpose of transforming the data into a format suitable for loading into a data warehousing application (step 405 of FIG. 4 ). Therefore, the warehouse administrator needs only define and program for data transport a single time using the graphical user interface of the analytic data interface. Not three separate times as would be required by prior art systems.
- the present invention provides a method and apparatus that allows for transporting data such that the data can be used in data warehousing applications.
- the present invention provides a method and apparatus that takes advantage of the standardization of database components.
- the present invention provides a method and apparatus that reduces the time required to define and program data transport for data warehousing applications.
Abstract
Description
- The present invention relates to database systems. More particularly, the present invention pertains to an apparatus and method for transporting data for a data warehousing application.
- Due to the increased amounts of data being stored and processed today, operational databases are constructed, categorized, and formatted in a manner conducive for maximum throughput, access time, and storage capacity. Unfortunately, the raw data found in these operational databases often exist as rows and columns of numbers and code which appears bewildering and incomprehensible to business analysts and decision makers. Furthermore, the scope and vastness of the raw data stored in modern databases renders it harder to analyze. Hence, applications were developed in an effort to help interpret, analyze, and compile the data so that a business analyst may readily and easily understand it. This is accomplished by mapping, sorting, and summarizing the raw data before it is presented for display. Thereby, individuals can now interpret the data and make key decisions based thereon.
- Extracting raw data from one or more operational databases and transforming it into useful information is the function of data “warehouses” and data “marts.” In data warehouses and data marts, the data is structured to satisfy decision support roles rather than operational needs. Before the data is loaded into the target data warehouse or data mart, the corresponding source data from an operational database is filtered to remove extraneous and erroneous records; cryptic and conflicting codes are resolved; raw data is translated into something more meaningful; and summary data that is useful for decision support, trend analysis or other end-user needs is pre-calculated. In the end, the data warehouse is comprised of an analytical database containing data useful for decision support. A data mart is similar to a data warehouse, except that it contains a subset of corporate data for a single aspect of business, such as finance, sales, inventory, or human resources. With data warehouses and data marts, useful information is retained at the disposal of the decision-makers.
- However, establishing a structure for transporting (extracting, transporting and loading) data from an operational database or databases into a structure that can be used for data warehousing applications is quite time consuming. In many instances many months of man-hours are required to define and program a suitable structure for transporting data from an operational database(s) into a format suitable for data warehousing applications.
- The complexities in designing a data model for transporting data from an operational database into target tables in a data warehouse are not simply technical problems. They also involve complex business semantic problems.
- Recently, many operational databases have begun to use standardized database structures. Several companies have recently created Business Application Programming Interfaces for getting data into and out of business databases that use these standardized database structures. Business application programming interfaces are effective for getting information into and out of a business database. However, the user must still perform the process of defining and programming for data transport in order to obtain output that is suitable for use as input to a data warehousing application. This is expensive and time consuming. In addition, these business application programming interfaces require extensive knowledge and programming to learn and use.
- The time and cost for defining and programming such that the data is suitable for use as input to a data warehousing application is particularly problematic for companies that use multiple different operational databases. More particularly, the process of defining and programming for data transport must be repeated for each different operational database. That is, for example, if a company has both a SAP database and an Oracle database, the process of defining and programming for data transport must be performed for both databases and the process is unique to each database.
- What is needed is a method and apparatus that allows for transporting data such that the data can be used in data warehousing applications. In addition, a method and apparatus is needed that meets that above need and that takes advantage of the standardization of database components. Moreover, a method and apparatus is needed that reduces the time required to define and program data transport for data warehousing applications. The present invention provides a method and apparatus that meets the above needs.
- The present invention includes a method and apparatus for transporting data for a data warehousing application. More particularly, the present invention introduces a method and a data transport process architecture that uses standardized structures of different types of source databases to achieve source-specific configuration for extraction, transformation, and loading in a data warehousing application.
- A system is disclosed that includes an analytic business component that translates operational data from data source having a standardized data structure. The system also includes a staging area for storing the translated data. In addition, the system includes a source adapter that is coupled to the staging area. An analytic data interface couples to the source adapter and receives the data having a common structure and transforms the data for loading into a data warehouse.
- In one embodiment of the present invention, data is extracted from one or more source containing data having a standard data structure and is translated into data that contains meaningful business terms. The translated data is then stored. In the present embodiment, the analytic business component is operable for extracting data from the source, translating the extracted data and for storing the translated data into a staging area.
- The translated data is then processed to obtain data having a common structure. In the present embodiment, a source adapter processes the translated data to obtain data having a common structure.
- The data having a common structure is then transformed into a format suitable for loading into a data mart. In the present embodiment, an analytic data interface receives the data having a common structure and transforms the data for loading into a data warehouse. The data can then be loaded into a data warehouse.
- In the present embodiment, the analytic data interface includes a graphical user interface that makes it easy to configure and customize how business data is loaded into an analytic applications system such as a data warehouse. The analytic data interface includes a simplified abstraction layer for the data warehouse administrator, allowing the warehouse administrator to configure how data is loaded into the analytic applications in a fraction of the time it takes to configure these capabilities programmatically as occurs in prior art systems. In addition, most of the complex technical problems are solved prior to data entering the analytic data interface. In many instances, these technical problems are solved without any required configuration or analysis by the warehouse administrator. This greatly simplifies the task of loading data into a data warehouse, saving significant expense and time.
- The benefits are particularly apparent for companies that use multiple different operational databases. More particularly, there is no need to define and program for data transport for each different operational database. The warehouse administrator needs only define and program for data transport a single time using the graphical user interface of the analytic data interface.
- Accordingly, the present invention provides a method and apparatus that allows for transporting data such that the data can be used in data warehousing applications. In addition, the present invention provides a method and apparatus that takes advantage of the standardization of database components. Moreover, the present invention provides a method and apparatus that reduces the time required to define and program data transport for data warehousing applications.
- These and other objects and advantages of the present invention will no doubt become obvious to those of ordinary skill in the art after having read the following detailed description of the preferred embodiments which are illustrated in the various drawing figures.
- The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments of the present invention and, together with the description, serve to explain the principles of the invention.
-
FIG. 1 illustrates an exemplary computer system used as part of a data warehousing system in accordance with one embodiment of the present invention. -
FIG. 2 illustrates an exemplary architecture that includes a server in accordance with one embodiment of the present invention. -
FIG. 3 illustrates an exemplary architecture that includes an analytic data interface in accordance with one embodiment of the present invention. -
FIG. 4 shows a method for transporting data to a data warehousing application in accordance with one embodiment of the present invention. - An apparatus and method for transporting data to a data warehousing application is described. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be obvious, however, to one skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the present invention.
- Some portions of the detailed descriptions that follow are presented in terms of procedures, logic blocks, processing, and other symbolic representations of operations on data bits within a computer memory. These descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. In the present application, a procedure, logic block, process, etc., is conceived to be a self-consistent sequence of steps or instructions leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated in a computer system. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.
- It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussions, it is appreciated that throughout the present invention, discussions utilizing terms such as “extracting,” “translating,” “loading,” “processing,” “transforming,” “storing” or the like, can refer to the actions and processes of a computer system, or similar electronic computing device. The computer system or similar electronic computing device manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission, or display devices.
- With reference to
FIG. 1 , portions of the present invention are comprised of the computer-readable and computer executable instructions which reside, for example, incomputer system 10 used as a part of a data warehousing system in accordance with one embodiment of the present invention. It is appreciated thatsystem 10 ofFIG. 1 is exemplary only and that the present invention can operate within a number of different computer systems including general-purpose computer systems, embedded computer systems, and stand-alone computer systems specially adapted for data warehousing applications.Computer system 10 includes an address/data bus 12 for conveying digital information between the various components, a central processor unit (CPU) 14 for processing the digital information and instructions, amain memory 16 comprised of volatile random access memory (RAM) for storing the digital information and instructions, a non-volatile read only memory (ROM) 18 for storing information and instructions of a more permanent nature. In addition,computer system 10 may also include a data storage unit 20 (e.g., a magnetic, optical, floppy, or tape drive) for storing vast amounts of data, and an I/O interface 22 for interfacing with peripheral devices (e.g., computer network, modem, mass storage devices, etc.). It should be noted that the software program for performing the transport process can be stored either inmain memory 16,data storage unit 20, or in an external storage device. Devices which may be coupled tocomputer system 10 include adisplay device 28 for displaying information to a computer user, an alphanumeric input device 30 (e.g., a keyboard), and a cursor control device 26 (e.g., mouse, trackball, light pen, etc.) for inputting data, selections, updates, etc. - Furthermore,
computer system 10 may be coupled in a network, such as in a client/server environment, whereby a number of clients (e.g., personal computers, workstations, portable computers, minicomputers, terminals, etc.), are used to run processes for performing desired tasks (e.g., inventory control, payroll, billing, etc.). -
FIG. 2 illustrates an exemplary computer network upon which an embodiment of the present invention may be practiced.Operational databases Databases 250 and 260 are the data warehouses or data marts that are the targets of the data transportation process. - In the present embodiment, software operable on
server 240 performs data transport operations. That is, in the present embodiment, data fromdatabases server 240 intodatabases 250 and 260. In the present embodiment,server 240 includes multiple microprocessors and data warehousing related software that operates in conjunction with an installed operating program such as, for example, Windows, NT, UNIX, etc. -
FIG. 3 shows an embodiment of the present invention that includes Analytic Business Components (ABCs) 12-14 that extract data from sources of data (e.g. databases 2-3 and web logs 4). Typically, sources contain data in the form of relational tables, Enterprise Resource Planning (ERP) objects, or flat files. Analytic business components 12-14 also translate operational data from each source of data into meaningful business terms. These business terms are then stored in staging areas 22-24. - Staging areas 22-24 hold data received from analytic business components 12-14. In the present embodiment, staging areas 22-24 consolidate data from disparate systems. The staging area denormalizes data where necessary, preparing it for storing in a data warehouse. More particularly, data is cleansed and remains formalized, tables from different databases are joined, and a refresh policy is carried out.
- Continuing with
FIG. 3 , staging areas 22-24 provide a structure that is flexible to allow for user configuration. The only structures that are not configurable are the primary key columns. In the present embodiment, staging areas 22-24 are not organized by subject area, and are not customized for viewing or reporting by end users. Out of the box, the staging area tables consist of all fields required by theanalytic data interface 5, including all extension fields. In one embodiment, the default database for the staging area is oracle. However, at implementation, the database type can be changed. - The use of staging areas 22-24 provide for quick and efficient data extract. This minimizes the time required for loading the database, allowing for a smaller operational window. In addition, the staging area prepares the data consistently for loading into the analytic data interface from various sources.
- Continuing with
FIG. 3 , source adapters 32-33 convert source-specific terminology into analytic data interface terminology. Source adapters are provided for each source with the exception of web logs, which do not require any further source-specific conversion. In the present embodiment, source adapters 32-33 combine extract-specific staging area objects into theanalytic data interface 5. In the present embodiment, source adapters 32-33 combine staging area objects to match up the inputs and their interrelationship as required by theanalytic data interface 5. -
Analytic data interface 5 transforms data for loading intodata warehouse 6 for use inapplications 8. In the present embodiment, the analytic data interface cleans data by enforcing commonalties in dates, names and other data types that appear across multiple systems and prepares it for the source-independent data warehouse. - In the present embodiment,
analytic data interface 5 includes a graphical user interface that makes it easy to configure and customize how business data is loaded into an analytic applications system such as adata warehouse 6.Analytic data interface 5 includes a simplified abstraction layer for the data warehouse administrator, allowing the warehouse administrator to configure how data is loaded into the analytic applications in a fraction of the time it takes to configure these capabilities programmatically as occurs in prior art systems. In addition, most of the complex technical problems are solved prior to data entering the analytic data interface. Often these technical problems are solved automatically by the preconfigured programming of the analytic business components without any required configuration or analysis by the warehouse administrator. This greatly simplifies the task of loading data into a data warehouse, saving significant expense and time. - In one embodiment of the present invention, analytic business components 12-14, source adapters 32-33, and analytic data interface 5 are implemented as maplets within the warehouse designer. In this embodiment, staging areas 42-43 exists as targets in the warehouse designer.
- An analytic applications system is illustrated that includes
data warehouse 6,operational data store 7 andapplications 8. It is appreciated that the method and apparatus of the present invention is well adapted for transporting data to any of a number of different types of analytic applications systems. For example, the present embodiment in well adapted for transporting data to an analytic applications system that includes a data mart and analytic applications systems having different structures and configurations. - Continuing with
FIG. 3 , in the present embodiment,data warehouse 6 includes a bus architecture and dimensional data models with conformed dimensions and facts for star schema analysis of data. In addition,data warehouse 6 includes support for slowly changing dimensions with effective dates for type II slowly changing dimensions. Moreover,data warehouse 6 includes pre-packaged dimensions (e.g. time, time of day, IP addresses, etc.), and provision for intelligent extension fields, normalized measures, aggregate tables, and analytic fields with additional complex measures. In the present embodiment,data warehouse 6 is packaged as targets in a warehouse designer. -
Operational data store 7 consolidates and stores references data for loading intodata warehouse 6. In the present embodiment,operational data store 7 retains customized, source-specific-fields that will not exist indata warehouse 6 such as reference data to help standardize other formats (e.g. zip codes, currency conversion rates, and product-code to product-name translations). - Continuing with
FIG. 3 ,applications 8 include data warehousing applications. In thepresent embodiment applications 8 include pre-packaged analytic tools that provide queries and reports for evaluating business performance such as, for example, applications built on the Power Center™ data integration platform made by Informatica Corporation of Palo Alto, Calif. In the present embodiment,applications 8 include programs that allow for drill-down capability, drill-up capability and drill-across capability. In addition,applications 8 allow for the performance of more detailed analysis using a multi-dimensional approach (slice-and-dice capability). Moreover, in the present embodiment,applications 8 include a user interface with web analytic capabilities that allows for generating standard reports and that includes ad-hoc query tools (that allow for drag and drop of measurements and dimensions to create custom reports). - In the present embodiment,
applications 8 are pre-configured with some aggregate tables on commonly used dimensions and facts. However, these default aggregate tables can be changed based on specific business needs. Aggregate tables contain pre-calculated pre-stored summaries that are stored in the data warehouse to improve query performance. -
FIG. 4 shows a method 400 for transporting data for a data warehousing application. In one embodiment of the present invention, method 400 is performed byserver 240 ofFIG. 2 which includes some or all of the components of computer 1 ofFIG. 1 . In another embodiment, the structure ofFIG. 3 is used to perform method 400. - As shown by
step 401, data is extracted from one or more source containing data having a standard data structure. In the embodiment shown inFIG. 2 , data is extracted fromdatabases server 240. In the embodiment shown inFIG. 3 , analytic business components 12-14 are operable to extract data from data sources 2-4. More particularly,analytic business component 12 extracts data fromdatabase 2. Similarly,analytic business component 13 extracts data fromdatabase 3 andanalytic business component 14 extracts data fromweb logs 4. - Data is then translated as shown by
step 402. In one embodiment of the present invention,step 402 is performed byserver 240 ofFIG. 2 . In another embodiment, analytic business components 12-14 ofFIG. 3 translate the data extracted instep 401 in order to produce translated data that contains meaningful business terms. More particularly,analytic business component 12 translates data fromdatabase 2. Similarly,analytic business component 13 translates data fromdatabase 3 whileanalytic business component 14 translates data fromweb logs 4. - Continuing with
FIG. 4 , in the present embodiment, analytic business components 12-14 are source-specific. That is, each analytic business component is adapted to extract and translate data from a specific type of database standard data structure. Thus, for example, ifdatabase 2 is an Ariba database,analytic business component 12 is an analytic business component for an Ariba database. Similarly, ifdatabase 3 is a SAP database,analytic business component 13 is an analytic business component for a SAP database. In an embodiment in whichdatabase 4 includes web logsanalytic business component 14 is an analytic business component adapted to extract and translate web logs. - The translation process hides the complexity of the source systems (e.g. databases 2-3 and web logs 4). In the present embodiment, analytic business components 12-14 perform joins in the data source that help to present the data in simple business terms. In addition, the analytic business components 12-14 present the source fields in form that is understandable to the user. For example, for SAP, business components 12-14 provide English descriptions.
- In the present embodiment, analytic business components 12-14 can be customized at implementation to provide additional business abstractions over and above those business abstractions preprogrammed into analytic business components 12-14. Moreover, analytic business components 12-14 encapsulate extraction logic as they move data from its source.
- The translated data is then loaded into staging areas as shown by
step 403. In the embodiment ofFIG. 2 , the translated data is loaded into staging areas stored onserver 240. In the embodiment shown inFIG. 3 , the translated data is loaded into staging areas 22-24. More particularly,analytic business component 12 loads translated data intostaging area 22. Similarly,analytic business component 13 loads translated data intostaging area 23 andanalytic business component 14 loads translated data intostaging area 24. - As shown by
step 404, the translated data is processed to obtain data having a common structure. In the embodiment shown inFIG. 2 ,server 240 is operable to process the translated data to obtain data having a common structure. - In the embodiment shown in
FIG. 3 , the processing ofstep 404 converts source-specific terminology into analytic data interface terminology. In the present embodiment, staging area objects are combined to match up the inputs and their interrelationship as required by theanalytic data interface 5. - Following are several specific examples of the conversion of source-specific terminology that is processed into analytic data interface terminology. It is appreciated that these examples are exemplary and that other source specific data is processed to be compatible with the inputs of the
analytic data interface 5. Data indicators and data indicator flags are configured based on the data. Physical deletions are performed and a delete flag is set to provide a common way to flag a record to be deleted. In addition, data type conversion and source-related clean up are performed. Also, unique key identification is configured based on the source and its data to take care of problems arising from the fact that the number of keys differ in each source. In the present embodiment, the set of rows that will be put in the data warehouse is also determined. - In the embodiment shown in
FIG. 3 , source adapters 32-33 are operable for processing the translated data within staging areas 22-23 to obtain data having a common structure. More particularly, source adapters 32-34 convert source-specific terminology into analytic data interface terminology. Source adapters are provided for each source with the exception of web logs, which do not require any further source-specific conversion. In the present embodiment, source adapters 32-33 combine extract-specific staging area objects into theanalytic data interface 5. In the present embodiment, source adapters 32-33 combine staging area objects to match up the inputs and their interrelationship as required by theanalytic data interface 5. - Continuing with
step 404 ofFIG. 4 , in the present embodiment source adapters 32-33 set the delete flag. More particularly, because each source handles deletes differently, there is a need to provide a uniform delete flag to the analytic data interface. To meet this need, source adapters 32-33 handle physical deletions and delete indicators and provide a common way to flag a record to be deleted. - In the present embodiment source adapters 32-33 handle data type conversions. More particularly, because the same concepts are represented differently in each source, there is a need to provide data type conversion. In the present embodiment, source adapters 32-33 publish the structure of each field and convert the data type using a consistent approach. In addition, source adapters 32-33 handle any source-related clean up.
- Continuing with
FIG. 3 , in the present embodiment source adapters 32-33 configure unique key identification based on the source and its data. This takes care of problems arising from the fact that the number of keys differ in each source. - Now referring to
FIG. 4 , the data having a common structure is transformed into a format suitable for loading into an analytic applications system such as a data warehousing application. In the present embodiment, the data having a common structure is transformed into a format suitable for loading into a data warehouse as shown by step 405. In the embodiment shown inFIG. 2 ,server 240 is operable to transform the data having a common structure into a format suitable for loading into a data warehouse. - In the present embodiment step 405 includes consolidation of business concepts into integrated structures that are suitable for querying and reporting. In addition, source definitions differences are normalized into a single, common definition. In the present embodiment, step 405 includes, for example, code lookup (e.g. currency conversion, unit of measure conversion and code to description field resolution), data-driven updates, intelligent expansion fields, dimension table specific features, fact table specific features, key resolution, key generation, and “bad” data flagging. In the present embodiment, the user can also insert, update, or reject a determination.
- In the embodiment shown in
FIG. 3 ,analytic data interface 5 is operable to transform data received from source adapters 32-33 andstaging area 24 into a format suitable for loading into a data mart. In the present embodiment,analytic data interface 5 provides complex transformation logic that integrates data in two ways. First, business concepts are consolidated across an entire value chain into integrated structures that are suitable for querying and reporting. In addition, theanalytic data interface 5 provides complex transformation logic that normalizes source definitions differences into a single, common definition. Some of the transformation logic performed in theanalytic data interface 5 include codes lookup (e.g. currency conversion, unit of measure conversion and code to description field resolution) and data-driven updates. In addition, intelligent expansion fields that extend out of the box capability such as pass through fields, codes fields, dare fields, money fields. Also, in the present embodiment, the analytic data interface includes dimension table specific features (e.g. surrogate key generation, slowly changing dimension support, and support for effective dates), fact table specific features (e.g. support for exchange rate lookup and support for dimension key lookup), key resolution, key generation, “bad” data flagging. In the present embodiment, the analytic data interface allows a user to insert, update, or reject a determination. - In the present embodiment,
analytic data interface 5 includes slowly changing dimension logic for tracking historically important data. A historically significant attribute is one that you want to retain for your records, even if subsequent records show that a change has been made. In the present embodiment, records within analytic data interface 5 can be configured using two different types of slowly changing dimension categories: historically insignificant attributes (Type 1 slowly changing dimensions) and historically significant attributes (Type 2 slowly changing dimensions). For type 1 slowly changing dimensions, the data field is simply overwritten. Although type 1 slowly changing dimensions does not maintain history, it is the simplest and fastest slowly changing dimension. Type 1 slowly changing dimension is used when the old value of the changed dimension is not deemed important or of interest to track, or is a historically insignificant attribute. For example, a user may want to use type 1 when changing incorrect values in a field. This way, there is no information for that record based on incorrect values. For example, when state name in a supplier table is a type 1 slowly changing dimension, upon changes to the state in which a supplier is located in, the previous value is overwritten (the previous state name) and the previous value is not saved. -
Type 2 slowly changing dimensions create a new record. This is the most common slowly changing dimension because it allows the user to track history. The old record allows for pointing to all history prior to the change, and the new record points to all history after the change. Because each change generates a new record, old and new records allow for partition history exactly. In the previous example, when state name in a supplier table is atype 2 slowly changing dimension, upon changes to the state in which a supplier is located in, a new, current record is generated. The previous value remains a record, and the new current record is a separate record. - The slowly changing dimension logic of the present invention gives four types of records that are stored in the staging area, new records, changed records with data that is not historically tracked, changed records having historical significance, and changed records having historical significance, and changed records whose changes have no significance of any kind.
- In one embodiment, a new customer key is used for the old sales record while the old customer key continues to be used for the new record. By assigning a new customer key, there is no need for a new addition to the customer table. A simple overwrite of the record showing the new combination suffices. As changed slowly changing dimension records come into a fact and dimension tables, the dimension table key is resolved only when both of the following facts are true: the key does not already exist in the data mart, and the key resolution attributes of the fact change.
- In the present embodiment, a predetermined alphanumeric character is used to indicate a need for data cleansing. That is, because most analytic data interface fields are mapped to fields in the transaction system, be it Ariba, ORMS or SAP, some fields may not be populated with values. For instance, a row in the supplier table may have information on a supplier's address, but may have no value in the supplier's region field. If a report is run on supplier prices by region, the suppliers for whom region information is missing would normally be excluded. However,
analytic data interface 5 provides a feature to identify all occurrences of missing values. In the present embodiment the identifier for missing values is a question mark (“?”). When the missing value fields are populated with the question mark, and a report is run on supplier prices by region, the suppliers for whom region information was missing are shown under a region identified by the character “?.” The question mark is a sign that the organization's data needs to be “cleansed.” - Cleansing the data in this case involves drilling into the category marked as “?” to learn, perhaps the supplier names or numbers within that group. The data warehouse administrator can then correct each of those suppliers by entering in the regional information on the back end.
- In the present embodiment, the logic for populating null fields is in the
analytic data interface 5. More particularly, the analytic data interface looks for columns that are both linked to a character data type and that are null, and populates them with a “?.” It is appreciated that the use of a character such as a question mark is simply the default setting to represent missing data. The present invention is well adapted for using a different character or multiple characters. - Because the data input into analytic data interface 5 has a common structure, there is no need to process data from each data source independently. More particularly, the data received at
analytic data interface 5 has already been translated to obtain meaningful business terms (step 402) and has been processed to obtain data having a common structure (step 404). Therefore, the data from different sources (e.g. databases 2-3 and web logs 4) can be treated as a single data source for the purpose of transformation (step 405). - In the present embodiment, because the analytic data interface includes a graphical user interface, it is easy to configure and customize how business data is loaded into an analytic applications system such as a data warehouse. In addition, because the analytic data interface includes a simplified abstraction layer for the data warehouse administrator, the warehouse administrator can configure how data is loaded into the analytic applications in a fraction of the time it takes to configure these capabilities programmatically. In addition, because most of the complex technical problems are solved prior to data entering the analytic data interface, without any required configuration or analysis by the warehouse administrator, the task of configuring data is greatly simplified. Thus, the present invention greatly simplifies the process of loading data into a data warehouse, saving significant expense and time.
- The benefits are particularly apparent for companies that use multiple different operational databases. More particularly, there is no need to define and program for data transport for each different operational database. The warehouse administrator needs only define and program for data transport a single time using the graphical user interface of the analytic data interface.
- In the present embodiment, maplets (reusable objects that represent a set of transformations) are used for code lookup, for address lookup, and for extraction. Also, maplets are used to identify all business locations and identify all business hierarchical structures.
- The transformed data is loaded into an analytic applications system such as a data warehousing application. In the embodiment shown in
FIG. 4 , the data is loaded into a data warehouse as shown by step 406. In the embodiment shown inFIG. 2 , the data is loaded into target databases 250-260 which can be databases of a data warehouse. In the embodiment shown inFIG. 3 , the data is loaded intodata warehouse 6. In addition, in the present embodiment, data is also loaded intooperational data store 7.Applications 8 then extract data fromdata warehouse 6 andoperational data store 7 for performing analysis. - The method and apparatus of the present invention are illustrated in the following example in which
database 2 is an Ariba database anddatabase 3 is a SAP database. In this embodiment,analytic business component 12 is an analytic business component for an Ariba database andanalytic business component 13 is an analytic business component for a SAP database. Thus, stagingarea 32 will contain data from an Ariba database that has been translated in order to include meaningful business terms, stagingarea 33 will contain data from an SAP database that has been translated in order to include meaningful business terms. Similarly, staging area 34 will contain data from web logs that has been translated in order to include meaningful business terms. In this embodiment,source adapter 32 will be an Ariba source adapter andsource adapter 33 will be a SAP source adapter while no source adapter is required for data fromweb logs 4. Because the data from each of sources 2-4 is provided toanalytic data interface 5, the data can be treated as a common data source for the purpose of transforming the data into a format suitable for loading into a data warehousing application (step 405 ofFIG. 4 ). Therefore, the warehouse administrator needs only define and program for data transport a single time using the graphical user interface of the analytic data interface. Not three separate times as would be required by prior art systems. - Accordingly, the present invention provides a method and apparatus that allows for transporting data such that the data can be used in data warehousing applications. In addition, the present invention provides a method and apparatus that takes advantage of the standardization of database components. Moreover, the present invention provides a method and apparatus that reduces the time required to define and program data transport for data warehousing applications.
- While the present invention has been described in particular embodiments, it should be appreciated that the present invention should not be construed as limited by such embodiments, but rather construed according to the below claims.
Claims (11)
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/877,370 US7117215B1 (en) | 2001-06-07 | 2001-06-07 | Method and apparatus for transporting data for data warehousing applications that incorporates analytic data interface |
PCT/US2001/019768 WO2002001415A2 (en) | 2000-06-26 | 2001-06-21 | Computer method and device for transporting data |
CA2414230A CA2414230C (en) | 2000-06-26 | 2001-06-21 | Computer method and device for transporting data |
EP01948540A EP1374090A2 (en) | 2000-06-26 | 2001-06-21 | Computer method and device for transporting data |
AU2001270013A AU2001270013A1 (en) | 2000-06-26 | 2001-06-21 | Computer method and device for transporting data |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/877,370 US7117215B1 (en) | 2001-06-07 | 2001-06-07 | Method and apparatus for transporting data for data warehousing applications that incorporates analytic data interface |
Publications (2)
Publication Number | Publication Date |
---|---|
US7117215B1 US7117215B1 (en) | 2006-10-03 |
US20060242160A1 true US20060242160A1 (en) | 2006-10-26 |
Family
ID=37037388
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/877,370 Expired - Lifetime US7117215B1 (en) | 2000-06-26 | 2001-06-07 | Method and apparatus for transporting data for data warehousing applications that incorporates analytic data interface |
Country Status (1)
Country | Link |
---|---|
US (1) | US7117215B1 (en) |
Cited By (35)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050216497A1 (en) * | 2004-03-26 | 2005-09-29 | Microsoft Corporation | Uniform financial reporting system interface utilizing staging tables having a standardized structure |
US20060112130A1 (en) * | 2004-11-24 | 2006-05-25 | Linda Lowson | System and method for resource management |
US7293026B1 (en) * | 2004-04-30 | 2007-11-06 | Ncr Corp. | Integrating a data warehouse and a database |
US20080052311A1 (en) * | 2003-01-13 | 2008-02-28 | Vasudev Rangadass | Master Data Management System for Centrally Managing Core Reference Data Associated with an Enterprise |
US20080162546A1 (en) * | 2006-12-29 | 2008-07-03 | Nadim Razvi | Monitoring Connection Between Computer System Layers |
US20080288522A1 (en) * | 2007-01-26 | 2008-11-20 | Herbert Dennis Hunt | Creating and storing a data field alteration datum using an analytic platform |
US20080294583A1 (en) * | 2007-01-26 | 2008-11-27 | Herbert Dennis Hunt | Similarity matching of a competitor's products |
US20080294372A1 (en) * | 2007-01-26 | 2008-11-27 | Herbert Dennis Hunt | Projection facility within an analytic platform |
US20080313225A1 (en) * | 2007-06-13 | 2008-12-18 | Spicer Peter F | Methods and Systems for Developing a Data Repository for Heterogeneous MLS Systems |
US20090012971A1 (en) * | 2007-01-26 | 2009-01-08 | Herbert Dennis Hunt | Similarity matching of products based on multiple classification schemes |
US20090193050A1 (en) * | 2008-01-25 | 2009-07-30 | Avaya Inc. | Report database dependency tracing through business intelligence metadata |
US7711104B1 (en) | 2004-03-31 | 2010-05-04 | Avaya Inc. | Multi-tasking tracking agent |
US7734032B1 (en) | 2004-03-31 | 2010-06-08 | Avaya Inc. | Contact center and method for tracking and acting on one and done customer contacts |
US7752230B2 (en) * | 2005-10-06 | 2010-07-06 | Avaya Inc. | Data extensibility using external database tables |
US7779042B1 (en) | 2005-08-08 | 2010-08-17 | Avaya Inc. | Deferred control of surrogate key generation in a distributed processing architecture |
US7787609B1 (en) | 2005-10-06 | 2010-08-31 | Avaya Inc. | Prioritized service delivery based on presence and availability of interruptible enterprise resources with skills |
US7809127B2 (en) | 2005-05-26 | 2010-10-05 | Avaya Inc. | Method for discovering problem agent behaviors |
US7822587B1 (en) | 2005-10-03 | 2010-10-26 | Avaya Inc. | Hybrid database architecture for both maintaining and relaxing type 2 data entity behavior |
US7936867B1 (en) | 2006-08-15 | 2011-05-03 | Avaya Inc. | Multi-service request within a contact center |
US7949121B1 (en) | 2004-09-27 | 2011-05-24 | Avaya Inc. | Method and apparatus for the simultaneous delivery of multiple contacts to an agent |
US8000989B1 (en) | 2004-03-31 | 2011-08-16 | Avaya Inc. | Using true value in routing work items to resources |
US8094804B2 (en) * | 2003-09-26 | 2012-01-10 | Avaya Inc. | Method and apparatus for assessing the status of work waiting for service |
US20120084770A1 (en) * | 2010-10-05 | 2012-04-05 | Sap Ag | Installing Analytical Content |
US8234141B1 (en) | 2004-09-27 | 2012-07-31 | Avaya Inc. | Dynamic work assignment strategies based on multiple aspects of agent proficiency |
US8260822B1 (en) | 2008-08-12 | 2012-09-04 | United Services Automobile Association (Usaa) | Systems and methods for storing and querying slowly changing dimensions |
US8391463B1 (en) | 2006-09-01 | 2013-03-05 | Avaya Inc. | Method and apparatus for identifying related contacts |
US8504534B1 (en) | 2007-09-26 | 2013-08-06 | Avaya Inc. | Database structures and administration techniques for generalized localization of database items |
US8565386B2 (en) | 2009-09-29 | 2013-10-22 | Avaya Inc. | Automatic configuration of soft phones that are usable in conjunction with special-purpose endpoints |
US8738412B2 (en) | 2004-07-13 | 2014-05-27 | Avaya Inc. | Method and apparatus for supporting individualized selection rules for resource allocation |
US8811597B1 (en) | 2006-09-07 | 2014-08-19 | Avaya Inc. | Contact center performance prediction |
US8938063B1 (en) | 2006-09-07 | 2015-01-20 | Avaya Inc. | Contact center service monitoring and correcting |
WO2016132253A1 (en) * | 2015-02-18 | 2016-08-25 | Persistent Systems Limited | Integrated intermediary computing device for data analytic enhancement |
US20160292186A1 (en) * | 2015-03-30 | 2016-10-06 | International Business Machines Corporation | Dynamically maintaining data structures driven by heterogeneous clients in a distributed data collection system |
US9466063B2 (en) | 2007-01-26 | 2016-10-11 | Information Resources, Inc. | Cluster processing of an aggregated dataset |
US9516069B2 (en) | 2009-11-17 | 2016-12-06 | Avaya Inc. | Packet headers as a trigger for automatic activation of special-purpose softphone applications |
Families Citing this family (55)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040210454A1 (en) * | 2003-02-26 | 2004-10-21 | Coughlin Bruce M. | System and method for providing technology data integration services |
US20050234969A1 (en) * | 2003-08-27 | 2005-10-20 | Ascential Software Corporation | Services oriented architecture for handling metadata in a data integration platform |
US20050240354A1 (en) * | 2003-08-27 | 2005-10-27 | Ascential Software Corporation | Service oriented architecture for an extract function in a data integration platform |
US20050223109A1 (en) * | 2003-08-27 | 2005-10-06 | Ascential Software Corporation | Data integration through a services oriented architecture |
US7814470B2 (en) * | 2003-08-27 | 2010-10-12 | International Business Machines Corporation | Multiple service bindings for a real time data integration service |
US20060010195A1 (en) * | 2003-08-27 | 2006-01-12 | Ascential Software Corporation | Service oriented architecture for a message broker in a data integration platform |
US8041760B2 (en) * | 2003-08-27 | 2011-10-18 | International Business Machines Corporation | Service oriented architecture for a loading function in a data integration platform |
US20050235274A1 (en) * | 2003-08-27 | 2005-10-20 | Ascential Software Corporation | Real time data integration for inventory management |
US8060553B2 (en) | 2003-08-27 | 2011-11-15 | International Business Machines Corporation | Service oriented architecture for a transformation function in a data integration platform |
US8307109B2 (en) * | 2003-08-27 | 2012-11-06 | International Business Machines Corporation | Methods and systems for real time integration services |
US20050232046A1 (en) * | 2003-08-27 | 2005-10-20 | Ascential Software Corporation | Location-based real time data integration services |
US20050262189A1 (en) * | 2003-08-27 | 2005-11-24 | Ascential Software Corporation | Server-side application programming interface for a real time data integration service |
US7814142B2 (en) * | 2003-08-27 | 2010-10-12 | International Business Machines Corporation | User interface service for a services oriented architecture in a data integration platform |
US7191160B2 (en) * | 2003-11-10 | 2007-03-13 | Sap Ag | Platform-independent data dictionary |
WO2005083563A2 (en) * | 2004-02-25 | 2005-09-09 | Siemens Medical Solutions Health Services Corporation | An executable application configuration system |
US7761406B2 (en) * | 2004-03-16 | 2010-07-20 | International Business Machines Corporation | Regenerating data integration functions for transfer from a data integration platform |
US20050251533A1 (en) * | 2004-03-16 | 2005-11-10 | Ascential Software Corporation | Migrating data integration processes through use of externalized metadata representations |
US20060004801A1 (en) * | 2004-05-03 | 2006-01-05 | Hoefer Felix F | Data consistency in a multi-layer datawarehouse |
JP2005321849A (en) * | 2004-05-06 | 2005-11-17 | Fujitsu Ltd | Data analysis support program, method, and device |
US8732696B2 (en) * | 2004-09-30 | 2014-05-20 | Sap Aktiengesellschaft | Analytic application model and marketplace |
US7536394B1 (en) * | 2004-11-23 | 2009-05-19 | Lockheed Martin Corporation | Operational information management system |
US7634492B2 (en) * | 2004-12-20 | 2009-12-15 | Microsoft Corporation | Aggregate data view |
US7587388B2 (en) * | 2005-07-28 | 2009-09-08 | Microsoft Corporation | Separating uploads into aggregate and raw data storage |
US8090658B2 (en) * | 2006-06-23 | 2012-01-03 | International Business Machines Corporation | System and method of member unique names |
WO2008002578A2 (en) | 2006-06-26 | 2008-01-03 | Nielsen Media Research, Inc. | Methods and apparatus for improving data warehouse performance |
US7984115B2 (en) * | 2006-12-08 | 2011-07-19 | Microsoft Corporation | Extensible application platform |
EP2122487A4 (en) * | 2007-01-16 | 2011-02-02 | Timmins Software Corp | Systems and methods for analyzing information technology systems using collaborative intelligence |
US20080177892A1 (en) * | 2007-01-19 | 2008-07-24 | International Business Machines Corporation | Method for service oriented data extraction transformation and load |
US8234240B2 (en) * | 2007-04-26 | 2012-07-31 | Microsoft Corporation | Framework for providing metrics from any datasource |
US8533661B2 (en) | 2007-04-27 | 2013-09-10 | Dell Products, Lp | System and method for automated on-demand creation of a customized software application |
US8136087B2 (en) * | 2007-07-24 | 2012-03-13 | International Business Machines Corporation | In-line processing of standardized text values |
CN103762723B (en) * | 2008-05-09 | 2017-04-12 | 埃森哲环球服务有限公司 | Method and system for managing a power grid |
US20100211539A1 (en) * | 2008-06-05 | 2010-08-19 | Ho Luy | System and method for building a data warehouse |
US20100076935A1 (en) * | 2008-09-09 | 2010-03-25 | Ahmir Hussain | Method, system, and computer for analytical reporting and archiving of data |
US7970728B2 (en) * | 2008-10-23 | 2011-06-28 | International Business Machines Corporation | Dynamically building and populating data marts with data stored in repositories |
US10096064B2 (en) * | 2008-11-06 | 2018-10-09 | Thomson Reuters Global Resources Unlimited Company | Method and system for source document data entry and form association |
US8626790B2 (en) | 2010-04-23 | 2014-01-07 | Hartford Fire Insurance Company | System and method for processing and analyzing dimension data |
US10671628B2 (en) * | 2010-07-09 | 2020-06-02 | State Street Bank And Trust Company | Systems and methods for data warehousing |
US8943076B2 (en) | 2012-02-06 | 2015-01-27 | Dell Products, Lp | System to automate mapping of variables between business process applications and method therefor |
WO2013135636A2 (en) * | 2012-03-12 | 2013-09-19 | Icon Clinical Research Limited | A clinical data management system |
US8805716B2 (en) | 2012-03-19 | 2014-08-12 | Dell Products, Lp | Dashboard system and method for identifying and monitoring process errors and throughput of integration software |
US8782103B2 (en) | 2012-04-13 | 2014-07-15 | Dell Products, Lp | Monitoring system for optimizing integrated business processes to work flow |
US9015106B2 (en) | 2012-04-30 | 2015-04-21 | Dell Products, Lp | Cloud based master data management system and method therefor |
US8589207B1 (en) | 2012-05-15 | 2013-11-19 | Dell Products, Lp | System and method for determining and visually predicting at-risk integrated processes based on age and activity |
US9069898B2 (en) | 2012-05-31 | 2015-06-30 | Dell Products, Lp | System for providing regression testing of an integrated process development system and method therefor |
US9092244B2 (en) | 2012-06-07 | 2015-07-28 | Dell Products, Lp | System for developing custom data transformations for system integration application programs |
US9443229B2 (en) | 2013-03-15 | 2016-09-13 | Elemica, Inc. | Supply chain message management and shipment constraint optimization |
US9224135B2 (en) | 2013-03-15 | 2015-12-29 | Elemica, Inc. | Method and apparatus for adaptive configuration for translation of business messages |
US8904528B2 (en) | 2013-03-15 | 2014-12-02 | Elemica, Inc. | Method and apparatus for translation of business messages |
US10997556B2 (en) * | 2013-04-08 | 2021-05-04 | Oracle International Corporation | Summarizing tabular data across multiple projects using user-defined attributes |
US9519695B2 (en) | 2013-04-16 | 2016-12-13 | Cognizant Technology Solutions India Pvt. Ltd. | System and method for automating data warehousing processes |
US9183074B2 (en) | 2013-06-21 | 2015-11-10 | Dell Products, Lp | Integration process management console with error resolution interface |
US9904706B2 (en) * | 2013-09-06 | 2018-02-27 | International Business Machines Corporation | Deferring data record changes using query rewriting |
US9690832B2 (en) | 2014-10-06 | 2017-06-27 | Netapp, Inc. | Enterprise reporting capabilities in storage management systems |
US10498858B2 (en) | 2016-12-14 | 2019-12-03 | Dell Products, Lp | System and method for automated on-demand creation of and execution of a customized data integration software application |
Citations (99)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5403147A (en) * | 1991-06-28 | 1995-04-04 | Kao Corporation | Method for warehousing and delivery of articles |
US5404513A (en) * | 1990-03-16 | 1995-04-04 | Dimensional Insight, Inc. | Method for building a database with multi-dimensional search tree nodes |
US5405531A (en) * | 1993-02-16 | 1995-04-11 | Geo-Microbial Technologies, Inc. | Method for reducing the amount of and preventing the formation of hydrogen sulfide in an aqueous system |
US5410688A (en) * | 1989-07-21 | 1995-04-25 | Hewlett-Packard Company | Distributed object based systems for communicating object data among different storage domains |
US5455945A (en) * | 1993-05-19 | 1995-10-03 | Vanderdrift; Richard | System and method for dynamically displaying entering, and updating data from a database |
US5511190A (en) * | 1995-01-20 | 1996-04-23 | Tandem Computers, Inc. | Hash-based database grouping system and method |
US5519859A (en) * | 1993-11-15 | 1996-05-21 | Grace; John A. | Method and apparatus for automatic table selection and generation of structured query language instructions |
US5537589A (en) * | 1994-06-30 | 1996-07-16 | Microsoft Corporation | Method and system for efficiently performing database table aggregation using an aggregation index |
US5563999A (en) * | 1990-10-19 | 1996-10-08 | Moore Business Forms, Inc. | Forms automation system |
US5603024A (en) * | 1993-10-08 | 1997-02-11 | International Business Machines Corporation | Lossless distribution of time series data in a relational data base network |
US5655101A (en) * | 1993-06-01 | 1997-08-05 | International Business Machines Corporation | Accessing remote data objects in a distributed memory environment using parallel address locations at each local memory to reference a same data object |
US5675785A (en) * | 1994-10-04 | 1997-10-07 | Hewlett-Packard Company | Data warehouse which is accessed by a user using a schema of virtual tables |
US5706495A (en) * | 1996-05-07 | 1998-01-06 | International Business Machines Corporation | Encoded-vector indices for decision support and warehousing |
US5708828A (en) * | 1995-05-25 | 1998-01-13 | Reliant Data Systems | System for converting data from input data environment using first format to output data environment using second format by executing the associations between their fields |
US5713020A (en) * | 1993-09-02 | 1998-01-27 | Microsoft Corporation | Method and system for generating database queries containing multiple levels of aggregation |
US5721911A (en) * | 1996-06-25 | 1998-02-24 | International Business Machines Corporation | Mechanism for metadata for an information catalog system |
US5721903A (en) * | 1995-10-12 | 1998-02-24 | Ncr Corporation | System and method for generating reports from a computer database |
US5778355A (en) * | 1996-06-11 | 1998-07-07 | International Business Machines Corp. | Database method and apparatus for interactively retrieving data members and related members from a collection of data |
US5781911A (en) * | 1996-09-10 | 1998-07-14 | D2K, Incorporated | Integrated system and method of data warehousing and delivery |
US5787415A (en) * | 1996-10-30 | 1998-07-28 | International Business Machines Corporation | Low maintenance data delivery and refresh system for decision support system database |
US5794228A (en) * | 1993-04-16 | 1998-08-11 | Sybase, Inc. | Database system with buffer manager providing per page native data compression and decompression |
US5794246A (en) * | 1997-04-30 | 1998-08-11 | Informatica Corporation | Method for incremental aggregation of dynamically increasing database data sets |
US5794229A (en) * | 1993-04-16 | 1998-08-11 | Sybase, Inc. | Database system with methodology for storing a database table by vertically partitioning all columns of the table |
US5794030A (en) * | 1995-12-04 | 1998-08-11 | Objectivity, Inc. | System and method for maintenance and deferred propagation of schema changes to the affected objects in an object oriented database |
US5799310A (en) * | 1995-05-01 | 1998-08-25 | International Business Machines Corporation | Relational database extenders for handling complex data types |
US5806060A (en) * | 1992-11-06 | 1998-09-08 | Ncr Corporation | Interactive data analysis employing a knowledge base |
US5822751A (en) * | 1996-12-16 | 1998-10-13 | Microsoft Corporation | Efficient multidimensional data aggregation operator implementation |
US5826258A (en) * | 1996-10-02 | 1998-10-20 | Junglee Corporation | Method and apparatus for structuring the querying and interpretation of semistructured information |
US5857197A (en) * | 1997-03-20 | 1999-01-05 | Thought Inc. | System and method for accessing data stores as objects |
US5870746A (en) * | 1995-10-12 | 1999-02-09 | Ncr Corporation | System and method for segmenting a database based upon data attributes |
US5870747A (en) * | 1996-07-09 | 1999-02-09 | Informix Software, Inc. | Generalized key indexes |
US5873102A (en) * | 1997-04-29 | 1999-02-16 | Oracle Corporation | Pluggable tablespaces on a transportable medium |
US5884262A (en) * | 1996-03-28 | 1999-03-16 | Bell Atlantic Network Services, Inc. | Computer network audio access and conversion system |
US5898431A (en) * | 1996-12-31 | 1999-04-27 | International Business Machines Corporation | Database graphical user interface with calendar view |
US5915019A (en) * | 1995-02-13 | 1999-06-22 | Intertrust Technologies Corp. | Systems and methods for secure transaction management and electronic rights protection |
US5933796A (en) * | 1996-08-09 | 1999-08-03 | Hitachi, Ltd. | Data extracting system based on characteristic quantities of data distribution |
US5970464A (en) * | 1997-09-10 | 1999-10-19 | International Business Machines Corporation | Data mining based underwriting profitability analysis |
US6014670A (en) * | 1997-11-07 | 2000-01-11 | Informatica Corporation | Apparatus and method for performing data transformations in data warehousing |
US6026388A (en) * | 1995-08-16 | 2000-02-15 | Textwise, Llc | User interface and other enhancements for natural language information retrieval system and method |
US6032145A (en) * | 1998-04-10 | 2000-02-29 | Requisite Technology, Inc. | Method and system for database manipulation |
US6032158A (en) * | 1997-05-02 | 2000-02-29 | Informatica Corporation | Apparatus and method for capturing and propagating changes from an operational database to data marts |
US6044374A (en) * | 1997-11-14 | 2000-03-28 | Informatica Corporation | Method and apparatus for sharing metadata between multiple data marts through object references |
US6065007A (en) * | 1998-04-28 | 2000-05-16 | Lucent Technologies Inc. | Computer method, apparatus and programmed medium for approximating large databases and improving search efficiency |
US6072492A (en) * | 1996-12-04 | 2000-06-06 | U.S. Philips Corporation | Selecting an information item in an information processing system |
US6078994A (en) * | 1997-05-30 | 2000-06-20 | Oracle Corporation | System for maintaining a shared cache in a multi-threaded computer environment |
US6119167A (en) * | 1997-07-11 | 2000-09-12 | Phone.Com, Inc. | Pushing and pulling data in networks |
US6122628A (en) * | 1997-10-31 | 2000-09-19 | International Business Machines Corporation | Multidimensional data clustering and dimension reduction for indexing and searching |
US6128624A (en) * | 1997-11-12 | 2000-10-03 | Ncr Corporation | Collection and integration of internet and electronic commerce data in a database during web browsing |
US6141699A (en) * | 1998-05-11 | 2000-10-31 | International Business Machines Corporation | Interactive display system for sequential retrieval and display of a plurality of interrelated data sets |
US6173310B1 (en) * | 1999-03-23 | 2001-01-09 | Microstrategy, Inc. | System and method for automatic transmission of on-line analytical processing system report output |
US6192364B1 (en) * | 1998-07-24 | 2001-02-20 | Jarg Corporation | Distributed computer database system and method employing intelligent agents |
US6205472B1 (en) * | 1998-09-18 | 2001-03-20 | Tacit Knowledge System, Inc. | Method and apparatus for querying a user knowledge profile |
US6208990B1 (en) * | 1998-07-15 | 2001-03-27 | Informatica Corporation | Method and architecture for automated optimization of ETL throughput in data warehousing applications |
US6216125B1 (en) * | 1998-07-02 | 2001-04-10 | At&T Corp. | Coarse indexes for a data warehouse |
US6233575B1 (en) * | 1997-06-24 | 2001-05-15 | International Business Machines Corporation | Multilevel taxonomy based on features derived from training documents classification using fisher values as discrimination values |
US6262598B1 (en) * | 1999-03-05 | 2001-07-17 | Sharp Kabushiki Kaisha | Voltage level shifter |
US6269336B1 (en) * | 1998-07-24 | 2001-07-31 | Motorola, Inc. | Voice browser for interactive services and methods thereof |
US6269369B1 (en) * | 1997-11-02 | 2001-07-31 | Amazon.Com Holdings, Inc. | Networked personal contact manager |
US6272485B1 (en) * | 1999-02-18 | 2001-08-07 | Creative Internet Applications, Inc. | Transferring selected formatted documents over a computer network using interface script |
US6292657B1 (en) * | 1998-07-13 | 2001-09-18 | Openwave Systems Inc. | Method and architecture for managing a fleet of mobile stations over wireless data networks |
US6336137B1 (en) * | 2000-03-31 | 2002-01-01 | Siebel Systems, Inc. | Web client-server system and method for incompatible page markup and presentation languages |
US6339775B1 (en) * | 1997-11-07 | 2002-01-15 | Informatica Corporation | Apparatus and method for performing data transformations in data warehousing |
US20020035565A1 (en) * | 2000-04-27 | 2002-03-21 | Arun Shah | Graphical user interface for relational database |
US6369840B1 (en) * | 1999-03-10 | 2002-04-09 | America Online, Inc. | Multi-layered online calendaring and purchasing |
US6385604B1 (en) * | 1999-08-04 | 2002-05-07 | Hyperroll, Israel Limited | Relational database management system having integrated non-relational multi-dimensional data store of aggregated data elements |
US20020056081A1 (en) * | 1999-12-02 | 2002-05-09 | Qualcomm Incorporated | Apparatus and method for decoding digital image and audio signals |
US20020059267A1 (en) * | 2000-04-17 | 2002-05-16 | Arun Shah | Analytical server including metrics engine |
US6393386B1 (en) * | 1998-03-26 | 2002-05-21 | Visual Networks Technologies, Inc. | Dynamic modeling of complex networks and prediction of impacts of faults therein |
US6404884B1 (en) * | 1999-10-08 | 2002-06-11 | Grape Technology Group, Inc. | Personalized assistance system and method |
US6408292B1 (en) * | 1999-08-04 | 2002-06-18 | Hyperroll, Israel, Ltd. | Method of and system for managing multi-dimensional databases using modular-arithmetic based address data mapping processes on integer-encoded business dimensions |
US20020077787A1 (en) * | 2000-12-18 | 2002-06-20 | Theodore Rappaport | Textual and graphical demarcation of location, and interpretation of measurements |
US6411936B1 (en) * | 1999-02-05 | 2002-06-25 | Nval Solutions, Inc. | Enterprise value enhancement system and method |
US6418200B1 (en) * | 1999-02-26 | 2002-07-09 | Mitel, Inc. | Automatic synchronization of address directories for unified messaging |
US6421781B1 (en) * | 1998-04-30 | 2002-07-16 | Openwave Systems Inc. | Method and apparatus for maintaining security in a push server |
US6424426B1 (en) * | 2000-03-28 | 2002-07-23 | Mongonet | Fax-to-email and email-to-fax communication system and method |
US20020099691A1 (en) * | 1998-06-24 | 2002-07-25 | Michael Dean Lore | Method and apparatus for aggregation of data in a database management system |
US6430624B1 (en) * | 1999-10-21 | 2002-08-06 | Air2Web, Inc. | Intelligent harvesting and navigation system and method |
US20020112237A1 (en) * | 2000-04-10 | 2002-08-15 | Kelts Brett R. | System and method for providing an interactive display interface for information objects |
US6438522B1 (en) * | 1998-11-30 | 2002-08-20 | Matsushita Electric Industrial Co., Ltd. | Method and apparatus for speech synthesis whereby waveform segments expressing respective syllables of a speech item are modified in accordance with rhythm, pitch and speech power patterns expressed by a prosodic template |
US6446062B1 (en) * | 1999-12-23 | 2002-09-03 | Bull Hn Information Systems Inc. | Method and apparatus for improving the performance of a generated code cache search operation through the use of static key values |
US6446059B1 (en) * | 1999-06-22 | 2002-09-03 | Microsoft Corporation | Record for a multidimensional database with flexible paths |
US6446096B1 (en) * | 1998-09-11 | 2002-09-03 | International Business Machines Corporation | Method and system for providing device-specific key control using role-based HTML element tags |
US6449619B1 (en) * | 1999-06-23 | 2002-09-10 | Datamirror Corporation | Method and apparatus for pipelining the transformation of information between heterogeneous sets of data sources |
US6457030B1 (en) * | 1999-01-29 | 2002-09-24 | International Business Machines Corporation | Systems, methods and computer program products for modifying web content for display via pervasive computing devices |
US6535872B1 (en) * | 1999-04-08 | 2003-03-18 | International Business Machines Corporation | Method and apparatus for dynamically representing aggregated and segmented data views using view element sets |
US6539359B1 (en) * | 1998-10-02 | 2003-03-25 | Motorola, Inc. | Markup language for interactive services and methods thereof |
US6549910B1 (en) * | 1998-10-02 | 2003-04-15 | Ncr Corporation | SQI-based automated, adaptive, histogram bin data description assist |
US6549937B1 (en) * | 1999-07-21 | 2003-04-15 | Microsoft Corporation | System and method for multi-protocol communication in a computer network |
US6553366B1 (en) * | 1998-10-02 | 2003-04-22 | Ncr Corporation | Analytic logical data model |
US6563912B1 (en) * | 1999-03-02 | 2003-05-13 | Toshiba America Information Systems, Inc. | System and method for providing integrated messaging |
US6564264B1 (en) * | 1999-12-08 | 2003-05-13 | At&T Corp. | System, apparatus and method for automatic address updating of outgoing and incoming user messages in a communications network |
US6574599B1 (en) * | 1999-03-31 | 2003-06-03 | Microsoft Corporation | Voice-recognition-based methods for establishing outbound communication through a unified messaging system including intelligent calendar interface |
US6581062B1 (en) * | 2000-03-02 | 2003-06-17 | Nimble Technology, Inc. | Method and apparatus for storing semi-structured data in a structured manner |
US6587857B1 (en) * | 1998-06-30 | 2003-07-01 | Citicorp Development Center, Inc. | System and method for warehousing and retrieving data |
US6601062B1 (en) * | 2000-06-27 | 2003-07-29 | Ncr Corporation | Active caching for multi-dimensional data sets in relational database management system |
US6616701B2 (en) * | 1998-05-23 | 2003-09-09 | Eolas Technologies, Inc. | Method and apparatus for identifying features of multidimensional image data in hypermedia systems |
US6629102B1 (en) * | 2000-07-28 | 2003-09-30 | International Business Machines Corporation | Efficiently updating a key table during outline restructure of a multi-dimensional database |
US6721728B2 (en) * | 2001-03-02 | 2004-04-13 | The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration | System, method and apparatus for discovering phrases in a database |
US6736870B2 (en) * | 2000-09-29 | 2004-05-18 | Thomas Josef Heimbach Gesellschaft Mit Beschrankter Haftung | Filter device |
Family Cites Families (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5420688A (en) | 1992-12-14 | 1995-05-30 | Farah; John | Interferometric fiber optic displacement sensor |
US5692181A (en) | 1995-10-12 | 1997-11-25 | Ncr Corporation | System and method for generating reports from a computer database |
US5832496A (en) | 1995-10-12 | 1998-11-03 | Ncr Corporation | System and method for performing intelligent analysis of a computer database |
US5689566A (en) | 1995-10-24 | 1997-11-18 | Nguyen; Minhtam C. | Network with secure communications sessions |
US5991742A (en) | 1996-05-20 | 1999-11-23 | Tran; Bao Q. | Time and expense logging system |
JPH09311806A (en) | 1996-05-24 | 1997-12-02 | Hitachi Ltd | Method for detecting illegal update of data |
US5854890A (en) | 1996-10-15 | 1998-12-29 | National Instruments Corporation | Fieldbus function block shell with user selectable data ownership |
US5848415A (en) | 1996-12-18 | 1998-12-08 | Unisys Corporation | Selective multiple protocol transport and dynamic format conversion in a multi-user network |
US5842213A (en) | 1997-01-28 | 1998-11-24 | Odom; Paul S. | Method for modeling, storing, and transferring data in neutral form |
US6002402A (en) | 1997-04-09 | 1999-12-14 | Symantec Corporation | System and method for producing a drag-and-drop object from a popup menu item |
US5987454A (en) | 1997-06-09 | 1999-11-16 | Hobbs; Allen | Method and apparatus for selectively augmenting retrieved text, numbers, maps, charts, still pictures and/or graphics, moving pictures and/or graphics and audio information from a network resource |
JP3423577B2 (en) | 1997-06-18 | 2003-07-07 | 古河電気工業株式会社 | Power supply control device for vehicles with battery dead prevention function |
US5999924A (en) * | 1997-07-25 | 1999-12-07 | Amazon.Com, Inc. | Method and apparatus for producing sequenced queries |
JP3922482B2 (en) | 1997-10-14 | 2007-05-30 | ソニー株式会社 | Information processing apparatus and method |
US6151601A (en) * | 1997-11-12 | 2000-11-21 | Ncr Corporation | Computer architecture and method for collecting, analyzing and/or transforming internet and/or electronic commerce data for storage into a data storage area |
US6151584A (en) | 1997-11-20 | 2000-11-21 | Ncr Corporation | Computer architecture and method for validating and collecting and metadata and data about the internet and electronic commerce environments (data discoverer) |
EP0949787A1 (en) | 1998-03-18 | 1999-10-13 | Sony International (Europe) GmbH | Multiple personality internet account |
EP0944003A1 (en) | 1998-03-18 | 1999-09-22 | SONY EUROPE GmbH | Notification subsystem |
US6477525B1 (en) * | 1998-12-28 | 2002-11-05 | Oracle Corporation | Rewriting a query in terms of a summary based on one-to-one and one-to-many losslessness of joins |
US6493800B1 (en) | 1999-03-31 | 2002-12-10 | International Business Machines Corporation | Method and system for dynamically partitioning a shared cache |
CA2311884A1 (en) * | 2000-06-16 | 2001-12-16 | Cognos Incorporated | Method of managing slowly changing dimensions |
US6502101B1 (en) | 2000-07-13 | 2002-12-31 | Microsoft Corporation | Converting a hierarchical data structure into a flat data structure |
-
2001
- 2001-06-07 US US09/877,370 patent/US7117215B1/en not_active Expired - Lifetime
Patent Citations (99)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5410688A (en) * | 1989-07-21 | 1995-04-25 | Hewlett-Packard Company | Distributed object based systems for communicating object data among different storage domains |
US5404513A (en) * | 1990-03-16 | 1995-04-04 | Dimensional Insight, Inc. | Method for building a database with multi-dimensional search tree nodes |
US5563999A (en) * | 1990-10-19 | 1996-10-08 | Moore Business Forms, Inc. | Forms automation system |
US5403147A (en) * | 1991-06-28 | 1995-04-04 | Kao Corporation | Method for warehousing and delivery of articles |
US5806060A (en) * | 1992-11-06 | 1998-09-08 | Ncr Corporation | Interactive data analysis employing a knowledge base |
US5405531A (en) * | 1993-02-16 | 1995-04-11 | Geo-Microbial Technologies, Inc. | Method for reducing the amount of and preventing the formation of hydrogen sulfide in an aqueous system |
US5794228A (en) * | 1993-04-16 | 1998-08-11 | Sybase, Inc. | Database system with buffer manager providing per page native data compression and decompression |
US5794229A (en) * | 1993-04-16 | 1998-08-11 | Sybase, Inc. | Database system with methodology for storing a database table by vertically partitioning all columns of the table |
US5455945A (en) * | 1993-05-19 | 1995-10-03 | Vanderdrift; Richard | System and method for dynamically displaying entering, and updating data from a database |
US5655101A (en) * | 1993-06-01 | 1997-08-05 | International Business Machines Corporation | Accessing remote data objects in a distributed memory environment using parallel address locations at each local memory to reference a same data object |
US5713020A (en) * | 1993-09-02 | 1998-01-27 | Microsoft Corporation | Method and system for generating database queries containing multiple levels of aggregation |
US5603024A (en) * | 1993-10-08 | 1997-02-11 | International Business Machines Corporation | Lossless distribution of time series data in a relational data base network |
US5519859A (en) * | 1993-11-15 | 1996-05-21 | Grace; John A. | Method and apparatus for automatic table selection and generation of structured query language instructions |
US5537589A (en) * | 1994-06-30 | 1996-07-16 | Microsoft Corporation | Method and system for efficiently performing database table aggregation using an aggregation index |
US5675785A (en) * | 1994-10-04 | 1997-10-07 | Hewlett-Packard Company | Data warehouse which is accessed by a user using a schema of virtual tables |
US5511190A (en) * | 1995-01-20 | 1996-04-23 | Tandem Computers, Inc. | Hash-based database grouping system and method |
US5915019A (en) * | 1995-02-13 | 1999-06-22 | Intertrust Technologies Corp. | Systems and methods for secure transaction management and electronic rights protection |
US5799310A (en) * | 1995-05-01 | 1998-08-25 | International Business Machines Corporation | Relational database extenders for handling complex data types |
US5708828A (en) * | 1995-05-25 | 1998-01-13 | Reliant Data Systems | System for converting data from input data environment using first format to output data environment using second format by executing the associations between their fields |
US6026388A (en) * | 1995-08-16 | 2000-02-15 | Textwise, Llc | User interface and other enhancements for natural language information retrieval system and method |
US5721903A (en) * | 1995-10-12 | 1998-02-24 | Ncr Corporation | System and method for generating reports from a computer database |
US5870746A (en) * | 1995-10-12 | 1999-02-09 | Ncr Corporation | System and method for segmenting a database based upon data attributes |
US5794030A (en) * | 1995-12-04 | 1998-08-11 | Objectivity, Inc. | System and method for maintenance and deferred propagation of schema changes to the affected objects in an object oriented database |
US5884262A (en) * | 1996-03-28 | 1999-03-16 | Bell Atlantic Network Services, Inc. | Computer network audio access and conversion system |
US5706495A (en) * | 1996-05-07 | 1998-01-06 | International Business Machines Corporation | Encoded-vector indices for decision support and warehousing |
US5778355A (en) * | 1996-06-11 | 1998-07-07 | International Business Machines Corp. | Database method and apparatus for interactively retrieving data members and related members from a collection of data |
US5721911A (en) * | 1996-06-25 | 1998-02-24 | International Business Machines Corporation | Mechanism for metadata for an information catalog system |
US5870747A (en) * | 1996-07-09 | 1999-02-09 | Informix Software, Inc. | Generalized key indexes |
US5933796A (en) * | 1996-08-09 | 1999-08-03 | Hitachi, Ltd. | Data extracting system based on characteristic quantities of data distribution |
US5781911A (en) * | 1996-09-10 | 1998-07-14 | D2K, Incorporated | Integrated system and method of data warehousing and delivery |
US5826258A (en) * | 1996-10-02 | 1998-10-20 | Junglee Corporation | Method and apparatus for structuring the querying and interpretation of semistructured information |
US5787415A (en) * | 1996-10-30 | 1998-07-28 | International Business Machines Corporation | Low maintenance data delivery and refresh system for decision support system database |
US6072492A (en) * | 1996-12-04 | 2000-06-06 | U.S. Philips Corporation | Selecting an information item in an information processing system |
US5822751A (en) * | 1996-12-16 | 1998-10-13 | Microsoft Corporation | Efficient multidimensional data aggregation operator implementation |
US5898431A (en) * | 1996-12-31 | 1999-04-27 | International Business Machines Corporation | Database graphical user interface with calendar view |
US5857197A (en) * | 1997-03-20 | 1999-01-05 | Thought Inc. | System and method for accessing data stores as objects |
US5873102A (en) * | 1997-04-29 | 1999-02-16 | Oracle Corporation | Pluggable tablespaces on a transportable medium |
US5794246A (en) * | 1997-04-30 | 1998-08-11 | Informatica Corporation | Method for incremental aggregation of dynamically increasing database data sets |
US6032158A (en) * | 1997-05-02 | 2000-02-29 | Informatica Corporation | Apparatus and method for capturing and propagating changes from an operational database to data marts |
US6078994A (en) * | 1997-05-30 | 2000-06-20 | Oracle Corporation | System for maintaining a shared cache in a multi-threaded computer environment |
US6233575B1 (en) * | 1997-06-24 | 2001-05-15 | International Business Machines Corporation | Multilevel taxonomy based on features derived from training documents classification using fisher values as discrimination values |
US6119167A (en) * | 1997-07-11 | 2000-09-12 | Phone.Com, Inc. | Pushing and pulling data in networks |
US5970464A (en) * | 1997-09-10 | 1999-10-19 | International Business Machines Corporation | Data mining based underwriting profitability analysis |
US6122628A (en) * | 1997-10-31 | 2000-09-19 | International Business Machines Corporation | Multidimensional data clustering and dimension reduction for indexing and searching |
US6269369B1 (en) * | 1997-11-02 | 2001-07-31 | Amazon.Com Holdings, Inc. | Networked personal contact manager |
US6014670A (en) * | 1997-11-07 | 2000-01-11 | Informatica Corporation | Apparatus and method for performing data transformations in data warehousing |
US6339775B1 (en) * | 1997-11-07 | 2002-01-15 | Informatica Corporation | Apparatus and method for performing data transformations in data warehousing |
US6128624A (en) * | 1997-11-12 | 2000-10-03 | Ncr Corporation | Collection and integration of internet and electronic commerce data in a database during web browsing |
US6044374A (en) * | 1997-11-14 | 2000-03-28 | Informatica Corporation | Method and apparatus for sharing metadata between multiple data marts through object references |
US6393386B1 (en) * | 1998-03-26 | 2002-05-21 | Visual Networks Technologies, Inc. | Dynamic modeling of complex networks and prediction of impacts of faults therein |
US6032145A (en) * | 1998-04-10 | 2000-02-29 | Requisite Technology, Inc. | Method and system for database manipulation |
US6065007A (en) * | 1998-04-28 | 2000-05-16 | Lucent Technologies Inc. | Computer method, apparatus and programmed medium for approximating large databases and improving search efficiency |
US6421781B1 (en) * | 1998-04-30 | 2002-07-16 | Openwave Systems Inc. | Method and apparatus for maintaining security in a push server |
US6141699A (en) * | 1998-05-11 | 2000-10-31 | International Business Machines Corporation | Interactive display system for sequential retrieval and display of a plurality of interrelated data sets |
US6616701B2 (en) * | 1998-05-23 | 2003-09-09 | Eolas Technologies, Inc. | Method and apparatus for identifying features of multidimensional image data in hypermedia systems |
US20020099691A1 (en) * | 1998-06-24 | 2002-07-25 | Michael Dean Lore | Method and apparatus for aggregation of data in a database management system |
US6587857B1 (en) * | 1998-06-30 | 2003-07-01 | Citicorp Development Center, Inc. | System and method for warehousing and retrieving data |
US6216125B1 (en) * | 1998-07-02 | 2001-04-10 | At&T Corp. | Coarse indexes for a data warehouse |
US6292657B1 (en) * | 1998-07-13 | 2001-09-18 | Openwave Systems Inc. | Method and architecture for managing a fleet of mobile stations over wireless data networks |
US6208990B1 (en) * | 1998-07-15 | 2001-03-27 | Informatica Corporation | Method and architecture for automated optimization of ETL throughput in data warehousing applications |
US6192364B1 (en) * | 1998-07-24 | 2001-02-20 | Jarg Corporation | Distributed computer database system and method employing intelligent agents |
US6269336B1 (en) * | 1998-07-24 | 2001-07-31 | Motorola, Inc. | Voice browser for interactive services and methods thereof |
US6446096B1 (en) * | 1998-09-11 | 2002-09-03 | International Business Machines Corporation | Method and system for providing device-specific key control using role-based HTML element tags |
US6205472B1 (en) * | 1998-09-18 | 2001-03-20 | Tacit Knowledge System, Inc. | Method and apparatus for querying a user knowledge profile |
US6553366B1 (en) * | 1998-10-02 | 2003-04-22 | Ncr Corporation | Analytic logical data model |
US6539359B1 (en) * | 1998-10-02 | 2003-03-25 | Motorola, Inc. | Markup language for interactive services and methods thereof |
US6549910B1 (en) * | 1998-10-02 | 2003-04-15 | Ncr Corporation | SQI-based automated, adaptive, histogram bin data description assist |
US6438522B1 (en) * | 1998-11-30 | 2002-08-20 | Matsushita Electric Industrial Co., Ltd. | Method and apparatus for speech synthesis whereby waveform segments expressing respective syllables of a speech item are modified in accordance with rhythm, pitch and speech power patterns expressed by a prosodic template |
US6457030B1 (en) * | 1999-01-29 | 2002-09-24 | International Business Machines Corporation | Systems, methods and computer program products for modifying web content for display via pervasive computing devices |
US6411936B1 (en) * | 1999-02-05 | 2002-06-25 | Nval Solutions, Inc. | Enterprise value enhancement system and method |
US6272485B1 (en) * | 1999-02-18 | 2001-08-07 | Creative Internet Applications, Inc. | Transferring selected formatted documents over a computer network using interface script |
US6418200B1 (en) * | 1999-02-26 | 2002-07-09 | Mitel, Inc. | Automatic synchronization of address directories for unified messaging |
US6563912B1 (en) * | 1999-03-02 | 2003-05-13 | Toshiba America Information Systems, Inc. | System and method for providing integrated messaging |
US6262598B1 (en) * | 1999-03-05 | 2001-07-17 | Sharp Kabushiki Kaisha | Voltage level shifter |
US6369840B1 (en) * | 1999-03-10 | 2002-04-09 | America Online, Inc. | Multi-layered online calendaring and purchasing |
US6173310B1 (en) * | 1999-03-23 | 2001-01-09 | Microstrategy, Inc. | System and method for automatic transmission of on-line analytical processing system report output |
US6574599B1 (en) * | 1999-03-31 | 2003-06-03 | Microsoft Corporation | Voice-recognition-based methods for establishing outbound communication through a unified messaging system including intelligent calendar interface |
US6535872B1 (en) * | 1999-04-08 | 2003-03-18 | International Business Machines Corporation | Method and apparatus for dynamically representing aggregated and segmented data views using view element sets |
US6446059B1 (en) * | 1999-06-22 | 2002-09-03 | Microsoft Corporation | Record for a multidimensional database with flexible paths |
US6449619B1 (en) * | 1999-06-23 | 2002-09-10 | Datamirror Corporation | Method and apparatus for pipelining the transformation of information between heterogeneous sets of data sources |
US6549937B1 (en) * | 1999-07-21 | 2003-04-15 | Microsoft Corporation | System and method for multi-protocol communication in a computer network |
US6385604B1 (en) * | 1999-08-04 | 2002-05-07 | Hyperroll, Israel Limited | Relational database management system having integrated non-relational multi-dimensional data store of aggregated data elements |
US6408292B1 (en) * | 1999-08-04 | 2002-06-18 | Hyperroll, Israel, Ltd. | Method of and system for managing multi-dimensional databases using modular-arithmetic based address data mapping processes on integer-encoded business dimensions |
US6404884B1 (en) * | 1999-10-08 | 2002-06-11 | Grape Technology Group, Inc. | Personalized assistance system and method |
US6430624B1 (en) * | 1999-10-21 | 2002-08-06 | Air2Web, Inc. | Intelligent harvesting and navigation system and method |
US20020056081A1 (en) * | 1999-12-02 | 2002-05-09 | Qualcomm Incorporated | Apparatus and method for decoding digital image and audio signals |
US6564264B1 (en) * | 1999-12-08 | 2003-05-13 | At&T Corp. | System, apparatus and method for automatic address updating of outgoing and incoming user messages in a communications network |
US6446062B1 (en) * | 1999-12-23 | 2002-09-03 | Bull Hn Information Systems Inc. | Method and apparatus for improving the performance of a generated code cache search operation through the use of static key values |
US6581062B1 (en) * | 2000-03-02 | 2003-06-17 | Nimble Technology, Inc. | Method and apparatus for storing semi-structured data in a structured manner |
US6424426B1 (en) * | 2000-03-28 | 2002-07-23 | Mongonet | Fax-to-email and email-to-fax communication system and method |
US6336137B1 (en) * | 2000-03-31 | 2002-01-01 | Siebel Systems, Inc. | Web client-server system and method for incompatible page markup and presentation languages |
US20020112237A1 (en) * | 2000-04-10 | 2002-08-15 | Kelts Brett R. | System and method for providing an interactive display interface for information objects |
US20020059267A1 (en) * | 2000-04-17 | 2002-05-16 | Arun Shah | Analytical server including metrics engine |
US20020035565A1 (en) * | 2000-04-27 | 2002-03-21 | Arun Shah | Graphical user interface for relational database |
US6601062B1 (en) * | 2000-06-27 | 2003-07-29 | Ncr Corporation | Active caching for multi-dimensional data sets in relational database management system |
US6629102B1 (en) * | 2000-07-28 | 2003-09-30 | International Business Machines Corporation | Efficiently updating a key table during outline restructure of a multi-dimensional database |
US6736870B2 (en) * | 2000-09-29 | 2004-05-18 | Thomas Josef Heimbach Gesellschaft Mit Beschrankter Haftung | Filter device |
US20020077787A1 (en) * | 2000-12-18 | 2002-06-20 | Theodore Rappaport | Textual and graphical demarcation of location, and interpretation of measurements |
US6721728B2 (en) * | 2001-03-02 | 2004-04-13 | The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration | System, method and apparatus for discovering phrases in a database |
Cited By (53)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080052311A1 (en) * | 2003-01-13 | 2008-02-28 | Vasudev Rangadass | Master Data Management System for Centrally Managing Core Reference Data Associated with an Enterprise |
US20080052316A1 (en) * | 2003-01-13 | 2008-02-28 | Vasudev Rangadass | Master Data Management System for Centrally Managing Core Reference Data Associated with an Enterprise |
US8392363B2 (en) * | 2003-01-13 | 2013-03-05 | Jda Software Group, Inc. | Master data management system for centrally managing core reference data associated with an enterprise |
US8204922B2 (en) * | 2003-01-13 | 2012-06-19 | Jda Software Group, Inc. | Master data management system for centrally managing core reference data associated with an enterprise |
US9025761B2 (en) | 2003-09-26 | 2015-05-05 | Avaya Inc. | Method and apparatus for assessing the status of work waiting for service |
US8891747B2 (en) | 2003-09-26 | 2014-11-18 | Avaya Inc. | Method and apparatus for assessing the status of work waiting for service |
US8751274B2 (en) | 2003-09-26 | 2014-06-10 | Avaya Inc. | Method and apparatus for assessing the status of work waiting for service |
US8094804B2 (en) * | 2003-09-26 | 2012-01-10 | Avaya Inc. | Method and apparatus for assessing the status of work waiting for service |
US7627554B2 (en) * | 2004-03-26 | 2009-12-01 | Microsoft Corporation | Uniform financial reporting system interface utilizing staging tables having a standardized structure |
US20050216497A1 (en) * | 2004-03-26 | 2005-09-29 | Microsoft Corporation | Uniform financial reporting system interface utilizing staging tables having a standardized structure |
US8731177B1 (en) | 2004-03-31 | 2014-05-20 | Avaya Inc. | Data model of participation in multi-channel and multi-party contacts |
US7953859B1 (en) | 2004-03-31 | 2011-05-31 | Avaya Inc. | Data model of participation in multi-channel and multi-party contacts |
US8000989B1 (en) | 2004-03-31 | 2011-08-16 | Avaya Inc. | Using true value in routing work items to resources |
US7734032B1 (en) | 2004-03-31 | 2010-06-08 | Avaya Inc. | Contact center and method for tracking and acting on one and done customer contacts |
US7711104B1 (en) | 2004-03-31 | 2010-05-04 | Avaya Inc. | Multi-tasking tracking agent |
US7293026B1 (en) * | 2004-04-30 | 2007-11-06 | Ncr Corp. | Integrating a data warehouse and a database |
US8738412B2 (en) | 2004-07-13 | 2014-05-27 | Avaya Inc. | Method and apparatus for supporting individualized selection rules for resource allocation |
US7949121B1 (en) | 2004-09-27 | 2011-05-24 | Avaya Inc. | Method and apparatus for the simultaneous delivery of multiple contacts to an agent |
US8234141B1 (en) | 2004-09-27 | 2012-07-31 | Avaya Inc. | Dynamic work assignment strategies based on multiple aspects of agent proficiency |
US20060112130A1 (en) * | 2004-11-24 | 2006-05-25 | Linda Lowson | System and method for resource management |
US7809127B2 (en) | 2005-05-26 | 2010-10-05 | Avaya Inc. | Method for discovering problem agent behaviors |
US7779042B1 (en) | 2005-08-08 | 2010-08-17 | Avaya Inc. | Deferred control of surrogate key generation in a distributed processing architecture |
US8578396B2 (en) | 2005-08-08 | 2013-11-05 | Avaya Inc. | Deferred control of surrogate key generation in a distributed processing architecture |
US7822587B1 (en) | 2005-10-03 | 2010-10-26 | Avaya Inc. | Hybrid database architecture for both maintaining and relaxing type 2 data entity behavior |
US7752230B2 (en) * | 2005-10-06 | 2010-07-06 | Avaya Inc. | Data extensibility using external database tables |
US7787609B1 (en) | 2005-10-06 | 2010-08-31 | Avaya Inc. | Prioritized service delivery based on presence and availability of interruptible enterprise resources with skills |
US7936867B1 (en) | 2006-08-15 | 2011-05-03 | Avaya Inc. | Multi-service request within a contact center |
US8391463B1 (en) | 2006-09-01 | 2013-03-05 | Avaya Inc. | Method and apparatus for identifying related contacts |
US8938063B1 (en) | 2006-09-07 | 2015-01-20 | Avaya Inc. | Contact center service monitoring and correcting |
US8811597B1 (en) | 2006-09-07 | 2014-08-19 | Avaya Inc. | Contact center performance prediction |
US20080162546A1 (en) * | 2006-12-29 | 2008-07-03 | Nadim Razvi | Monitoring Connection Between Computer System Layers |
US7653661B2 (en) * | 2006-12-29 | 2010-01-26 | Sap Ag | Monitoring connection between computer system layers |
US20090012971A1 (en) * | 2007-01-26 | 2009-01-08 | Herbert Dennis Hunt | Similarity matching of products based on multiple classification schemes |
US8489532B2 (en) | 2007-01-26 | 2013-07-16 | Information Resources, Inc. | Similarity matching of a competitor's products |
US9466063B2 (en) | 2007-01-26 | 2016-10-11 | Information Resources, Inc. | Cluster processing of an aggregated dataset |
US9262503B2 (en) | 2007-01-26 | 2016-02-16 | Information Resources, Inc. | Similarity matching of products based on multiple classification schemes |
US20080294372A1 (en) * | 2007-01-26 | 2008-11-27 | Herbert Dennis Hunt | Projection facility within an analytic platform |
US20080288522A1 (en) * | 2007-01-26 | 2008-11-20 | Herbert Dennis Hunt | Creating and storing a data field alteration datum using an analytic platform |
US20080294583A1 (en) * | 2007-01-26 | 2008-11-27 | Herbert Dennis Hunt | Similarity matching of a competitor's products |
US8160984B2 (en) | 2007-01-26 | 2012-04-17 | Symphonyiri Group, Inc. | Similarity matching of a competitor's products |
US20080313225A1 (en) * | 2007-06-13 | 2008-12-18 | Spicer Peter F | Methods and Systems for Developing a Data Repository for Heterogeneous MLS Systems |
US8838592B2 (en) * | 2007-06-13 | 2014-09-16 | Mlslistings Inc. | Methods and systems for developing a data repository for heterogeneous MLS systems |
US8504534B1 (en) | 2007-09-26 | 2013-08-06 | Avaya Inc. | Database structures and administration techniques for generalized localization of database items |
US8856182B2 (en) | 2008-01-25 | 2014-10-07 | Avaya Inc. | Report database dependency tracing through business intelligence metadata |
US20090193050A1 (en) * | 2008-01-25 | 2009-07-30 | Avaya Inc. | Report database dependency tracing through business intelligence metadata |
US8260822B1 (en) | 2008-08-12 | 2012-09-04 | United Services Automobile Association (Usaa) | Systems and methods for storing and querying slowly changing dimensions |
US8565386B2 (en) | 2009-09-29 | 2013-10-22 | Avaya Inc. | Automatic configuration of soft phones that are usable in conjunction with special-purpose endpoints |
US9516069B2 (en) | 2009-11-17 | 2016-12-06 | Avaya Inc. | Packet headers as a trigger for automatic activation of special-purpose softphone applications |
US8661432B2 (en) * | 2010-10-05 | 2014-02-25 | Sap Ag | Method, computer program product and system for installing applications and prerequisites components |
US20120084770A1 (en) * | 2010-10-05 | 2012-04-05 | Sap Ag | Installing Analytical Content |
WO2016132253A1 (en) * | 2015-02-18 | 2016-08-25 | Persistent Systems Limited | Integrated intermediary computing device for data analytic enhancement |
US20160292186A1 (en) * | 2015-03-30 | 2016-10-06 | International Business Machines Corporation | Dynamically maintaining data structures driven by heterogeneous clients in a distributed data collection system |
US10007682B2 (en) * | 2015-03-30 | 2018-06-26 | International Business Machines Corporation | Dynamically maintaining data structures driven by heterogeneous clients in a distributed data collection system |
Also Published As
Publication number | Publication date |
---|---|
US7117215B1 (en) | 2006-10-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7117215B1 (en) | Method and apparatus for transporting data for data warehousing applications that incorporates analytic data interface | |
US6161103A (en) | Method and apparatus for creating aggregates for use in a datamart | |
US6212524B1 (en) | Method and apparatus for creating and populating a datamart | |
US8346811B2 (en) | System and method for analyzing and reporting extensible data from multiple sources in multiple formats | |
US6189004B1 (en) | Method and apparatus for creating a datamart and for creating a query structure for the datamart | |
US6687693B2 (en) | Architecture for distributed relational data mining systems | |
Marco | Building and managing the meta data repository | |
US6026392A (en) | Data retrieval method and apparatus with multiple source capability | |
Datta et al. | The cube data model: a conceptual model and algebra for on-line analytical processing in data warehouses | |
US6339775B1 (en) | Apparatus and method for performing data transformations in data warehousing | |
US6625617B2 (en) | Modularized data retrieval method and apparatus with multiple source capability | |
US7739224B1 (en) | Method and system for creating a well-formed database using semantic definitions | |
US6263341B1 (en) | Information repository system and method including data objects and a relationship object | |
US20050262087A1 (en) | Apparatus and method for maintaining row set security through a metadata interface | |
US20020038306A1 (en) | Method of managing slowly changing dimensions | |
US20120005153A1 (en) | Creation of a data store | |
US20050065952A1 (en) | Extensible framework supporting deposit of heterogenous data sources into a target data repository | |
US20110320399A1 (en) | Etl builder | |
KR20050061597A (en) | System and method for generating reports for a versioned database | |
KR100538547B1 (en) | Data retrieval method and apparatus with multiple source capability | |
US7461076B1 (en) | Method and apparatus for creating a well-formed database system using a computer | |
CA2414230C (en) | Computer method and device for transporting data | |
US20080313153A1 (en) | Apparatus and method for abstracting data processing logic in a report | |
US20070282804A1 (en) | Apparatus and method for extracting database information from a report | |
US20030135827A1 (en) | System, method and apparatus for improved business intelligence |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INFORMATICA CORPORATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KANCHWALLA, FIROZ;LYLE, DAVID;BAIS, SUJIT C.;AND OTHERS;REEL/FRAME:011893/0761;SIGNING DATES FROM 20010522 TO 20010524 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
CC | Certificate of correction | ||
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
AS | Assignment |
Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH CAROLINA Free format text: SECURITY AGREEMENT;ASSIGNOR:INFORMATICA CORPORATION;REEL/FRAME:036294/0701 Effective date: 20150806 Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH Free format text: SECURITY AGREEMENT;ASSIGNOR:INFORMATICA CORPORATION;REEL/FRAME:036294/0701 Effective date: 20150806 |
|
AS | Assignment |
Owner name: INFORMATICA LLC, CALIFORNIA Free format text: CHANGE OF NAME;ASSIGNOR:INFORMATICA CORPORATION;REEL/FRAME:036453/0406 Effective date: 20150806 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553) Year of fee payment: 12 |
|
AS | Assignment |
Owner name: NOMURA CORPORATE FUNDING AMERICAS, LLC, NEW YORK Free format text: NOTICE OF SUCCESSION OF AGENCY;ASSIGNOR:BANK OF AMERICA, N.A.;REEL/FRAME:052018/0070 Effective date: 20200225 |
|
AS | Assignment |
Owner name: NOMURA CORPORATE FUNDING AMERICAS, LLC, NEW YORK Free format text: SECURITY INTEREST;ASSIGNOR:INFORMATICA LLC;REEL/FRAME:052022/0906 Effective date: 20200225 |
|
AS | Assignment |
Owner name: JPMORGAN CHASE BANK, N.A., NEW YORK Free format text: SECURITY INTEREST;ASSIGNOR:INFORMATICA LLC;REEL/FRAME:057973/0568 Effective date: 20211029 Owner name: INFORMATICA LLC, CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:NOMURA CORPORATE FUNDING AMERICAS, LLC;REEL/FRAME:057973/0507 Effective date: 20211029 Owner name: INFORMATICA LLC, CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:NOMURA CORPORATE FUNDING AMERICAS, LLC;REEL/FRAME:057973/0496 Effective date: 20211029 |