Asha U Patki

US Patent:

20130246376, Sep 19, 2013

Filed:

Mar 16, 2012

Appl. No.:

13/422910

Inventors:

Rajan Padmanabhan - Chennai, IN
Asha Uday Patki - Phoenix AZ, US
Girish Shantharama - Mangalore, IN

Assignee:

INFOSYS LIMITED - Bangalore

International Classification:

G06F 17/30

US Classification:

707694, 707E17005

Abstract:

This technology defines one or more of initial validation rules, one or more source to target mapping instructions, one or more data filtering rules, one or more data validation rules, one or more data transformation rules, and one or more file definition rules. The initial validations are performed on one or more source files based on the initial validation rules. The initially validated source files are mapped into a staging database based on the source to target mapping instructions. The data filtering rules are applied to the mapped source files in the staging database. Validation and transformation are performed on each of the successfully filtered source files based on the data validation rules and the data transformation rules. The validated and transformed source files are loaded into a core database. One or more load ready files are generated from the loaded source files based on the target file generation filtering rules.

US Patent:

20120265726, Oct 18, 2012

Filed:

Apr 18, 2011

Appl. No.:

13/088556

Inventors:

Rajan Padmanabhan - Phoenix AZ, US
Asha Uday Patki - Phoenix AZ, US

Assignee:

Infosys Limited - Bangalore

International Classification:

G06F 17/30

US Classification:

707602, 707E17005

Abstract:

Systems, apparatus, computer-readable storage media, and methods are disclosed for allowing analysis, migration, and validation of data from a source environment (such as an RDBMS system) to a target environment (such as a data warehouse (DW) appliance). In one example, a method comprises analyzing a source database, a source ETL environment, a target database, and a target ETL environment to produce configuration data, the configuration data being used for generating a mapping of the source database to a target database in the target database environment, a mapping of the source DDL code to target DDL code in the target database environment, and a mapping of source ETL code to target ETL code for the target database environment, and migrating at least one table from the source database, at least a portion of the source DDL code, and at least a portion of the source ETL code to the target database environment, where the migrating is based at least in part on the mapping generated using the configuration data.