IP Library Granted Patent US 12,579,114
Granted Patent B2
US 12,579,114 · App. 18/806,247 · Granted Mar 17, 2026

Managing relational databases

Inventors: Jeffrey Allen Erickson (Farmersville, TX); Marjorie Ann Bue (Clear Lake, MN); Richard Forrest Herwig, Jr. (Burnsville, MN); Michael Shaun Ogilvie (Little Canada, MN); George Reynard Davis, Jr. (Charlotte, NC); Denise May Broderick (Zimmerman, MN)
Assignee: Wells Fargo Bank, N.A.
G06F16/214G06F16/212G06F16/2282G06F16/2379
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,579,114
App. No.
18/806,247
Granted
Mar 17, 2026
Kind
B2
Abstract

A relational database for migrating data in a workflow between databases in different environments. Graphical user interfaces are generated through which database management scripts are automatically generated for migrating data between environments. Generally, the database management scripts are compatible with database attributes. The database management scripts are executed to update data tables stored on the databases.

Claims (71)

1 . A computer-implemented method for a relational database management system, comprising:

generating a graphical user interface, the graphical user interface including a first migration button and a second migration button, wherein the graphical user interface is configured such that:

(i) a first selection of the first migration button generates a first Structured Query Language (SQL) computer-executable database management script configured to modify a data entry of an initial control table to adapt the data entry to a first database metadata attribute associated with a first control table of a first database; and

(ii) a second selection of the second migration button generates a second SQL computer-executable database management script that is configured to modify the data entry of the initial control table to adapt the data entry to a second database metadata attribute associated with a second control table of a second database; and

migrating the data entry to one of the first control table of the first database and the second control table of the second database based on the first selection or the second selection,

wherein the first SQL computer-executable database management script is different from the second SQL computer-executable database management script;

wherein the first database is different from the second database; and

wherein the first database metadata attribute is different from the second database metadata attribute.

2 . The computer-implemented method of claim 1 ,

wherein selection of the first migration button causes the data entry to be modified by updating the data entry to be compatible with first metadata of the first database; and

wherein selection of the second migration button causes the data entry to be modified by updating the data entry to be compatible with second metadata of the second database.

3 . The computer-implemented method of claim 2 ,

wherein the first metadata includes first schema of the first control table; and

wherein the second metadata includes second schema of the second control table.

4 . The computer-implemented method of claim 3 , wherein each of the first metadata and the second metadata includes one or more of:

a number of table rows;

a type of table row; and

a data type of a table field.

5 . The computer-implemented method of claim 3 , wherein each of the first metadata and the second metadata includes a data type of a table field, the data type including one of:

a character only data type;

a numerical only data type; and

an alphanumeric data type.

6 . The computer-implemented method of claim 3 , wherein each of the first metadata and the second metadata includes a data type of a table field, the data type including a number of decimal places data type.

7 . The computer-implemented method of claim 1 ,

wherein execution of the first SQL computer-executable database management script generates a first indicator that an update of first data fields of a first table succeeded or failed; and

wherein execution of the second SQL computer-executable database management script generates a second indicator that an update of second data fields of a second table succeeded or failed.

8 . The computer-implemented method of claim 1 , wherein the first migration button and the second migration button are selectable from a dropdown menu.

9 . The computer-implemented method of claim 1 ,

wherein the first SQL computer-executable database management script is generated after:

the first migration button is selected; and

a third button is selected to commit selection of the first migration button; and

wherein the second SQL computer-executable database management script is generated after:

the second migration button is selected; and

the third button is selected to commit selection of the second migration button.

10 . A relational database management system, comprising:

a database associated with a database environment, the database environment having database attributes;

at least one processor; and

a non-transitory computer-readable medium storing instructions that when executed by the at least one processor cause the at least one processor to:

generate a graphical user interface, the graphical user interface including a first migration button and a second migration button

generate, based on a first selection of the first migration button, a first Structured Query Language (SQL) computer-executable database management script configured to modify a data entry of an initial control table to adapt the data entry to a first database metadata attribute associated with a first control table of a first database; and

generate, based on a second selection of the second migration button, a second SQL computer-executable database management script that is configured to modify the data entry of the initial control table to adapt the data entry to a second database metadata attribute associated with a second control table of a second database; and

migrate the data entry to one of the first control table of the first database and the second control table of the second database based on the first selection or the second selection,

wherein the first SQL computer-executable database management script is different from the second SQL computer-executable database management script;

wherein the first database is different from the second database; and

wherein the first database metadata attribute is different from the second database metadata attribute.

11 . The relational database management system of claim 10 , wherein the instructions, when executed by the at least one processor, cause the at least one processor to:

update, based on the selection of the first migration button, the data entry to be compatible with first metadata of the first database; and

update, based on the selection of the second migration button, the data entry to be compatible with second metadata of the second database.

12 . The relational database management system of claim 11 ,

wherein the first metadata includes first schema of the first control table; and

wherein the second metadata includes second schema of the second control table.

13 . The relational database management system of claim 12 , wherein each of the first metadata and the second metadata includes one or more of:

a number of table rows;

a type of table row; and

a data type of a table field.

14 . The relational database management system of claim 12 , wherein each of the first metadata and the second metadata includes a data type of a table field, the data type including one of:

a character only data type;

a numerical only data type; and

an alphanumeric data type.

15 . The relational database management system of claim 12 , wherein each of the first metadata and the second metadata includes a data type of a table field, the data type including a number of decimal places data type.

16 . The relational database management system of claim 10 , wherein the instructions, when executed by the at least one processor, cause the at least one processor to:

execute the first SQL computer-executable database management script and, based thereon, generate a first indicator that an update of first data fields of a first table succeeded or failed; and

execute the second SQL computer-executable database management script and, based thereon, generate a second indicator that an update of second data fields of a second table succeeded or failed.

17 . The relational database management system of claim 10 , wherein the graphical user interface includes a dropdown menu that includes the first migration button and the second migration button.

18 . The relational database management system of claim 10 ,

wherein the first SQL computer-executable database management script is generated after:

the first migration button is selected; and

a third button is selected to commit selection of the first migration button; and

wherein the second SQL computer-executable database management script is generated after:

the second migration button is selected; and

the third button is selected to commit selection of the second migration button.

Assignments (2)
STATEMENT OF CHANGE OF ADDRESS OF ASSIGNEE Recorded Jun 17, 2025
From: WELLS FARGO BANK, N.A.
To: WELLS FARGO BANK, N.A.
Reel/Frame 071649/0870 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 16, 2024
From: ERICKSON, JEFFREY ALLEN; BUE, MARJORIE ANN; HERWIG, RICHARD FORREST, JR.; OGILVIE, MICHAEL SHAUN; DAVIS, GEORGE REYNARD, JR.; BRODERICK, DENISE MAY
To: WELLS FARGO BANK, N.A.
Reel/Frame 068307/0833 →
Continuity (3)
Continuation 18330684 · Jun 7, 2023
Continuation 16901533 · Jun 15, 2020
Related Publication 20240403275A1 · Dec 5, 2024
References Cited (32)
US 7269703B2 · Watanabe · 2007 [cited by examiner]
US 8010909B1 · Hanson · 2011 [cited by examiner]
US 8549248B2 · Liu et al. · 2013 [cited by applicant]
US 9280569B2 · Do et al. · 2016 [cited by applicant]
US 9430505B2 · Rajan et al. · 2016 [cited by applicant]
US 9519663B2 · Engelko et al. · 2016 [cited by applicant]
US 9747311B2 · Buehne et al. · 2017 [cited by applicant]
US 9779126B2 · Tu et al. · 2017 [cited by applicant]
US 9977798B2 · Bester et al. · 2018 [cited by applicant]
US 9996562B2 · Higginson et al. · 2018 [cited by applicant]
US 10268633B2 · Mohanty et al. · 2019 [cited by applicant]
US 10346374B1 · Johnson et al. · 2019 [cited by applicant]
US 20050243604A1 · Harken et al. · 2005 [cited by applicant]
US 20060235899A1 · Tucker · 2006 [cited by applicant]
US 20160179850A1 · Martin et al. · 2016 [cited by applicant]
US 20180107466A1 · Rihani et al. · 2018 [cited by applicant]
US 20190108223A1 · Fabijancic et al. · 2019 [cited by applicant]
Bernstein et al., Model management 2.0: manipulating richer mappings, Proceedings of the 2007 ACM SIGMOD international conference of Management of data, pp. 1-12, Jun. 11, 2007. [cited by applicant]
Bordbar et al., Integrated model-based software development, data access, and data migration, International Conference on Model Driven Engineering Languages and Systems, pp. 382-396, Oct. 2, 2005. [cited by applicant]
Cusick et al., Applying Operational Profiles to Demonstrate Production Readiness Of an Oracle to SQL Server Database Port using Web Services, Jul. 25, 2011. [cited by applicant]
Chanchary et al., Data migration: Connecting databases in the cloud, The 3rd International Conference on Communications and Information Technology (ICCIT) 2012. [cited by applicant]
Ferreto et al., “Server Consolidation with Migration Control for Virtualized Data Centers,” Future Generation Computer Systems 27 ( 2011), pp. 1027-1034, ScienceDirect. (Year: 2011). [cited by applicant]
Islam et al., Data migration: Connecting databases in the cloud, The 3rd International Conference on Communications and Information Technology (ICCIT) 2012. [cited by applicant]
Jigyasu et al., SQL to XQuery translation in the aqualogic data services platform, 22nd International Conference on Data Engineering (ICDE'06), pp. 97-97, Apr. 3, 2006. [cited by applicant]
Kasonde et al., A Seamless Network Database Migration, Tool for Institutions in Zambia, International Journal of Advanced Computer Science and Applications 9, No. 1: 191-199, Jan. 1, 2018. [cited by applicant]
Lau et al., Migrating e-commerce database applications to an enterprise java environment, Proceedings of the 2001 conference of the Centre for Advanced Studies on Collaborative research, p. 9, Nov. 5, 2001. [cited by applicant]
Munir et al., Database independent migration of objects into an object-relational database, The 2nd International Workshop on Autonomous Decentralized System, 2002., pp. 132-139, Nov. 7, 2002. [cited by applicant]
Osman et al., “The Design and Implementation of Zap: A System for Migrating Computing Environments,” USENIX Association 5th Symposium on Operating Systems Design and Implementation, pp. 361-376. (Year: 2002). [cited by applicant]
Rahm et al. A survey of approaches to automatic schema matching, VLDB Journal 10, No. 4: 334-350, Dec. 1, 2001. [cited by applicant]
Ramzan et al., NoSQL based Secure Environments, IEEE Access, May 15, 2019. [cited by applicant]
Ramzan et al., “Intelligence Data engineering for Migration to NoSQL Based Security environments,” 2019, pp. 69042-69057. [cited by applicant]
Thakar et al., “Migrating a (Large) Science Database to the Cloud,” HPDC'10, ACM, pp. 430-435, Jun. 20-25, 2010. (Year: 2010). [cited by applicant]