Database merging migration verification method, device, electronic device and storage medium

Abstract

The present application relates to a database merge migration verification method, device, electronic device and storage medium, including: obtaining source-side business data corresponding to the source library to be migrated, and obtaining data source information corresponding to the source-side business data; migrating the source-side business data to the target aggregation library table, and configuring the data source information of the aggregated business data in the target aggregation library table; when all the source libraries to be migrated are migrated, reading the target aggregated business data and the source-side business data corresponding to the data source information for comparison and verification. This method, when migrating from the source library to be migrated to the target aggregation library table, uses the data source information corresponding to the source-side business data as the data source information of the aggregated business data, so that when the migration is completed and verification is performed, the target aggregated business data can be compared and verified with the source-side business data corresponding to the data source information, achieving accurate comparison and improving the efficiency and accuracy of migration data verification and comparison.

Description

Technical Field

[0001] The present application relates to the technical field of data migration, and in particular to a database merge migration verification method, device, electronic device and storage medium. Background Art

[0002] When migrating heterogeneous databases, especially in the scenario of merging N source ends to one target end, since multiple source ends are merged into one target end, the merged data migration can be completed as long as the primary key of the target end does not conflict. However, when performing data comparison and verification after migration, if it is not clear which source end the data on the target end belongs to, it is necessary to compare with multiple source ends separately. The hit rate of the comparison result is 1 / N. Once there is a miss or multiple hits, it is impossible to make an effective and accurate judgment. For example, it is impossible to accurately judge whether the difference is caused by abnormal data itself or by comparison with incorrect database tables, resulting in low migration verification efficiency. Summary of the invention

[0003] The present application provides a database merge migration verification method, device, electronic device and storage medium to solve the technical problem of low migration verification efficiency when performing database merge migration from multiple source ends to one target end.

[0004] In a first aspect, the present application provides a database merge migration verification method, the method comprising:

[0005] Obtain source-side business data corresponding to the source database to be migrated, and obtain data source information corresponding to the source-side business data;

[0006] Migrate the source end business data to the target aggregation library table as the aggregated business data of the target aggregation library, and configure the data source information of the aggregated business data in the target aggregation library table;

[0007] When the migration of all the source libraries to be migrated is completed, read the target aggregated business data in the target aggregated library table;

[0008] The target aggregated business data is compared and verified with the source-end business data corresponding to the data source information of the target aggregated business data.

[0009] Optionally, migrating the source end business data to a target aggregation library table as aggregated business data of a target aggregation library, and configuring data source information of the aggregated business data in the target aggregation library table includes:

[0010] Creating a target aggregation library table according to the first table structure of the source library to be migrated; wherein the table structure of the target aggregation library table includes the first table structure and a target column, and the target column is used to store data source information of the aggregated business data;

[0011] Migrating the source-end business data to the first table structure of the target aggregation library table as aggregated business data of the target aggregation library;

[0012] The data source information of the source business data is configured in the target column and in the corresponding row of the aggregated business data.

[0013] Optionally, configuring the data source information of the source service data to a row in the target column corresponding to the aggregate service data includes:

[0014] Determine the data source information of the source end business data as the first source information of the aggregated business data;

[0015] The first source information of the aggregated business data is configured to a row in the target column corresponding to the aggregated business data.

[0016] Optionally, migrating the source business data to the first table structure of the target aggregation library table includes:

[0017] Transmitting the source service data to the target aggregation library through the transport layer;

[0018] Parse the data transmitted by the transport layer and write it into the first table structure of the target aggregation library table.

[0019] Optionally, comparing and verifying the target aggregated service data with source-end service data corresponding to data source information of the target aggregated service data includes:

[0020] Create multiple target queues; wherein the target queues correspond one-to-one to the source libraries to be migrated;

[0021] Reading the source-side business data of the source database to be migrated into the target queue corresponding to the source database to be migrated;

[0022] The target aggregated business data is compared and verified with the source business data in the target queue corresponding to the data source information of the target aggregated business data until all the source business data comparison is completed.

[0023] Optionally, comparing and verifying the target aggregated service data with the source-end service data in the target queue corresponding to the data source information of the target aggregated service data until all the source-end service data comparison is completed, including:

[0024] Compare and verify the target aggregated service data with the source service data in the target queue corresponding to the data source information of the target aggregated service data;

[0025] If the comparison and verification pass, the source-end business data is removed from the target queue, and the next target aggregated business data is compared and verified until the comparison of all the source-end business data in the target queue is completed.

[0026] Optionally, the target column is a hidden column.

[0027] In a second aspect, the present application provides a database merge migration verification device, the device comprising:

[0028] An acquisition module is used to acquire source-side business data corresponding to the source database to be migrated, and to acquire data source information corresponding to the source-side business data;

[0029] A migration module, used to migrate the source end business data to the target aggregation library table as the aggregated business data of the target aggregation library, and configure the data source information of the aggregated business data in the target aggregation library table;

[0030] A reading module, used for reading the target aggregated business data in the target aggregated library table when the migration of all the source libraries to be migrated is completed;

[0031] The comparison and verification module is used to compare and verify the target aggregated business data with the source business data corresponding to the data source information of the target aggregated business data.

[0032] In a third aspect, the present application provides an electronic device, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus;

[0033] Memory, used to store computer programs;

[0034] The processor is used to implement the database merge migration verification method described in any one of the embodiments of the first aspect when executing the program stored in the memory.

[0035] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the database merge migration verification method as described in any one of the embodiments of the first aspect is implemented.

[0036] The above technical solution provided by the embodiment of the present application has the following advantages over the prior art: the method provided by the embodiment of the present application obtains the source-end business data corresponding to the source library to be migrated, and obtains the data source information corresponding to the source-end business data; migrates the source-end business data to the target aggregation library table as the aggregated business data of the target aggregation library, and configures the data source information of the aggregated business data in the target aggregation library table; when the migration of all the source libraries to be migrated is completed, reads the target aggregated business data in the target aggregation library table; compares and verifies the target aggregated business data with the source-end business data corresponding to the data source information of the target aggregated business data. This method, when migrating from the source library to be migrated to the target aggregation library table, uses the data source information corresponding to the source-end business data as the data source information of the aggregated business data, so that when the migration is completed and verified, the target aggregated business data can be compared and verified with the source-end business data corresponding to the data source information, thereby achieving accurate comparison and improving the efficiency and accuracy of the migration data verification comparison. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0038] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0039] One or more embodiments are exemplarily described by pictures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings represent similar elements, and unless otherwise stated, the figures in the drawings do not constitute proportional limitations.

[0040] Figure 1 A system architecture diagram of a database merge migration verification method provided in one embodiment of the present application;

[0041] Figure 2 A schematic diagram of a process flow of a database merge migration verification method provided by an embodiment of the present application;

[0042] Figure 3 A schematic diagram of a database merge migration verification provided by an embodiment of the present application;

[0043] Figure 4 A data verification schematic diagram provided for an embodiment of the present application;

[0044] Figure 5 A schematic diagram of the structure of a database merge migration verification device provided by an embodiment of the present application;

[0045] Figure 6 A schematic diagram of the structure of an electronic device provided in accordance with an embodiment of the present application. DETAILED DESCRIPTION

[0046] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0047] The disclosure below provides many different embodiments or examples to realize the different structures of the present application. In order to simplify the disclosure of the present application, the parts and settings of specific examples are described below. Of course, they are only examples, and the purpose is not to limit the present application. In addition, the present application can repeat reference numbers and / or letters in different examples. This repetition is for the purpose of simplification and clarity, and does not itself indicate the relationship between the various embodiments and / or settings discussed.

[0048] In order to solve the technical problem of low migration verification efficiency when performing database merging and migrating multiple source ends to one target end in the prior art, the present application provides a database merging migration verification method, device, electronic device and storage medium, which can achieve that when the migration is completed and the verification is performed, the target aggregated business data can be compared and verified with the source business data corresponding to the data source information, thereby achieving accurate comparison and improving the efficiency and accuracy of migration data verification and comparison.

[0049] The first embodiment of the present application provides a database merge migration verification method, which can be applied to Figure 1 The system architecture shown includes multiple source libraries 101 to be migrated and a target aggregate library 102. The source libraries 101 to be migrated and the target aggregate library 102 establish a communication connection.

[0050] Next, based on the system architecture, the database merge migration verification method is described in detail, such as Figure 2 , the database merge migration verification method includes:

[0051] Step 201, obtaining source-side business data corresponding to the source database to be migrated, and obtaining data source information corresponding to the source-side business data.

[0052] In this embodiment, for a scenario where there are multiple source repositories to be migrated, the source business data corresponding to each source repositories to be migrated is obtained, as well as the data source information corresponding to each source business data. The data source information may be, for example, the source repositories address, source repositories name, source repositories table name, and other information that can accurately locate the source of the source business data.

[0053] Step 202: Migrate the source-side business data to the target aggregation library table as the aggregated business data of the target aggregation library, and configure the data source information of the aggregated business data in the target aggregation library table.

[0054] In one embodiment, source-end business data is migrated to a target aggregation library table as aggregated business data of the target aggregation library, and data source information of the aggregated business data is configured in the target aggregation library table, including: creating a target aggregation library table according to a first table structure of the source library to be migrated; wherein the table structure of the target aggregation library table includes a first table structure and a target column, and the target column is used to store data source information of the aggregated business data; migrating the source-end business data to the first table structure of the target aggregation library table as aggregated business data of the target aggregation library; and configuring the data source information of the source-end business data to the corresponding row of the target column with the aggregated business data.

[0055] In this embodiment, the target aggregation library table can be constructed according to the first table structure of the source library to be migrated. In the target aggregation library table, there is one more target column than the first table structure, and the target column can be used to store the data source information of the aggregated business data. The first table structure of the source end business data migrated to the target aggregation library table can be called the aggregated business data of the target aggregation library. In theory, the aggregated business data should be consistent with the source end business data before migration, but data loss and data errors may occur during the migration process. It is necessary to verify the aggregated business data after the migration is completed to ensure the consistency of the data before and after the migration. In this embodiment, during the data migration process, that is, the source end business data is migrated to the first table structure of the target aggregation library table as the aggregated business data of the target aggregation library, and the data source information of the source end business data is configured to the target column of the target aggregation library table and the corresponding row of the aggregated business data, so that each aggregated business data has its clear source information. When verifying the aggregated business data, there is no need to verify and compare with multiple source ends. It is only necessary to accurately locate which source library and which source table it belongs to according to the data source information, which improves the efficiency of verification and comparison, and reduces the occurrence of misjudgment in the case of misses.

[0056] In one embodiment, the target column can be set as a hidden column. The data source information (such as the source library address, source library name, source library table name, etc.) is stored in the hidden column in the target aggregate library table. During the comparison and verification, the information in the hidden column is parsed to achieve accurate comparison with the source end, thereby improving the verification efficiency without interfering with the normal viewing of data. During reverse reflux, the migration tool can ignore the hidden column according to the rules to avoid affecting the source end table data.

[0057] In one embodiment, the data source information of the source business data is configured to the corresponding row of the aggregated business data in the target column, including: determining the data source information of the source business data as the first source information of the aggregated business data; configuring the first source information of the aggregated business data to the corresponding row of the target column with the aggregated business data.

[0058] In this embodiment, the data source information of the source business data is determined as the first source information of the aggregated business data, and the first source information of the aggregated business data is configured in the target column and the corresponding row of the aggregated business data. The corresponding row refers to the same row as the aggregated business data, so that in the same row of each aggregated business data, the data source information of the aggregated business data is saved in the hidden target column.

[0059] In one embodiment, migrating source business data to the first table structure of the target aggregation library table includes: transmitting the source business data to the target aggregation library through the transport layer; parsing the data transmitted by the transport layer and writing it into the first table structure of the target aggregation library table.

[0060] In this embodiment, the source end business data can be transmitted to the target aggregation library through the transport layer, and the data transmitted by the transport layer can be parsed and written into the first table structure of the target aggregation library table through the playback end.

[0061] Step 203, when the migration of all source libraries to be migrated is completed, read the target aggregated business data in the target aggregated library table.

[0062] Step 204 , compare and verify the target aggregated business data with the source-end business data corresponding to the data source information of the target aggregated business data.

[0063] This method uses the data source information corresponding to the source business data as the data source information of the aggregated business data when migrating from the source database to be migrated to the target aggregate database table. Therefore, when the migration is completed and verified, the target aggregated business data can be compared and verified with the source business data corresponding to the data source information, thereby achieving accurate comparison and improving the efficiency and accuracy of the migration data verification comparison.

[0064] In one embodiment, the target aggregated business data is compared and verified with the source business data corresponding to the data source information of the target aggregated business data, including: creating multiple target queues; wherein the target queues correspond one-to-one to the source libraries to be migrated; reading the source business data of the source libraries to be migrated into the target queue corresponding to the source library to be migrated; comparing and verifying the target aggregated business data with the source business data in the target queue corresponding to the data source information of the target aggregated business data, until all source business data comparisons are completed.

[0065] In this embodiment, the comparison and verification can be performed in the data verification component. The data verification component creates multiple target queues internally. The number of target queues is the same as the number of source libraries to be migrated. Each source library to be migrated corresponds to a target queue. The data verification component reads the source business data in the source library to be migrated to its corresponding target queue. During the verification, the target aggregate business data in the target aggregation library is compared and verified one by one with the source business data in the target queue according to its data source information until all source business data comparison is completed.

[0066] In one embodiment, the target aggregated business data is compared and verified with the source business data in the target queue corresponding to the data source information of the target aggregated business data until the comparison of all source business data is completed, including: comparing and verifying the target aggregated business data with the source business data in the target queue corresponding to the data source information of the target aggregated business data; if the comparison and verification passes, the source business data is removed from the target queue, and the next target aggregated business data is compared and verified until the comparison of all source business data in the target queue is completed.

[0067] In this embodiment, the specific verification and comparison step may be to compare and verify the target aggregated business data with the source business data in the target queue corresponding to the data source information of the target aggregated business data. If the comparison and verification of the source business data passes, the source business data is removed from the target queue, and the next target aggregated business data is compared and verified until all source business data in the target queue are compared, thereby ensuring that no data is missed during the data comparison and verification process, and ensuring the accuracy and completeness of the data verification.

[0068] In a specific embodiment, the schematic diagram of database merge migration verification is as follows: Figure 3, mainly involving the three aspects of source data collection, data transmission, and target data writing of the database migration tool, and is applicable to the merge migration scenario of multiple source ends to one target end. For example, the source end includes source 1, source 2, and source 3, as well as source tables DB1.T1, DB2.T2, and DB3.T3. The aggregate library table is DB.T123, which includes all the data in source tables DB1.T1, DB2.T2, and DB3.T3, and also includes a hidden column to store the data source information (i.e., source information) corresponding to the source table data.

[0069] Specifically, the aggregation table end (also called the target aggregation table, or the target end) is used to store the migrated data. The acquisition end is responsible for collecting data from the source end, recording the data source information and passing it to the transport layer. The transport layer receives the data from the acquisition end for storage and transmission. The playback end is used to parse the transport layer data and write it to the target aggregation table. The data verification component is used to read the source end data and compare and verify it with the target end data.

[0070] In this embodiment, the aggregation library table end (target end): creates a target aggregation library table according to the table structure to be migrated, and adds a column in the table structure of the target aggregation library table to store data source information. Collection end: configures the mapping information between the source and target ends and collects the source business data. At the same time, the data source information (source library address, source library name, source library table name, etc.) is added to the collected business data. The data source information is distinguished from the business data through specific format rules to avoid polluting the business data. Transport layer: The transport layer is responsible for transmitting data to the playback end without additional processing. Playback end: The playback end parses the data transmitted by the transport layer and writes it into the target aggregation library table. Data verification component: The data verification diagram is as shown in Figure 4 , the verification component creates a target queue equivalent to the source library. Each source library corresponds to a target queue. The verification component reads the source data into the corresponding target queue. For example, the source data of source 1 is read into queue 1, the source data of source 2 is read into queue 2, and the source data of source 3 is read into queue 3. At the same time, the data in the target aggregation library table is read and its data source information (hidden column) is parsed, and then it is compared with the data in the corresponding source target queue. The compared data can be removed from the queue, and the comparison is performed in a loop in sequence until all data comparison and verification are completed.

[0071] In this embodiment, since accurate comparison can be performed, the efficiency of data comparison and verification in the migration of sub-library and sub-table to aggregated library and table data can be effectively improved, and the misjudgment in the case of misses can be reduced, thereby improving the accuracy of verification. This method requires capturing data source information (specific sub-library address, library name, sub-table name, etc.) at the migration tool layer. At the same time, it is necessary to add hidden columns to the target end aggregate table to record the data source information in a specific format to facilitate identification by the comparison tool. When performing verification, the comparison tool obtains the source information of the data by analyzing the information in the hidden column, thereby achieving accurate comparison, improving verification efficiency, and reducing data misjudgment rate.

[0072] Based on the same technical concept, the second embodiment of the present application provides a database merge migration verification device, such as Figure 5 , the device comprises:

[0073] The acquisition module 501 is used to acquire the source business data corresponding to the source database to be migrated, and acquire the data source information corresponding to the source business data;

[0074] Migration module 502, used to migrate the source end business data to the target aggregation library table as the aggregated business data of the target aggregation library, and configure the data source information of the aggregated business data in the target aggregation library table;

[0075] A reading module 503 is used to read the target aggregated business data in the target aggregated library table when the migration of all the source libraries to be migrated is completed;

[0076] The comparison and verification module 504 is used to compare and verify the target aggregated business data with the source-end business data corresponding to the data source information of the target aggregated business data.

[0077] When migrating from a source database to be migrated to a target aggregate database table, the device uses the data source information corresponding to the source-side business data as the data source information of the aggregated business data, so that when verification is performed after the migration is completed, the target aggregated business data can be compared and verified with the source-side business data corresponding to the data source information, thereby achieving precise comparison and improving the efficiency and accuracy of the migration data verification comparison.

[0078] like Figure 6 As shown, an embodiment of the present application provides an electronic device, including a processor 111, a communication interface 112, a memory 113 and a communication bus 114, wherein the processor 111, the communication interface 112, and the memory 113 communicate with each other through the communication bus 114.

[0079] Memory 113, used for storing computer programs;

[0080] In one embodiment of the present application, the processor 111 is used to implement the database merge migration verification method provided by any one of the aforementioned method embodiments when executing the program stored in the memory 113, including:

[0081] Obtain source-side business data corresponding to the source database to be migrated, and obtain data source information corresponding to the source-side business data;

[0082] Migrate the source end business data to the target aggregation library table as the aggregated business data of the target aggregation library, and configure the data source information of the aggregated business data in the target aggregation library table;

[0083] When the migration of all the source libraries to be migrated is completed, read the target aggregated business data in the target aggregated library table;

[0084] The target aggregated business data is compared and verified with the source-end business data corresponding to the data source information of the target aggregated business data.

[0085] The communication bus mentioned in the above terminal can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0086] The communication interface is used for communication between the above terminal and other devices.

[0087] The memory may include a random access memory (RAM) or a non-volatile memory, such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0088] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0089] An embodiment of the present application further provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the database merge migration verification method provided by any of the aforementioned method embodiments is implemented.

[0090] The device embodiments described above are merely illustrative, wherein 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 modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0091] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a general hardware platform, and of course, by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the relevant technology can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0092] It should be understood that the terms used herein are only for the purpose of describing specific example embodiments and are not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms "one", "an" and "said" as used herein may also be meant to include plural forms. The terms "include", "comprise", "contain", and "have" are inclusive, and therefore specify the existence of stated features, steps, operations, elements and / or parts, but do not exclude the existence or addition of one or more other features, steps, operations, elements, parts, and / or combinations thereof. The method steps, processes, and operations described herein are not interpreted as necessarily requiring them to be performed in the specific order described or illustrated, unless the execution order is clearly indicated. It should also be understood that additional or alternative steps may be used.

[0093] 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. In the description, the suffixes such as "module", "component" or "unit" used to represent the elements are only used to facilitate the description of the present application and have no specific meaning in themselves. Therefore, "module", "component" or "unit" can be used in a mixed manner.

[0094] The above description is only a specific implementation of the present application, so that those skilled in the art can understand or implement the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest range consistent with the principles and novel features applied for herein.

Claims

1. A database merge migration verification method, characterized in that: The method comprises: Obtain source-side business data corresponding to the source database to be migrated, and obtain data source information corresponding to the source-side business data; Migrate the source end business data to the target aggregation library table as the aggregated business data of the target aggregation library, and configure the data source information of the aggregated business data in the target aggregation library table; When the migration of all the source libraries to be migrated is completed, read the target aggregated business data in the target aggregated library table; The target aggregated business data is compared and verified with the source-end business data corresponding to the data source information of the target aggregated business data.

2. The method according to claim 1, characterized in that Migrating the source end business data to the target aggregation library table as the aggregated business data of the target aggregation library, and configuring the data source information of the aggregated business data in the target aggregation library table, including: Creating a target aggregation library table according to the first table structure of the source library to be migrated; wherein the table structure of the target aggregation library table includes the first table structure and a target column, and the target column is used to store data source information of the aggregated business data; Migrating the source-end business data to the first table structure of the target aggregation library table as aggregated business data of the target aggregation library; The data source information of the source business data is configured in the target column and in the corresponding row of the aggregated business data.

3. The method according to claim 2, characterized in that Configuring the data source information of the source end service data to the row corresponding to the aggregated service data in the target column includes: Determine the data source information of the source end business data as the first source information of the aggregated business data; The first source information of the aggregated business data is configured to a row in the target column corresponding to the aggregated business data.

4. The method according to claim 2, characterized in that: Migrating the source end business data to the first table structure of the target aggregation library table includes: Transmitting the source service data to the target aggregation library through the transport layer; Parse the data transmitted by the transport layer and write it into the first table structure of the target aggregation library table.

5. The method according to claim 1, characterized in that Comparing and verifying the target aggregated service data with source-end service data corresponding to data source information of the target aggregated service data includes: Create multiple target queues; wherein the target queues correspond one-to-one to the source libraries to be migrated; Reading the source-side business data of the source database to be migrated into the target queue corresponding to the source database to be migrated; The target aggregated business data is compared and verified with the source business data in the target queue corresponding to the data source information of the target aggregated business data until all the source business data comparison is completed.

6. The method according to claim 5, characterized in that Comparing and verifying the target aggregated service data with the source-end service data in the target queue corresponding to the data source information of the target aggregated service data until all the source-end service data comparisons are completed, including: Compare and verify the target aggregated service data with the source service data in the target queue corresponding to the data source information of the target aggregated service data; If the comparison and verification pass, the source-end business data is removed from the target queue, and the next target aggregated business data is compared and verified until the comparison of all the source-end business data in the target queue is completed.

7. The method according to claim 2, characterized in that: The target column is a hidden column.

8. A database merge migration verification device, characterized in that: The device comprises: An acquisition module is used to acquire source-side business data corresponding to the source database to be migrated, and to acquire data source information corresponding to the source-side business data; A migration module, used to migrate the source end business data to the target aggregation library table as the aggregated business data of the target aggregation library, and configure the data source information of the aggregated business data in the target aggregation library table; A reading module, used for reading the target aggregated business data in the target aggregated library table when the migration of all the source libraries to be migrated is completed; The comparison and verification module is used to compare and verify the target aggregated business data with the source-end business data corresponding to the data source information of the target aggregated business data.

9. An electronic device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; Memory, used to store computer programs; The processor is used to implement the database merge migration verification method described in any one of claims 1 to 7 when executing the program stored in the memory.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the database merge migration verification method according to any one of claims 1 to 7 is implemented.

Images