Unified database transition tool
Disclosed are a system and method for transitioning a database from one computer environment to another according to a standard workflow. An individual issues a command relating to transition to the system, and a transition management processor selects an associated sequence of technical transition processes according to a dynamic, best practices workflow. Each such process is performed by a corresponding module in the system, which is first configured by the processor according to which environment the command pertains. Some of the modules may be built-in, while some of the modules may be provided by third parties, including the database vendor. After each module performs its respective process, it generates a report, and when all modules have completed the processor transmits to the individual a response based on the produced reports, e.g. as a webpage.
1. A method of deploying a pre-production database into a production environment, the method comprising:
in response to receiving commands from a pre-production user and a production user, by a transition management processor comprising hardware, the transition management processor:
retrieving, from a data storage repository according to a best practices workflow, a sequence of processes that implement each received command;
for each process in the retrieved sequence, configuring a database analysis module according to whether the command pertains to the pre-production environment or the production environment, then executing the process using the database analysis module to produce a report; and
transmitting, to the respective commanding user, a response based on the produced reports;
wherein one of the commands received from the production user in response to the produced reports causes the pre-production database to be used by applications executing in the production environment during a stabilization period in which the pre-production database is maintained by the pre-production user; and
wherein after the transition management processor determines that the stabilization period has elapsed successfully, the database is maintained by the production user.
2. The method according to claim 1 , further comprising the transition management processor storing the produced reports in the data storage repository.
3. The method according to claim 1 , wherein a first sequence of the processes in the retrieved sequence comprises automatically, in the pre-production environment: predicting common transition errors when the database is used by applications executing in the production environment, auditing compliance of data in the database in accordance with the production environment, and validating a maintenance plan.
4. The method according to claim 3 , wherein the common transition errors include data connection errors, or insufficient disk space errors, or invalid database indexes, or database users having improper data access permissions, or data lookup performance errors, or unused data errors, or improper database software patching errors, or any combination thereof.
5. The method according to claim 3 , wherein a second sequence of the processes comprises repeatedly requesting manual review by the production user of the reports of the predicting, auditing and validating processes, until the production user either approves or rejects each such process.
6. The method according to claim 5 , wherein repeatedly requesting comprises transmitting one or more emails to the production user, to a manager of the production user, or both.
7. The method according to claim 6 , wherein a third sequence of the processes comprises, after the production user approves the predicting, auditing, and validating processes, transmitting a stabilization period beginning email to the pre-production user.
8. The method according to claim 7 , wherein a fourth sequence of the database analysis processes comprises, waiting a fixed duration after transmitting the stabilization period beginning email, then transmitting a stabilization period ending email to the pre-production user and to the production user.
9. The method according to claim 3 , wherein predicting the common transition errors is performed by a machine learning module.
10. The method according to claim 9 , wherein the machine learning module operates by determining information about the database and an operating system in the pre-production environment using which the database is executing.
11. The method according to claim 10 , wherein the machine learning module further operates by performing an automated analysis of the operating system to compute operating system parameters.
12. The method according to claim 11 , wherein the machine learning module further operates by performing an automated analysis of the database to compute database parameters.
13. The method according to claim 12 , wherein the machine learning module further operates by classifying the operating system parameters and the database parameters according to a model for predicting the common transition errors.
14. The method according to claim 13 , wherein the machine learning module further operates by training the model according to the classification.
15. The method according to claim 13 , wherein the machine learning module further operates by generating reports, based on the classification, of a transition failure prediction, of potential problems caused by the common issues, and of the pre-production environment.
16. The method according to claim 15 , wherein the machine learning module further operates by transmitting the generated reports to the pre-production user.
17. A system for deploying a pre-production database into a production environment, the system comprising:
a plurality of modules, each module for performing a respective process;
a data storage repository for storing associations between each of a plurality of commands and a corresponding plurality of configurable sequences of the processes that implement the command; and
a transition management processor comprising hardware for, in response to receiving commands from a pre-production user and a production user:
retrieving, from the data storage repository according to a best practices workflow, the sequence of processes that implement the received command;
for each process in the retrieved sequence, configuring the respective module in the plurality of modules according to whether the command pertains to the pre-production environment or the production environment, then executing the process using the respective module to produce a report; and
transmitting, to the respective user, a response based on the produced reports;
wherein one of the commands received from the production user in response to the produced reports causes the pre-production database to be used by applications executing in the production environment during a stabilization period in which the pre-production database is maintained by the pre-production user; and
wherein after the transition management processor determines that the stabilization period has elapsed successfully, the database is maintained by the production user.
18. The system according to claim 17 , wherein the data storage repository comprises a database.
19. The system according to claim 17 , wherein the plurality of modules includes a module that predicts common transition failures according to a machine learning model.