NOVEL DATABASE SCHEMA CHANGE, RECORDING AND VERSION CONTROL METHOD AND PLATFORM

Abstract

This application relates to systems, methods, devices, and other techniques for a novel database schema change, recording and version control.

Claims

1. A method managing schema changes, comprising: receiving a plurality of change requests from at least one requester, wherein the plurality of change requests comprises instructions for modifying database schema in at least one database within a set of databases; generating a work issue comprising the plurality of change requests; assigning a plurality of users to be reviewers of the plurality of change requests, wherein the reviewers are associated with approving privileges for changes in the set of databases, wherein the work issue is provided to the reviewers for approval of the plurality of change requests; generating a work list having a set of approved change requests, wherein the set of approved change requests comprises one or more of the plurality of change requests of the work issue that are approved by the reviewers, and wherein the worklist is provided to an automatic system for executing the one or more approved change requests from the set of approved change requests; and executing the one or more approved change requests from the set of approved change requests based on the worklist, wherein the execution of the one or more approved change requests from the set of approved change requests creates a plurality of versions of the at least one database, and wherein each of the plurality of versions is maintained within the at least one database.

2. A method managing schema changes, comprising: receiving a plurality of change requests from at least one requester, wherein the plurality of change requests comprises instructions for modifying database schema in at least one database within a set of databases; generating a work issue comprising the plurality of change requests; assigning a plurality of users to be reviewers of the plurality of change requests, wherein the reviewers are associated with approving privileges for changes in the set of database, wherein the work issue is provided to the reviewers for approval of the plurality of change requests in the first worklist , wherein an automatic check is provided to the reviewers, wherein the automatic check comprises database connection check, migration schema correctness check, syntax error check, backward compatibility check, and optimization check, wherein the at least one request and the reviewers are in a collaborative relationship; generating a work list having a set of approved change requests, wherein the set of approved change requests comprises one or more of the plurality of change requests of the work issue that are approved by the reviewers, and wherein the worklist is provided to an automatic system for executing the one or more approved change requests from the set of approved change requests; and executing the one or more approved change requests from the set of approved change requests based on the worklist, wherein the execution of the one or more approved change requests from the set of approved change requests creates a plurality of versions of the at least one database, and wherein each of the plurality of versions is maintained within the at least one database.

3. A method managing schema changes, comprising: receiving a plurality of change requests from at least one requester, wherein the plurality of change requests comprises instructions for modifying database schema in at least one database within a set of databases; generating a work issue comprising the plurality of change requests; assigning a plurality of users to be reviewers of the plurality of change requests, wherein the reviewers are associated with approving privileges for changes in the set of database, wherein the work issue is provided to the reviewers for approval of the plurality of change requests in the first worklist , wherein an automatic check is provided to the reviewers, wherein the automatic check comprises database connection check, migration schema correctness check, syntax error check, backward compatibility check, and optimization check; generating a work list having a set of approved change requests, wherein the set of approved change requests comprises one or more of the plurality of change requests of the work issue that are approved by the reviewers, and wherein the worklist is provided to an automatic system for executing the one or more approved change requests from the set of approved change requests; executing the one or more approved change requests from the set of approved change requests based on the worklist, wherein the execution of the one or more approved change requests from the set of approved change requests creates a plurality of versions of the at least one database, and wherein each of the plurality of versions is maintained within the at least one database; checking unauthorized database schema modification within the at least one database of the set of databases by a pre-determined time interval; reporting schema drift if any unauthorized database schema modification is detected ; reporting another schema drift if differences are found with a copy of the at least one database with another version control systems; reporting missing database backup if there is no database backup detected; and reporting unintended database access if there is an unauthorized access to the set of database occurs.

4. A method of managing schema changes, comprising: receiving a plurality of change requests from at least one requester in an external version control system, wherein the plurality of change requests comprises instructions for modifying database schema in at least one database, wherein the external version control stores a first copy of the at least one databases , wherein the external version control system is configured to assign a peer reviewer to review and approve the plurality of change requests, wherein a first version of modified database schema is configured to be recorded in the first copy of the at the least one database by the external version control system after approval from the peer reviewer; notifying an internal system of the approval from the peer reviewer, wherein the internal system stores a second copy of the at least one database, wherein a client system stores a third copy of the at least one database; generating a work issue within the internal system comprising the plurality of change requests; assigning a plurality of users to be reviewers of the plurality of change requests within the internal system, wherein the reviewers are associated with approving privileges for changes in the set of database, wherein the reviewers could be database developers, wherein the work issue is provided to the reviewers for approval of the plurality of change requests in the first worklist , wherein an automatic check is provided to the reviewers, wherein the automatic check comprises database connection check, migration schema correctness check, syntax error check, backward compatibility check, and optimization check; generating a work list having a set of approved change requests within the internal system, wherein the set of approved change requests comprises one or more of the plurality of change requests of the work issue that are approved by the reviewers; executing the one or more approved change requests to the from the set of approved change requests based on the worklist within the internal system and within the client system; wherein the execution of the one or more approved change requests from the set of approved change requests within the internal system creates a second version of the database schema and updates the second copy of the at least one database within the internal system, wherein the execution of the one or more approved change requests from the set of approved change requests within the client system creates a third version of the database schema and updates the second copy of the at least one database with the client system, checking unauthorized database schema modification within the at least one database by a pre-determined time interval; reporting schema drift if any unauthorized database schema modification is detected ; reporting another schema drift if differences are found among any two of the first version of modified database schema, the second version of the modified database schema and the third version of the modified database schema, when there is no authorized database schema modification; reporting missing database backup if there is no database backup detected; and reporting unintended database access if there is an unauthorized access to the set of database occurs.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0029] FIG. 1 shows an example of a method of doing a novel database schema change, recording and version control.

[0030] FIG. 2 shows another example of another method of doing a novel database schema change, recording and version control.

[0031] FIG. 3 shows a third example of a third method of doing a novel database schema change, recording and version control.

[0032] FIG. 4 shows a fourth example of a fourth method of doing a novel database schema change, recording and version control.

DETAILED DESCRIPTION OF THE INVENTION

[0033] FIG. 1 shows an example of a method of doing a novel database schema change, recording and version control.

[0034] In some embodiments, the method comprises a step 105 of receiving a plurality of change requests from at least one requester, wherein the plurality of change requests comprises instructions for modifying database schema in at least one database within a set of databases.

[0035] In some embodiments, the method comprises a step 110 of generating a work issue comprising the plurality of change requests.

[0036] In some embodiments, the method comprises a step 115 of assigning a plurality of users to be reviewers of the plurality of change requests, wherein the reviewers are associated with approving privileges for changes in the set of databases, wherein the work issue is provided to the reviewers for approval of the plurality of change requests.

[0037] In some embodiments, the method comprises a step 120 of generating a work list having a set of approved change requests, wherein the set of approved change requests comprises one or more of the plurality of change requests of the work issue that are approved by the reviewers, and wherein the worklist is provided to an automatic system for executing the one or more approved change requests from the set of approved change requests.

[0038] In some embodiments, the method comprises a step 125 of executing the one or more approved change requests from the set of approved change requests based on the worklist, wherein the execution of the one or more approved change requests from the set of approved change requests creates a plurality of versions of the at least one database, and wherein each of the plurality of versions is maintained within the at least one database.

[0039] FIG. 2 shows another example of another method of doing a novel database schema change, recording and version control.

[0040] In some embodiments, the method comprises a step 205 of receiving a plurality of change requests from at least one requester, wherein the plurality of change requests comprises instructions for modifying database schema in at least one database within a set of databases.

[0041] In some embodiments, the method comprises a step 210 of generating a work issue comprising the plurality of change requests.

[0042] In some embodiments, the method comprises a step 215 of assigning a plurality of users to be reviewers of the plurality of change requests, wherein the reviewers are associated with approving privileges for changes in the set of database, wherein the work issue is provided to the reviewers for approval of the plurality of change requests in the first worklist , wherein an automatic check is provided to the reviewers, wherein the automatic check comprises database connection check, migration schema correctness check, syntax error check, backward compatibility check, and optimization check, wherein the at least one request and the reviewers are in a collaborative relationship.

[0043] In some embodiments, the method comprises a step 220 of generating a work list having a set of approved change requests, wherein the set of approved change requests comprises one or more of the plurality of change requests of the work issue that are approved by the reviewers, and wherein the worklist is provided to an automatic system for executing the one or more approved change requests from the set of approved change requests.

[0044] In some embodiments, the method comprises a step 225 of executing the one or more approved change requests from the set of approved change requests based on the worklist, wherein the execution of the one or more approved change requests from the set of approved change requests creates a plurality of versions of the at least one database, and wherein each of the plurality of versions is maintained within the at least one database.

[0045] FIG. 3 shows a third example of a third method of doing a novel database schema change, recording and version control.

[0046] In some embodiments, the method comprises a step 305 of receiving a plurality of change requests from at least one requester, wherein the plurality of change requests comprises instructions for modifying database schema in at least one database within a set of databases;

[0047] In some embodiments, the method comprises a step 310 of generating a work issue comprising the plurality of change requests.

[0048] In some embodiments, the method comprises a step 315 of assigning a plurality of users to be reviewers of the plurality of change requests, wherein the reviewers are associated with approving privileges for changes in the set of database, wherein the work issue is provided to the reviewers for approval of the plurality of change requests in the first worklist , wherein an automatic check is provided to the reviewers, wherein the automatic check comprises database connection check, migration schema correctness check, syntax error check, backward compatibility check, and optimization check.

[0049] In some embodiments, the method comprises a step 320 of generating a work list having a set of approved change requests, wherein the set of approved change requests comprises one or more of the plurality of change requests of the work issue that are approved by the reviewers, and wherein the worklist is provided to an automatic system for executing the one or more approved change requests from the set of approved change requests.

[0050] In some embodiments, the method comprises a step 325 of executing the one or more approved change requests from the set of approved change requests based on the worklist, wherein the execution of the one or more approved change requests from the set of approved change requests creates a plurality of versions of the at least one database, and wherein each of the plurality of versions is maintained within the at least one database.

[0051] In some embodiments, the method comprises a step 330 of checking unauthorized database schema modification within the at least one database of the set of databases by a pre-determined time interval.

[0052] In some embodiments, the method comprises a step 335 of reporting schema drift if any unauthorized database schema modification is detected .

[0053] In some embodiments, the method comprises a step 340 of reporting another schema drift if differences are found with a copy of the at least one database with another version control systems.

[0054] In some embodiments, the method comprises a step 345 of reporting missing database backup if there is no database backup detected.

[0055] In some embodiments, the method comprises a step 350 of reporting unintended database access if there is an unauthorized access to the set of database occurs.

[0056] FIG. 4 shows a fourth example of a fourth method of doing a novel database schema change, recording and version control.

[0057] In some embodiments, the method comprises a step 405 of receiving a plurality of change requests from at least one requester in an external version control system, wherein the plurality of change requests comprises instructions for modifying database schema in at least one database, wherein the external version control stores a first copy of the at least one databases , wherein the external version control system is configured to assign a peer reviewer to review and approve the plurality of change requests, wherein a first version of modified database schema is configured to be recorded in the first copy of the at the least one database by the external version control system after approval from the peer reviewer.

[0058] In some embodiments, the method comprises a step 410 of notifying an internal system of the approval from the peer reviewer, wherein the internal system stores a second copy of the at least one database, wherein a client system stores a third copy of the at least one database.

[0059] In some embodiments, the method comprises a step 415 of generating a work issue within the internal system comprising the plurality of change requests.

[0060] In some embodiments, the method comprises a step 420 of assigning a plurality of users to be reviewers of the plurality of change requests within the internal system, wherein the reviewers are associated with approving privileges for changes in the set of database, wherein the reviewers could be database developers, wherein the work issue is provided to the reviewers for approval of the plurality of change requests in the first worklist, wherein an automatic check is provided to the reviewers, wherein the automatic check comprises database connection check, migration schema correctness check, syntax error check, backward compatibility check, and optimization check.

[0061] In some embodiments, the method comprises a step 425 of generating a work list having a set of approved change requests within the internal system, wherein the set of approved change requests comprises one or more of the plurality of change requests of the work issue that are approved by the reviewers.

[0062] In some embodiments, the method comprises a step 430 of executing the one or more approved change requests to the from the set of approved change requests based on the worklist within the internal system and within the client system; wherein the execution of the one or more approved change requests from the set of approved change requests within the internal system creates a second version of the database schema and updates the second copy of the at least one database within the internal system, wherein the execution of the one or more approved change requests from the set of approved change requests within the client system creates a third version of the database schema and updates the second copy of the at least one database with the client system.

[0063] In some embodiments, the method comprises a step 435 of checking unauthorized database schema modification within the at least one database by a pre-determined time interval.

[0064] In some embodiments, the method comprises a step 440 of reporting schema drift if any unauthorized database schema modification is detected.

[0065] In some embodiments, the method comprises a step 445 of reporting another schema drift if differences are found among any two of the first version of modified database schema, the second version of the modified database schema and the third version of the modified database schema, when there is no authorized database schema modification.

[0066] In some embodiments, the method comprises a step 450 of reporting missing database backup if there is no database backup detected.

[0067] In some embodiments, the method comprises a step 455 of reporting unintended database access if there is an unauthorized access to the set of database occurs.