# US 10,311,077 B2 · Database table conversion

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

- Number: US 10,311,077 B2
- Document ID: US10311077B2
- Status: Granted
- Kind: B2
- Application number: 14/920,362
- Filed: 2015-10-22
- Published: 2017-04-27
- Granted: 2019-06-04
- Earliest claimed: 2015-10-22
- Assignees: Sap SE
- Applicants: Sap SE
- Inventors: Juergen Specht; Volker Driesen
- Web page: https://patentgrep.com/patent/US10311077B2

## CPC

- G06F 16/258: {Data format conversion from or to a database}
- G06F 16/214: {Database migration support}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Methods, systems, and computer program products for converting a database table and implementing upgrades and/or migrations are described. A bridge schema comprising a bridge view for a table in a database of an original schema is created and a bridge application server instance is created, the bridge application server instance configured to utilize the bridge schema to access the table of the original schema. The table of the original schema is revised to conform to a specified target schema and a target application server instance configured to access the revised table is created.

## Claims

### Claim 1

A computerized method for performing an upgrade, the method comprising:
creating a bridge schema comprising a bridge view in the bridge schema for a table of an original schema, wherein a first field of the table is of a first data type in the original schema, and wherein the first field is of a second data type in a target schema;
adding to the table a revised first field having the second data type, wherein the bridge view accesses the first field and does not access the revised first field;
creating a bridge application server instance, the bridge application server instance configured to utilize the bridge schema containing the bridge view to access the table;
copying data from the first field to the revised first field, wherein the copying comprises modifying the data from the first field from the first data type to the second data type;
deleting the first field;
renaming the revised first field to a name of the first field; and
creating a target application server instance configured to access the table.

### Claim 2 (depends on 1)

The computerized method of claim 1, further comprising creating an alias for the table, the alias being the target of the bridge view in the bridge schema, the bridge view being defined to select from the alias of the table.

### Claim 3 (depends on 2)

The computerized method of claim 2, further comprising dropping the alias for the table of the original schema.

### Claim 4 (depends on 1)

The computerized method of claim 1, further comprising configuring an application running in the application server instance to access the bridge schema and the view in the bridge schema.

### Claim 5 (depends on 4)

The computerized method of claim 4, wherein only fields of the table conforming to the original schema are accessible to the application via the bridge application server instance.

### Claim 6 (depends on 4)

The computerized method of claim 4, further comprising configuring the application to execute in the target application server instance.

### Claim 7 (depends on 6)

The computerized method of claim 6, wherein fields of the table conforming to the target schema are accessible to the application executing in the target application server instance.

### Claim 8 (depends on 1)

The computerized method of claim 1, further comprising creating a target repository table that corresponds to the target schema.

### Claim 9 (depends on 8)

The computerized method of claim 8, further comprising dropping an alias for a source repository table of the original schema, the source repository table having a name, and renaming the source repository table to the name of the dropped alias for the source repository table.

### Claim 10 (depends on 9)

The computerized method of claim 9, further comprising renaming the target repository table that corresponds to the target schema to the name of the source repository table of the original schema.

### Claim 11 (depends on 1)

The computerized method of claim 1, further comprising dropping the bridge schema.

### Claim 12

An apparatus for performing an upgrade, the apparatus comprising:
one or more hardware processors;
memory to store instructions that, when executed by the one or more hardware processors perform operations comprising:
creating a bridge schema comprising a bridge view in the bridge schema for a table of the original schema, wherein a first field of the table is of a first data type in an original schema, and wherein the first field is of a second data type in a target schema;
adding to the table a revised first field having the second data type, wherein the bridge view accesses the first field and does not access the revised first field;
creating a bridge application server instance, the bridge application server instance configured to utilize the bridge schema to access the table;
copying data from the first field to the revised first field, wherein the copying comprises modifying the data from the first field from the first data type to the second data type;
deleting the first field;
renaming the revised first field to a name of the first field; and
creating a target application server instance configured to access the table.

### Claim 13 (depends on 12)

The apparatus of claim 12, further comprising instructions that, when executed by the processor cause the processor to create an alias for the table of the original schema.

### Claim 14 (depends on 13)

The apparatus of claim 13, further comprising instructions that, when executed by the processor cause the processor to drop the alias for the table of the original schema.

### Claim 15 (depends on 12)

The apparatus of claim 12, further comprising instructions that, when executed by the processor cause the processor to configure an application to access the bridge application server instance.

### Claim 16 (depends on 15)

The apparatus of claim 15, wherein only fields of the table conforming to the original schema are accessible to the application via the bridge application server instance.

### Claim 17 (depends on 15)

The apparatus of claim 15, further comprising instructions that, when executed by the processor cause the processor to configure the application to execute in the target application server instance.

### Claim 18 (depends on 17)

The apparatus of claim 17, wherein fields of the table conforming to the target schema are accessible to the application executing in the target application server instance.

### Claim 19 (depends on 12)

The apparatus of claim 12, further comprising instructions that, when executed by the processor cause the processor to create a target repository table that corresponds to the target schema, drop an alias for a source repository table of the original schema, the source repository table having a name, rename the source repository table to the name of the dropped alias for the source repository table, rename the target repository table that corresponds to the target schema to the name of the source repository table of the original schema, and drop the bridge schema.

### Claim 20

A non-transitory computer-readable medium embodying instructions that, when executed by a processor, perform operations comprising:
creating a bridge schema comprising a bridge view for a table in a database of an original schema, wherein a first field of the table is of a first data type in the original schema, and wherein the first field is of a second data type in a target schema;
adding to the table a revised first field having the second data type, wherein the bridge view accesses the first field and does not access the revised first field;
creating a bridge application server instance, the bridge application server instance configured to utilize the bridge schema to access the table;
copying data from the first field to the revised first field, wherein the copying comprises modifying the data from the first field from the first data type to the second data type;
deleting the first field;
renaming the revised first field to a name of the first field; and
creating a target application server instance configured to access the table.