System and method to determine database schema impact
First Claim
Patent Images
1. A method for database management, comprising:
- storing, in memory, a replication of a source database associated with a schema;
assigning, by a processor, a unique database user identification to each downstream client system accessing the source database;
receiving database query statements, each database query statement identifying a software application accessing a name of a database table and the unique database user identification assigned to each downstream client system issuing each database query statement;
storing, in the memory, a dependency matrix for the replication of the source database, the dependency matrix associating the unique database user identification assigned to each downstream client system and to the name of the database table identified in each database query statement;
monitoring the dependency matrix for an impact to the software application;
identifying, based on the monitoring, a change to the schema of the replication of the source database;
verifying the change by repeatedly comparing database data for the replication of the source database to metadata for the source database; and
responsive to the verifying of the change, informing the software application of the impact due to the change to the schema of the replication of the source database.
1 Assignment
0 Petitions
Accused Products
Abstract
Database management systems associate a user identifier with an application and monitor access by the application to a database replication. Any changes to a schema associated with the database replication or different instances of the database are identified based on the monitoring. Identified changes are verified and a usage parameter of the database or database replication is analyzed to determine usage data, which can be stored in a database usage repository. A determination regarding the expected impact of an identified change is determined from the usage data.
-
Citations
20 Claims
-
1. A method for database management, comprising:
-
storing, in memory, a replication of a source database associated with a schema; assigning, by a processor, a unique database user identification to each downstream client system accessing the source database; receiving database query statements, each database query statement identifying a software application accessing a name of a database table and the unique database user identification assigned to each downstream client system issuing each database query statement; storing, in the memory, a dependency matrix for the replication of the source database, the dependency matrix associating the unique database user identification assigned to each downstream client system and to the name of the database table identified in each database query statement; monitoring the dependency matrix for an impact to the software application; identifying, based on the monitoring, a change to the schema of the replication of the source database; verifying the change by repeatedly comparing database data for the replication of the source database to metadata for the source database; and responsive to the verifying of the change, informing the software application of the impact due to the change to the schema of the replication of the source database. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12)
-
-
13. A database management system, comprising:
-
a processor; and memory storing instructions that, when executed by the processor, cause the processor to perform operations, the operations comprising; synchronizing a database replication associated with a source database and associated with a schema; assigning a unique database user identification to each downstream client system accessing the source database; receiving database query statements, each database query statement identifying a software application accessing a name of a database table and the unique database user identification assigned to each downstream client system issuing each database query statement; storing a dependency matrix for the database replication, the dependency matrix associating the unique database user identification assigned to each downstream client system and to the name of the database table identified in each database query statement; monitoring the dependency matrix for an impact to the software application; identifying, based on the monitoring, a change to the schema of the database replication; verifying the change by repeatedly comparing database data for the database replication to metadata for the source database; and responsive to the verifying of the change, informing the software application of the impact due to the change to the schema of the database replication. - View Dependent Claims (14, 15, 16, 17)
-
-
18. A memory storing instructions that, when executed by a processor, cause the processor to perform operations, the operations comprising:
-
storing a replication of a source database associated with a schema; assigning a unique database user identification to each downstream client system accessing the source database; receiving database query statements, each database query statement identifying a software application accessing a name of a database table and the unique database user identification assigned to each downstream client system issuing each database query statement; storing a dependency matrix for the replication of the source database, the dependency matrix associating the unique database user identification assigned to each downstream client system and to the name of the database table identified in each database query statement; monitoring the dependency matrix for an impact to the software application; identifying, based on the monitoring, a change to the schema of the replication of the source database; verifying the change by repeatedly comparing database data for the replication of the source database to metadata for the source database; and responsive to the verifying of the change, informing the software application of the impact due to the change to the schema of the replication of the source database. - View Dependent Claims (19, 20)
-
Specification