# US 2021/0334251 A1 · Consolidating Multiple Databases into a Single or a Smaller Number of Databases

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0334251 A1
- Document ID: US20210334251A1
- Status: Published application
- Kind: A1
- Application number: 16/855,176
- Filed: 2020-04-22
- Published: 2021-10-28
- Earliest claimed: 2020-04-22
- Assignees: Capital One Services, LLC
- Applicants: Capital One Services, LLC
- Inventors: Dennis J. Mire; Kishore Doppalapudi
- Web page: https://patentgrep.com/patent/US20210334251A1

## CPC

- G06F 16/214: {Database migration support}
- G06F 9/44505: {Configuring for program initiating, e.g. using registry, configuration files}
- G06F 16/1734: {Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs}
- G06F 16/182: Distributed file systems
- G06F 16/211: {Schema design and management}
- G06F 16/221: {Column-oriented storage; Management thereof}
- G06F 16/2282: {Tablespace storage structures; Management thereof}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A system, method, and computer-readable medium for consolidating multiple databases into a single or a smaller number of databases is described. An improved structure of target database may be achieved by removing constraints used when creating legacy databases. According to some aspects, these and other benefits may be achieved by combining multiple source tables into a single target table with errors being identified and addressed during the creation of the instructions to generate the target table. In implementation, this may be effected by converting values from a source table and values from a target table into normalized versions of those values and then comparing the normalized values. A benefit includes verifying that the data from the source table is being properly reflected in the target table.

## Claims

### Claim 1

A method comprising:
identifying a first set of relationships between a first source table of a first source database and a target table of a target database, wherein the first set of relationships include specific columns of the first source table and an identification of a table type of the first source table;
storing the first set as first source table-specific relationships;
identifying a second set of relationships between a second source table of a second source database and the table of the target database, wherein the second set of relationships include specific columns of the second source table and an identification of a table type of the second source table;
storing the second set as second source table-specific relationships;
assigning an order in the target table in which columns from the first table are to be added;
arranging, in the assigned order, columns of the target table to be populated with content from the second table;
generating, based on the assigned order and the first source table-specific relationships, a conversion configuration file;
recursively generating, based on the assigned order and the second source table-specific relationships, additional conversion information for the conversion configuration file;
grouping data from the first database into a first batch;
grouping data from the second database into a second batch;
executing the conversion configuration file on the first batch;
formatting cells in the first batch into a text format;
formatting cells in a portion of data from the target database into the text format, wherein the portion of data from the target database corresponds to the first batch;
comparing content of text-formatted cells from the first batch and content of text-formatted cells from the portion of data from the target database;
generating an alert, based on the comparison, that the content of at least one text-formatted cell from the first batch and the content of at least one text-formatted corresponding cell from the portion of data from the target database do not match;
modifying, based on the alert, the conversion configuration file; and
executing the modified conversion configuration file, based on the batch from the first database and the batch from the second database, to populate the table of the target database.

### Claim 2 (depends on 1)

The method according to claim 1,
wherein the first source table includes fact data,
wherein the second source table includes history data, and
wherein the table of the target database includes fact data and history data.

### Claim 3 (depends on 1)

The method according to claim 1,
wherein the conversion configuration file is a first conversion configuration file,
wherein the method further comprises:
executing a second conversion configuration file related to a third table of a third source database to populate the table of the target database,
wherein the third table is an overwrite table.

### Claim 4 (depends on 1)

The method according to claim 1,
wherein the first database is a legacy database, and
wherein the target database is a cloud-based database.

### Claim 5 (depends on 1)

The method according to claim 1,
wherein the target database is a relational database.

### Claim 6 (depends on 1)

The method according to claim 1,
wherein the alert includes an identification of a difference between the content of the non-matching cells from the first batch and the portion of data from the target database.

### Claim 7 (depends on 1)

The method according to claim 1,
wherein the alert includes an identification of a difference between the content of the non-matching cells from the first batch and the portion of data from the target database and an identification of a modification to conform the content of the cells to each other.

### Claim 8

A system comprising:
a first source database comprising a first source table;
a second source database comprising a second source table;
a target database comprising a target table; and
a server comprising one or more processors and memory, wherein the memory stores instructions that, when executed by the one or more processors, cause the server to:
identifying a first set of relationships between a first source table of the first source database and the target table of the target database, wherein the first set of relationships include specific columns of the first source table and an identification of the table type of the first source table;
storing the first set as first source table-specific relationships;
identifying a second set of relationships between the second source table of the second source database and the table of the target database, wherein the second set of relationships include specific columns of the second source table and an identification of a table type of the second source table;
storing the second set as second source table-specific relationships;
assigning an order in the target table in which columns from the first table are to be added;
arranging, in the assigned order, columns of the target table to be populated with content from the second table;
generating, based on the assigned order and the first source table-specific relationships, a conversion configuration file;
recursively generating, based on the assigned order and the second source table-specific relationships, additional conversion information for the conversion configuration file;
grouping data from the first database into first batch;
executing the conversion configuration file on the first batch;
formatting cells in the first batch into a text format;
formatting cells in a portion of data from the target database into the text format, wherein the portion of data from the target database corresponds to the first batch;
comparing content of text-formatted cells from the first batch and content of text-formatted cells from the portion of data from the target database;
modifying, based on an alert that the compared content does not match, the conversion configuration file; and
executing the modified conversion configuration file, based on the batch from the first database, to populate the table of the target database.

### Claim 9 (depends on 8)

The system according to claim 8,
wherein the first source table includes fact data,
wherein the second source table includes history data, and
wherein the table of the target database includes fact data and history data.

### Claim 10 (depends on 8)

The system according to claim 8,
wherein the conversion configuration file is a first conversion configuration file,
wherein the instructions, when executed by the one or more processors, further cause the server to:
executing a second conversion configuration file corresponding to a third table of a third source database to populate the table of the target database,
wherein the third table is an overwrite table.

### Claim 11 (depends on 8)

The system according to claim 8,
wherein the first database is a legacy database, and
wherein the target database is a cloud-based database.

### Claim 12 (depends on 8)

The system according to claim 8,
wherein the target database is a relational database.

### Claim 13 (depends on 8)

The system according to claim 8,
wherein the alert includes an identification of a difference between the content of the non-matching cells from the first batch and the portion of data from the target database.

### Claim 14 (depends on 8)

The system according to claim 8,
wherein the alert includes an identification of a difference between the content of the non-matching cells from the first batch of data and the portion of data from the target database and an identification of a modification to conform the content of the cells to each other.

### Claim 15

One or more non-transitory media storing instructions that, when executed by one or more processors, cause the one or more processors to perform steps comprising:
identifying a first set of relationships between a first source table of a first source database and a target table of a target database, wherein the first set of relationships include specific columns of the first source table and an identification of a table type of the first source table;
storing the first set as first source table-specific relationships;
identifying a second set of relationships between a second source table of a second source database and the table of the target database, wherein the second set of relationships include specific columns of the second source table and an identification of a table type of the second source table;
storing the second set as second source table-specific relationships;
assigning an order in the target table in which columns from the first table are to be added;
arranging, in the assigned order, columns of the target table to be populated with content from the second table;
generating, based on the assigned order and the first source table-specific relationships, a conversion configuration file;
recursively generating, based on the assigned order and the second source table-specific relationships, additional conversion information for the conversion configuration file;
grouping data from the first database into a first batch;
grouping data from the second database into a second batch;
executing the conversion configuration file on the first batch;
formatting cells in the first batch into a text format;
formatting cells in a portion of data from the target database into the text format, wherein the portion of data from the target database corresponds to the first batch;
comparing content of text-formatted cells from the first batch of data and content of text-formatted cells from the portion of data from the target database;
generating an alert, based on the comparison, that the content of at least one text-formatted cell from the first batch and the content of at least one text-formatted corresponding cell from the portion of data from the target database do not match;
modifying, based on the alert, the conversion configuration file; and
executing the modified conversion configuration file, based on the batches from the first database and the batches from the second database, to populate the table of the target database,
wherein the alert includes an identification of a difference between the content of the non-matching cells from the first batch and the portion of data from the target database and an identification of a modification to conform the content of the cells to each other.

### Claim 16 (depends on 15)

The one or more non-transitory media according to claim 15,
wherein the first source table includes fact data,
wherein the second source table includes history data, and
wherein the table of the target database includes fact data and history data.

### Claim 17 (depends on 15)

The one or more non-transitory media according to claim 15,
wherein the conversion configuration file is a first conversion configuration file,
wherein the instructions further comprise causing the one or more processors to:
execute a second conversion configuration file related to a third table of a third source database to populate the table of the target database,
wherein the third table is an overwrite table.

### Claim 18 (depends on 15)

The one or more non-transitory media according to claim 15,
wherein the first database is a legacy database, and
wherein the target database is a cloud-based database.

### Claim 19 (depends on 15)

The computer-readable medium according to claim 15,
wherein the target database is a relational database.

### Claim 20 (depends on 1)

The one or more non-transitory media according to claim 1,
wherein the alert includes a suggestion of how to modify the configuration file.
