CN118394736A - Database replacement method, device, medium and computing equipment - Google Patents

Abstract

The application discloses a database replacement method, a device, a medium and a computing device, wherein the method comprises the following steps: based on the user requirements and the application scene of the source database, constructing a test environment; performing function verification and system verification on a pre-established target database based on the built test environment; in the process of performing function verification and system verification on the target database, adjusting a database layer and an interface layer of the target database to obtain a target replacement database; and replacing the source database with the target replacement database. The application aims to solve the technical problem of low database replacement efficiency.

Description

A database replacement method, device, medium and computing equipment

Technical Field

The present application relates to the field of database technology, and in particular to a database replacement method, apparatus, medium and computing device.

Background technique

With the continuous development of information technology, many companies have stored massive amounts of data in their databases. While these data bring convenience to the development of enterprises, they also present some challenges, such as data storage, management, and daily operation and maintenance. Considering the performance, storage space, and stability of the database, it is often necessary to replace the database, that is, to migrate the source database from the first server system to the second server system. During the database replacement process, production applications connected to the source database are usually suspended for a long time, resulting in low database replacement efficiency and a significant impact on the normal use of users.

The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art.

Summary of the invention

The main purpose of the present application is to provide a database replacement method, apparatus, medium and computing device, aiming to solve the technical problem of low database replacement efficiency.

To achieve the above-mentioned purpose, the present application provides a database replacement method, which includes: building a test environment based on user needs and application scenarios of a source database; performing functional verification and system verification on a pre-created target database based on the built test environment; in the process of performing functional verification and system verification on the target database, adjusting the database layer and interface layer of the target database to obtain a target replacement database; and replacing the source database with the target replacement database.

Optionally, based on the constructed test environment, functional verification and system verification are performed on the pre-created target database, including: migrating the source database to the database layer of the target database; verifying the functions of the database layer and business layer of the target database after the migration is completed in the constructed test environment; verifying the performance and backup data of the target database after the migration is completed in the constructed test environment.

Optionally, the functions of the database layer and the business layer of the target database after the migration are verified in the constructed test environment, including: using a preset tool to capture a first preset statement of the source database; and in the constructed test environment, verifying the compatibility of the database layer and the business layer of the target database based on the first preset statement.

Optionally, the verification of the performance and backup data of the target database after the migration is completed in the constructed test environment includes: verifying and counting the time consumed in executing the first preset statement in the constructed test environment; verifying the response speed of the target database by using a preset stress testing tool; performing security verification on user operation permissions and data packets generated based on user operations; verifying the scalability of the target database by connecting to a pre-configured device without stopping service; and verifying the backup data of the target database within a preset backup cycle.

Optionally, after replacing the source database with the target replacement database, the method further comprises: monitoring and evaluating actual operation of the replaced target replacement database.

Optionally, the monitoring and evaluation of the actual operation of the target replacement database after replacement includes: setting up database monitoring software; based on the database monitoring software, monitoring the operation of the target replacement database after replacement in real time to obtain various monitoring indicators; analyzing the various monitoring indicators at preset time intervals to generate a system operation report.

Optionally, the method for creating the target database includes: obtaining a business replacement technical point based on the database layer, database access interface layer, and business database scheduling layer of the source database base; and creating the target database based on the business replacement technical point.

In addition, to achieve the above-mentioned purpose, the present application also provides a database replacement device, which includes: a construction module, which is used to build a test environment based on user needs and application scenarios of the source database; a verification module, which is used to perform functional verification and system verification on a pre-created target database based on the constructed test environment; an adjustment module, which is used to adjust the database layer and interface layer of the target database during the process of performing functional verification and system verification on the target database to obtain a target replacement database; a replacement module, which is used to replace the source database with the target replacement database.

In addition, the present application also provides a computing device, which includes: at least one processor, a memory and an input and output unit; wherein the memory is used to store a computer program, and the processor is used to call the computer program stored in the memory to execute any of the methods described above.

In addition, the present application also provides a computer-readable storage medium, which includes instructions, and when the instructions are executed on a computer, the computer executes any one of the above methods.

The embodiments of the present application propose a database replacement method, apparatus, medium and computing device, which build a test environment according to user needs and application scenarios of a source database; perform function verification and system verification on a pre-created target database through the built test environment; perform function verification and system verification on the target database to facilitate adjustment of the database layer and interface layer of the target database to obtain a target replacement database; after the function verification, system verification and adjustment of the database layer and interface layer of the target replacement database, there will be no system incompatibility issues with the source database, and the target replacement database can replace the source database after rapid switching without long pauses for replacement, which can effectively improve the efficiency of database replacement and reduce the inconvenience caused to the normal use of users.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of a flow chart of a database replacement method provided in an embodiment of the present application;

FIG2 is a functional module diagram of a database replacement device provided by an embodiment of the present application;

FIG3 is a schematic diagram of the structure of a medium provided by an embodiment of the present application;

FIG. 4 is a schematic diagram of the structure of a computing device provided in an embodiment of the present application.

The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with embodiments and with reference to the accompanying drawings.

Detailed ways

It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application. On the contrary, these embodiments are provided to make the present disclosure more thorough and complete, and to fully convey the scope of the present disclosure to those skilled in the art.

Those skilled in the art know that the embodiments of the present application can be implemented as a system, device, equipment, method or computer program product. Therefore, the present application can be specifically implemented in the following forms, namely: complete hardware, complete software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.

With the continuous development of information technology, many companies have stored massive amounts of data in their databases. While these data bring convenience to the development of enterprises, they also bring some challenges, such as data storage, management, and daily operation and maintenance. Considering the performance, storage space, stability, and other aspects of the database, it is often necessary to replace the database, that is, migrate the source database from the first server system to the second server system. During the database replacement process, production applications connected to the source database are usually suspended for a long time, which has a significant impact on the normal use of users.

The main solution of the embodiment of the present application is: based on user needs and application scenarios of the source database, a test environment is built; based on the built test environment, a pre-created target database is functionally verified and a system is verified; in the process of functionally verifying and a system is verified on the target database, the database layer and the interface layer of the target database are adjusted to obtain a target replacement database; and the source database is replaced with the target replacement database.

The present application provides a solution, which builds a test environment according to user needs and application scenarios of a source database; performs function verification and system verification on a pre-created target database through the built test environment; facilitates adjustment of the database layer and the interface layer of the target database by performing function verification and system verification on the target database to obtain a target replacement database; after the function verification, the system verification and the adjustment of the database layer and the interface layer of the target replacement database, there will be no system incompatibility problem with the source database, and the target replacement database can replace the source database after rapid switching, without the need for long-term pauses for replacement, which can effectively improve the efficiency of database replacement and reduce the inconvenience caused to the normal use of users.

It should be noted that any number of elements in the drawings is for illustration rather than limitation, and any naming is only for distinction and does not have any limiting meaning.

The principles of the present application are explained in detail below with reference to several representative implementations of the present application.

Referring to FIG. 1 , an embodiment of the present application provides a database replacement method, the method comprising:

Step S110: Building a test environment based on user needs and application scenarios of the source database.

In the example embodiment, the application scenario of the source database is a system operation scenario using the source database, for example, a business application system using the source database is used to monitor the flight of an aircraft. User requirements can be user requirements for the effect achieved by the business application system during operation after the database replacement is implemented. For example, when the business application system using the source database is running, the source database cannot meet the system throughput. In this case, when setting up the test environment, the user's evaluation parameters for the database throughput are added. Setting up the test environment can be, for example, copying the entire business application system to a new server device and starting to provide services. The copied business application system is the test verification environment.

Step S120: Based on the constructed test environment, function verification and system verification are performed on the pre-created target database.

In an example embodiment, the target database is a database pre-designed according to user requirements to replace the source database. Functional verification is to perform functional verification on the technical points involved in the target database, which may include verifying the functions of the database layer and business layer of the target database in a test environment; system verification is to verify the response speed, security, stability, etc. of the target database in a test environment.

In a specific embodiment, a method for creating a target database includes: obtaining a business replacement technical point based on a database layer, a database access interface layer, and a business database scheduling layer of a source database base; and creating a target database based on the business replacement technical point.

In the example embodiment, for example, the source database is a MySQL database, and the target database to be created is an ACEDB database; the migration tool is used to complete the database object migration from the MySQL database to the ACEDB database; the data comparison and verification tool is used to complete the meta information and data consistency comparison between the MySQL database and the ACEDB database, and obtain the business replacement technical point; wherein, the meta information and data consistency comparison in the business replacement technical point involves the comparison of the database layer, database access interface layer, and business database scheduling layer between the ACEDB database and the MySQL database base. The database access interface layer is embedded in the program configuration file of the business system, and only the URL address string for connecting to the database needs to be replaced, and the designer modifies the configuration file parameters according to business needs; the modified configuration file parameters are obtained to create the target database.

In a specific embodiment, the above step S120 may include:

Step S1201, migrating the source database to the database layer of the target database;

Step S1202, verifying the functions of the database layer and the business layer of the target database after the migration is completed in the constructed test environment;

Step S1203: Verify the performance and backup data of the target database after the migration is completed in the constructed test environment.

In an example embodiment, the performance of the target database includes the response speed, security, and scalability of the target database; wherein the response speed of the target database is the time taken for the target database to respond to test instructions in a test environment to query, update, delete, and other operations on data in the database.

The scalability of the target database refers to the ability of the target database to flexibly adjust its scale and performance as the amount of data, number of users or business needs grow. Specifically, the scalability of the target database is reflected in the following aspects: Horizontal expansion: By adding more database instances or nodes to share the load and improve the overall processing capacity. This expansion method can effectively cope with the rapid growth of data volume and the increase in concurrent access. Vertical expansion: By upgrading hardware resources, such as using higher-performance CPUs, increasing memory and storage space, the performance of a single database instance can be improved. This method is suitable for scenarios with large data volumes and high performance requirements. Functional expansion: As the business develops, it may be necessary to add new functions or modules to the database to meet changing business needs.

It can be understood that the database layer of the source database is migrated to the database layer of the target database, that is, the database objects in the source database, such as tables, views, constraints and other database objects and data, must all be migrated to the target database without distinction. The purpose of the migration is to ensure that all source database information is completely and consistently migrated to the target database. The operation of the business application system is based on the objects and data in the database. This step is the premise and basis for realizing database migration. To a certain extent, it can ensure smooth migration during the replacement process, and the business application system does not need to make a large number of modifications to the target database, so that the production application does not need to be suspended for a long time during the database replacement process, which greatly reduces the impact on the production application.

After the migration is completed, in the established test environment, the technical points involved in the target database that has completed the database layer migration are functionally verified, as well as the performance of the target database, such as the response speed, security, stability, scalability, and ROSE backup data of the target database. During the verification process, adjustments are made to the database layer and the interface layer until all functions are implemented to ensure a smooth transition between the old and new systems during the actual replacement process.

Furthermore, the above step S1202 may include: using a preset tool to capture a first preset statement of the source database; and verifying the compatibility of the database layer and the business layer of the target database based on the first preset statement in the constructed test environment.

In an exemplary embodiment, the first preset statement may be an SQL statement, where SQL (Structured Query Language) is a standard programming language for managing relational databases. SQL can be used to perform various database operations, such as querying, inserting, updating, and deleting data.

For example, the source database is a MySQL database, and the target database is an ACEDB database. A MySQL crawler tool is used to crawl the SQL statements of the MySQL database embedded in the business application system. The crawled SQL statements are used to evaluate and verify the SQL syntax compatibility in a test environment to ensure that there will be no SQL syntax compatibility issues that cause execution errors in the business application system after replacement.

Furthermore, the above-mentioned step S1203 may include, in the constructed test environment, verifying statistics on the time consumed in executing the first preset statement; using a preset stress testing tool to verify the response speed of the target database; performing security verification on user operation permissions and data packets generated based on user operations; without stopping the service, connecting to a pre-configured device to verify the scalability of the target database; and verifying the backup data of the target database within a preset backup cycle.

In the example embodiment, the first preset statement can be an SQL statement; the preset stress testing tool is a JMeter stress testing tool; in the prior art, when switching, there is a short external service interruption, which lasts for about 10 minutes. In this embodiment, the situation where the service status is not stopped is the online status of each component of the business application system, for example, the database is online, that is, it can be reflected in providing database access or operation functions, and the status flag can be obtained through the database system table SYS_CLUSTERS. Business services are online, for example, specifically reflected in the front-end page, and the operating user can normally perform data operations, save and function process operations.

Understandable, for example, in the business application system and test environment using the source database, use SQL statements to execute time statistics at the same time to observe whether the test results are consistent; use the JMeter stress testing tool to compare the response speed of the source database and the target database under the same conditions.

When testing the security of the target database, for example, perform functional comparison and verification on system users and operation permissions, and perform data capture and analysis on data security such as data transmission encryption and data storage encryption;

When testing the scalability of the target database, for example, without stopping the service in the built test environment, add a new server with the same configuration to the test environment to test whether it can provide external services normally;

When testing the ROSE backup data of the target database, for example, during the backup cycle, verify in the test environment whether the data of the primary target database backed up by ROSE is consistent with the data of the standby target database; and when the primary target database goes down, whether switching to the standby target database can provide normal external services.

By adjusting the database layer and interface layer of the target database in the test environment, the stability of the target database after subsequent replacement during the operation of the business application system can be ensured, reducing the risk of switching failure.

Step S130 , in the process of performing function verification and system verification on the target database, adjusting the database layer and the interface layer of the target database to obtain a target replacement database.

In the example embodiment, the performance of the target database after the migration and the ROSE backup data are systematically verified in a test environment. During the verification process, the database layer and interface layer of the target database are adjusted until all functions in the test environment are implemented, ensuring that the subsequent actual replacement process can achieve a smooth transition between the business application system using the source database and the business application system using the target database.

It should be noted that the business application system involved in the embodiment of the present application adopts a dual-machine hot standby deployment model, that is, the business application system includes a main database and a backup database. The original MySQL database is a dual-machine hot standby, in which the main database and the backup database are both MySQL databases. In order to comply with the original dual-machine hot standby deployment model, it is also necessary to create a main ACEDB database and a backup ACEDB database in the test environment. Therefore, it is necessary to first complete the technical adaptation between ROSE and the target database to ensure that the data synchronization and replication functions of the target database using ROSE are normal and meet the usage requirements.

By adjusting the database layer and interface layer of the target database in the test environment, the compatibility of the target database and the business application system after subsequent replacement can be ensured, thereby achieving smooth migration in the actual switching process and reducing the time required for switching.

Step S140: Replace the source database with the target replacement database.

By executing steps S110 to S130, the compatibility and stability test evaluation is completed before the database is replaced, so that the personnel performing the switch can clearly understand the compatibility between different database types and the replacement workload, which not only ensures the success rate of database switching; but also saves the time spent on switching, does not require long-term suspension of production applications, and greatly reduces the impact on production applications.

After step S140 , the method further includes: monitoring and evaluating the actual operation of the replaced target replacement database.

In an example embodiment, for example, the stability of a business application system using a target replacement database may be monitored and evaluated; and the stability of a replaced target replacement database may be monitored and evaluated when the business application system is running.

By monitoring and evaluating the actual operation of the target replacement database after replacement, it can be realized that if problems arise during the operation of the subsequent business application system, the problem can be located and analyzed through this monitoring process, thereby improving the efficiency of problem solving.

In a specific embodiment, the above method may specifically include: setting up database monitoring software; based on the database monitoring software, real-time monitoring of the operation of the replaced target replacement database to obtain various monitoring indicators; analyzing various monitoring indicators at preset time intervals to generate a system operation report.

In the example embodiment, the monitoring indicators include the throughput, execution time, number of concurrent connections, utilization, utilization, cache hit rate and IOPS (Input/Output Per Second) of the target database: a measure of the database's ability to process requests, including read, write, server-side and client-side requests. By monitoring the throughput, the overall load of the database can be understood. The system operation report includes: data read and write speed, hardware server name, operating system, resource consumption parameters of the database software, parameter status, and database operation status information. The database monitoring software is a monitoring software independently deployed on another server. The database monitoring software can capture the resource consumption, parameter status, and database operation status information of the hardware server, operating system, and database software through the SNMP protocol of the server operating system and the database system table, and record it in the monitoring log as a report statistics and analysis. The database system table, also known as the system catalog or system table, is a special table in the database system. These tables are mainly used to store metadata information of various objects in the database, including columns, indexes, views, stored procedures, triggers, etc.

As can be understood from the above embodiments, the embodiments of the present application analyze the usage modes and methods of the source database by the business application system before replacing the underlying database type, and intuitively display the differences in usage modes and compatibility between different database types through technical means or tools, which serves as a basis for evaluation and verification before replacing the target database, thereby changing the database evaluation and replacement work from the existing complex and ambiguous state to an intuitive and quantifiable evaluation state, effectively controlling risks and reducing the probability of replacement failure.

For example, use the migration tool to complete the database object migration from MySQL database to ACEDB database; use the data comparison and verification tool to complete the metadata and data consistency comparison between MySQL data and ACEDB database; use the network packet capture tool to capture the SQL statement executed by the embedded MySQL database in the business system; build a test environment for experimental verification, and complete the business function verification of the business application system and the target database after replacement in the test environment; deploy database monitoring software, which can be used to monitor the status, resource consumption, and operation stability of the server where the target database is located and the target database itself. Use business access stress testing tools such as LoadRunner to continuously test business concurrent access and observe response delay and system stability; use database testing tools such as BenchmarkSQL and Sysbench to continuously test the database concurrently and observe response delay and target database operation stability; replace the interface address information of the original business application system to access the database and officially switch the underlying database type; continuously monitor the operation stability of the business application system and the operation stability of the target database after replacement, so that if there are problems in the subsequent business application system operation process, the monitoring process can be used to locate and analyze the problems, thereby improving the efficiency of problem solving.

The above-mentioned steps S110 to S140 are implemented to build a test environment according to user needs and application scenarios of the source database; through the built test environment, function verification and system verification are performed on the pre-created target database; through the function verification and system verification of the target database, the database layer and the interface layer of the target database are adjusted to obtain the target replacement database; after the function verification, system verification and adjustment of the database layer and the interface layer of the target replacement database, there will be no system incompatibility problem with the source database, and it can be realized that it can replace the source database after rapid switching, and there is no need to pause for replacement for a long time, which can effectively improve the efficiency of database replacement and reduce the inconvenience caused to the normal use of users.

After introducing the method of the exemplary embodiment of the present application, a database replacement device of the exemplary embodiment of the present application is described below with reference to FIG. 2 . The database replacement device 200 includes: a building module 210, a verification module 220, an adjustment module 230, and a replacement module 240; wherein,

The building module 210 is used to build a test environment based on user needs and application scenarios of the source database;

The verification module 220 is used to perform functional verification and system verification on the pre-created target database based on the constructed test environment;

The adjustment module 230 is used to adjust the database layer and the interface layer of the target database during the process of functional verification and system verification of the target database to obtain a target replacement database;

The replacement module 240 is used to replace the source database with a target replacement database.

As an optional implementation, the verification module 220 is also used to migrate the source database to the database layer of the target database; verify the functions of the database layer and business layer of the target database after the migration is completed in the established test environment; and verify the performance and backup data of the target database after the migration is completed in the established test environment.

As an optional implementation, the verification module 220 is also used to capture a first preset statement of the source database using a preset tool; in the constructed test environment, the compatibility of the database layer and the business layer of the target database is verified based on the first preset statement.

As an optional implementation, the verification module 220 is also used to verify and count the time consumed in executing the first preset statement in the constructed test environment; to verify the response speed of the target database using a preset stress testing tool; to perform security verification on user operation permissions and data packets generated based on user operations; to verify the scalability of the target database by connecting to a pre-configured device without stopping service; and to verify the backup data of the target database within a preset backup cycle.

As an optional implementation, the database replacement device 200 is further configured to monitor and evaluate the actual operation of the replaced target replacement database.

As an optional implementation, the database replacement device 200 is also used to set up database monitoring software; based on the database monitoring software, the operation of the replaced target replacement database is monitored in real time to obtain various monitoring indicators; the various monitoring indicators are analyzed at preset time intervals to generate a system operation report.

As an optional implementation, the building module 210 is also used to obtain business replacement technical points based on the database layer, database access interface layer, and business database scheduling layer of the source database base; and create a target database based on the business replacement technical points.

After introducing the method and apparatus of the exemplary embodiment of the present application, next, the computer-readable storage medium of the exemplary embodiment of the present application is described with reference to FIG3. Please refer to FIG3, where the computer-readable storage medium shown is a CD 30 on which a computer program (i.e., a program product) is stored. When the computer program is executed by the processor, the steps described in the above method implementation are implemented, for example, a test environment is built based on user needs and application scenarios of the source database; based on the built test environment, functional verification and system verification are performed on a pre-created target database; in the process of functional verification and system verification of the target database, the database layer and the interface layer of the target database are adjusted to obtain a target replacement database; the source database is replaced with the target replacement database; the specific implementation method of each step is not repeated here.

It should be noted that examples of the computer-readable storage medium may also include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other optical or magnetic storage media, which are not listed here one by one.

After introducing the method, apparatus and medium according to the exemplary embodiment of the present application, next, a computing device for model processing according to the exemplary embodiment of the present application will be described with reference to FIG. 4 .

Fig. 4 shows a block diagram of an exemplary computing device 40 suitable for implementing the embodiments of the present application, and the computing device 40 may be a computer system or a server. The computing device 40 shown in Fig. 4 is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

As shown in FIG. 4 , the components of computing device 40 may include, but are not limited to: one or more processors or processing units 401 , system memory 402 , and a bus 403 connecting different system components (including system memory 402 and processing unit 401 ).

The computing device 40 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the computing device 40, including volatile and non-volatile media, removable and non-removable media.

The system memory 402 may include a computer system readable medium in the form of a volatile memory, such as RAM 4021 and/or a cache memory 4022, wherein the RAM is a random access memory. The computing device 40 may further include other removable/non-removable, volatile/non-volatile computer system storage media. As an example only, ROM 4023 may be used to read and write non-removable, non-volatile magnetic media (not shown in FIG. 4, commonly referred to as "hard disk drive"). Although not shown in FIG. 4, a disk drive for reading and writing a removable non-volatile disk (such as a "floppy disk"), and an optical disk drive for reading and writing a removable non-volatile optical disk (such as a CD-ROM, DVD-ROM or other optical medium) may be provided. In these cases, each drive may be connected to the bus 403 via one or more data medium interfaces. The system memory 402 may include at least one program product having a set (such as at least one) of program modules, which are configured to perform the functions of the various embodiments of the present application.

A program/utility 4025 having a set (at least one) of program modules 4024 may be stored, for example, in system memory 402, and such program modules 4024 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. Program modules 4024 generally perform the functions and/or methods of the embodiments described herein.

The computing device 40 may also communicate with one or more external devices 404 (such as keyboards, pointing devices, displays, etc.). This communication may be performed via an I/O interface 405, which is an input/output interface. In addition, the computing device 40 may also communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN) and/or a public network, such as the Internet) via a network adapter 406. As shown in Figure 4, the network adapter 406 communicates with other modules (such as a processing unit 401, etc.) of the computing device 40 via a bus 403. It should be understood that, although not shown in Figure 4, other hardware and/or software modules may be used in conjunction with the computing device 40.

The processing unit 401 executes various functional applications and data processing by running the program stored in the system memory 402, for example, based on user needs and the application scenario of the source database, a test environment is built; based on the built test environment, a pre-created target database is functionally verified and a system is verified; in the process of functionally verifying and system verifying the target database, the database layer and the interface layer of the target database are adjusted to obtain a target replacement database; and the source database is replaced with the target replacement database. The specific implementation method of each step is not repeated here. It should be noted that although several units/modules or sub-units/sub-modules of the database replacement device are mentioned in the above detailed description, this division is only exemplary and not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more units/modules described above can be concretized in one unit/module. Conversely, the features and functions of one unit/module described above can be further divided into multiple units/modules to be concretized.

In the description of the present application, it should be noted that the terms "first", "second" and "third" are only used for descriptive purposes and cannot be understood as indicating or implying relative importance.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of devices or units can be electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present application, which are used to illustrate the technical solutions of the present application, rather than to limit them. The protection scope of the present application is not limited thereto. Although the present application is described in detail with reference to the above-described embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-described embodiments within the technical scope disclosed in the present application, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

In addition, although the operations of the method of the present application are described in a specific order in the drawings, this does not require or imply that the operations must be performed in this specific order, or that all the operations shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and/or one step may be decomposed into multiple steps.

Claims (10)

1. A database replacement method, the method comprising:

based on the user requirements and the application scene of the source database, constructing a test environment;

performing function verification and system verification on a pre-established target database based on the built test environment;

In the process of performing function verification and system verification on the target database, adjusting a database layer and an interface layer of the target database to obtain a target replacement database;

And replacing the source database with the target replacement database.

2. The method of claim 1, wherein the performing functional verification and system verification on the pre-created target database based on the built test environment comprises:

migrating the source database to a database layer of the target database;

verifying the functions of a database layer and a business layer of the target database after migration is completed in the built test environment;

And verifying the performance of the target database and the backup data after the migration is completed in the built test environment.

3. The method of claim 2, wherein verifying the functions of the database layer and the business layer of the target database after the migration is completed in the built test environment comprises:

grabbing a first preset sentence of the source database by using a preset tool;

and verifying the compatibility of the database layer and the business layer of the target database based on the first preset statement in the built test environment.

4. The method of claim 3, wherein verifying the performance of the target database and the backup data after migration in the built test environment comprises:

in the built test environment, verifying and counting the time consumption of executing the first preset statement;

Verifying the response speed of the target database by adopting a preset pressure measuring tool;

Carrying out security verification on the user operation authority and the data packet generated based on the user operation;

In the state of not stopping service, accessing preconfigured equipment to verify the expandability of the target database;

and verifying the backup data of the target database in a preset backup period.

5. The method of claim 1, wherein after said replacing the source database with the target replacement database, the method further comprises:

and monitoring and evaluating the actual operation of the replaced target replacement database.

6. The method of claim 5, wherein the monitoring and evaluating the actual operation of the replaced target replacement database comprises:

setting database monitoring software;

Based on the database monitoring software, monitoring the operation of the replaced target replacement database in real time to obtain various monitoring indexes;

and analyzing each monitoring index at intervals of a preset time period to generate a system operation report.

7. The method according to claim 1, wherein the method of creating the target database comprises:

obtaining a service replacement technical point based on a database layer, a database access interface layer and a service database scheduling layer of the source database base;

and creating a target database based on the service replacement technical point.

8. A database replacement apparatus, the apparatus comprising:

The building module is used for building a test environment based on the user requirements and the application scene of the source database;

The verification module is used for carrying out function verification and system verification on a pre-established target database based on the built test environment;

The adjusting module is used for adjusting the database layer and the interface layer of the target database in the process of performing function verification and system verification on the target database to obtain a target replacement database;

And the replacing module is used for replacing the source database with the target replacing database.

9. A computer readable storage medium comprising instructions which, when run on a computer, cause the computer to perform the method of any of claims 1 to 7.

10. A computing device, the computing device comprising:

At least one processor, memory, and input output unit;

Wherein the memory is for storing a computer program and the processor is for invoking the computer program stored in the memory to perform the method of any of claims 1-7.