CN114281803A - Data migration method, device, equipment, medium and program product - Google Patents

Abstract

The present disclosure provides a data migration method, which can be applied to the field of Internet technology or the field of finance. The data migration method includes: acquiring configuration information, where the configuration information includes data connection configuration information, data migration configuration information, and user mapping; connecting a source database and a target database based on the data connection configuration information; and based on the data migration configuration information Perform data migration with user mapping, wherein the data includes parameter type data and business type data; perform data migration verification based on the data migration result; wherein, the user mapping is used to realize the matching of user parameters between the source database and the target database, The matching result is used to realize the migration of business data. The present disclosure also provides a data migration apparatus, device, medium and program product.

Description

Data migration method, apparatus, apparatus, medium and program product

technical field

The present disclosure relates to the field of Internet technology or the field of finance, and in particular, to a data migration method, apparatus, device, medium and program product.

Background technique

Data migration is an important node in system reconstruction. The existing data migration methods often have inaccurate data permissions to migrate, and the data cannot be smoothly presented in the new system after migration. When the above problems occur, it is often necessary to modify the functions and implementation methods of the new system to accommodate the deficiencies of the migrated data. A new data migration method needs to be developed to improve the accuracy and completeness of data migration and improve the smoothness of data migration in the new system.

SUMMARY OF THE INVENTION

In view of the above problems, embodiments of the present disclosure provide a data migration method, apparatus, device, medium and program product.

According to a first aspect of the present disclosure, there is provided a data migration method, including: acquiring configuration information, the configuration information including data connection configuration information, data migration configuration information, and user mapping; connecting based on the data connection configuration information source database and target database; perform data migration based on the data migration configuration information and user mapping, wherein the data includes parameter data and business data; perform data migration verification based on the data migration result; wherein the user mapping It is used to realize the user parameter matching between the source database and the target database, and the matching result is used to realize the migration of business data.

According to an embodiment of the present disclosure, the user mapping includes user combination information including at least one of a user organization and a user department, and at least one of a user name and a user registration name.

According to an embodiment of the present disclosure, the source database and the target database are heterogeneous databases.

According to an embodiment of the present disclosure, the source database is a non-relational database, and the target database is a relational database.

According to an embodiment of the present disclosure, when the file data in the source database contains attachments, the method further includes: acquiring the file data from the source database; splitting the file data into a source file and a source attachment; The source attachment is stored in the file server; the file path and identification information from the file server are obtained; the mapping relationship between the target file in the target database and the source attachment in the file server is established based on the file path and identification information, wherein the target file is the source Generated after the file is migrated to the target database.

According to an embodiment of the present disclosure, the source database is distributed and stored in m source servers, where m is an integer greater than or equal to 2, the target database is centrally stored in the target server, and the method further includes: obtaining data from the source server file data of the database; split the file data into source files and source attachments; store the source attachments in the current source server temporary directory; obtain target attachment information from the target server, wherein the target attachment information is based on the source Attachment and source file identification information are generated, and the source file identification information is obtained from the temporary directory of the source server; based on the target attachment information, a mapping relationship between the target file and the target attachment is established, wherein the target file is the source file migrated to. generated after the target database.

According to an embodiment of the present disclosure, the source file identification information includes at least one of a source server identification, an organization identification, and a source file identification.

According to an embodiment of the present disclosure, the source file identification further includes a time hash name.

A second aspect of the present disclosure provides a data migration device, comprising: a first acquisition module configured to acquire configuration information, the configuration information including data connection configuration information, data migration configuration information, and user mapping; a connection module configured to configure To connect the source database and the target database based on the data connection configuration information; the migration module is configured to perform data migration based on the data migration configuration information and user mapping, wherein the data includes parameter data and business data; The module is configured to perform data migration verification based on the data migration result; wherein, the user mapping is used to realize the matching of user parameters between the source database and the target database, and the matching result is used to realize the migration of business data.

A third aspect of the present disclosure provides an electronic device, comprising: one or more processors; a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more programs When executed by the processor, one or more processors are caused to execute the above method.

A fourth aspect of the present disclosure also provides a computer-readable storage medium having executable instructions stored thereon, the instructions, when executed by a processor, cause the processor to perform the above method.

A fifth aspect of the present disclosure also provides a computer program product, including a computer program, which implements the above method when executed by a processor.

The data migration method provided by the embodiments of the present disclosure realizes accurate matching of user parameters of the source database and the target database by configuring user mapping, and further realizes the accurate migration of business data. After migration, data permissions are accurate and can be smoothly presented in the new system.

Description of drawings

The foregoing and other objects, features and advantages of the present disclosure will become more apparent from the following description of embodiments of the present disclosure with reference to the accompanying drawings, in which:

FIG. 1 schematically shows an application scenario diagram of a data migration method, apparatus, device, medium, and program product according to an embodiment of the present disclosure.

FIG. 2 schematically shows a flowchart of a data migration method according to an embodiment of the present disclosure.

FIG. 3 schematically shows a flowchart of a method for attachment migration according to an embodiment of the present disclosure.

FIG. 4 schematically shows a flowchart of an attachment migration method according to other embodiments of the present disclosure.

FIG. 5 schematically shows a structural block diagram of a data migration apparatus according to an embodiment of the present disclosure.

FIG. 6 schematically shows a block diagram of an electronic device suitable for implementing a data migration method according to an embodiment of the present disclosure.

Detailed ways

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood, however, that these descriptions are exemplary only, and are not intended to limit the scope of the present disclosure. In the following detailed description, for convenience of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the present disclosure. It will be apparent, however, that one or more embodiments may be practiced without these specific details. Also, in the following description, descriptions of well-known structures and techniques are omitted to avoid unnecessarily obscuring the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the present disclosure. The terms "comprising", "comprising" and the like as used herein indicate the presence of stated features, steps, operations and/or components, but do not preclude the presence or addition of one or more other features, steps, operations or components.

All terms (including technical and scientific terms) used herein have the meaning as commonly understood by one of ordinary skill in the art, unless otherwise defined. It should be noted that terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly rigid manner.

Where expressions like "at least one of A, B, and C, etc.," are used, they should generally be interpreted in accordance with the meaning of the expression as commonly understood by those skilled in the art (eg, "has A, B, and C") At least one of the "systems" shall include, but not be limited to, systems with A alone, B alone, C alone, A and B, A and C, B and C, and/or A, B, C, etc. ).

It should be noted that the data migration method, apparatus, system, and electronic device provided by the embodiments of the present disclosure can be used in Internet technology related aspects of data migration, and can also be used in various fields other than Internet technology, such as the financial field. The application fields of the data migration method, apparatus, system, and electronic device provided by the embodiments of the present disclosure are not limited.

An embodiment of the present disclosure provides a data migration method, including: acquiring configuration information, where the configuration information includes data connection configuration information, data migration configuration information, and user mapping. The source database and the target database are connected based on the data connection configuration information. Data migration is performed based on the data migration configuration information and user mapping, wherein the data includes parameter data and service data. Perform data migration verification based on the data migration result. The user mapping is used to match user parameters between the source database and the target database, and the matching result is used to migrate business data.

FIG. 1 schematically shows an application scenario diagram of a data migration method, apparatus, device, medium, and program product according to an embodiment of the present disclosure.

As shown in FIG. 1 , an application scenario 100 according to this embodiment may include a data migration platform, a source database 102 , a target database 103 , a network 104 , a file server 105 and a user terminal 106 . The network 104 is used as a medium for providing a communication link between the data migration platform 101 , the source database 102 , the target database 103 , the file server 105 and the user terminal 106 . The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

The user can use the user terminal 106 to interact with the data migration platform 101 through the network 104, and set configuration information to configure the data migration. Various communication client applications may also be installed on the user terminal 106, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (just examples).

The user terminal 106 may be a variety of electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop and desktop computers, and the like.

The data migration platform 101 can obtain configuration information from the user terminal 106 and connect the source database 102 and the target database 103 according to the configuration information, thereby establishing a data migration channel between the source database 102 and the target database 103 . The data migration platform can be a background management server (just an example). The source database 102 can be stored on a single server or server cluster, which can contain one or more databases, and the target database 103 can also be stored on a single server or server cluster, which can contain one or more databases. The source database 102 may contain data to be migrated, and the target database 103 may contain migrated data, wherein the data to be migrated and the migrated data may have the same or different structures. File server 105 may be used to store attachment files.

It should be noted that, the data migration method provided by the embodiments of the present disclosure may generally be executed by the data migration platform 101 . Correspondingly, the data migration apparatus provided by the embodiments of the present disclosure may generally be provided in the data migration platform 101 . The data migration method provided by the embodiments of the present disclosure may also be executed by a server or server cluster different from the data migration platform 101 and capable of communicating with the source database 102 , the target database 103 , the file server 105 and/or the user terminal 106 . Correspondingly, the data migration apparatus provided by the embodiments of the present disclosure may also be set in a server or server cluster that is different from the data migration platform 101 and can communicate with the source database 102 , the target database 103 , the file server 105 and/or the user terminal 106 . .

It should be understood that the numbers of user terminals, data migration platforms, networks, source databases, target databases and file servers in FIG. 1 are merely illustrative. According to implementation needs, there can be any number of user terminals, data migration platforms, networks, source databases, target databases and file servers.

Based on the scenario described in FIG. 1 , the data migration method of the disclosed embodiment will be described in detail below with reference to FIGS. 2 to 4 .

FIG. 2 schematically shows a flowchart of a data migration method according to an embodiment of the present disclosure.

As shown in FIG. 2 , the data migration method of this embodiment includes operations S210 to S240.

In operation S210, configuration information is acquired.

According to an embodiment of the present disclosure, the data migration method can be implemented based on a data migration platform. To implement data migration, the data migration platform may acquire preset configuration information based on the user terminal. The typical configuration information may include data connection configuration information, data migration configuration information, and user mapping.

In an embodiment of the present disclosure, the data connection configuration information may include JDBC configuration information. JDBC is a Java database connection technology, which is a Java API for executing SQL statements and can access various databases. Typical JDBC configuration information can include a connection string, username and password. The target database can be accessed through the configured JDBC information. In the embodiment of the present disclosure, the data may include parameter type data and service type data. Correspondingly, the data migration configuration information may include but is not limited to: configuration type, file type name, file name, filter condition, attachment file configuration, file service configuration, field mapping configuration, field type, special method name, etc. Among them, the configuration type can choose to migrate business data or parameter data for configuration. The file type name can include the name of the data type to be migrated, such as signing, posting, transaction approval, etc. The file name can include the name of the database to be migrated, such as the name of a document database. The filtering conditions may include configuring filtering conditions for data extraction in the database to be migrated, such as the time range of data extraction, and the existing form of data (eg, electronic, physical, semi-electronic, etc.). Attachment file configuration may include configuring whether attachment files are involved. The file service configuration may include configuration file server related information, such as the IP address or port of the file server, and the destination path of the attachment file transfer, etc. Field mapping configuration can include configuring target database field names, corresponding fields in the source database, and their size limits. Field types include the types of fields that can be mapped, such as text, integer, numeric (float), rich text, date, time, etc. Special method names include special methods that can complete field value acquisition through the background, such as processing methods for extracting special formats that cannot be converted through conventional mapping. It can be understood that the data migration configuration information can be configured by selecting or filling in.

According to the embodiment of the present disclosure, the user mapping is used to implement the user parameter matching between the source database and the target database, and the matching result is used to implement the migration of business data. Specifically, user mapping can be established in advance to match the parameters of the same user in the source database and the target database, which is convenient for finding business data associated with the same user in the source database, and migrating the relevant business data to the target database to achieve The exact correspondence of the user and its associated business data in the target database.

According to an embodiment of the present disclosure, the user mapping may include user combination information including at least one of a user organization and a user department, and at least one of a user name and a user registration name.

In some specific embodiments, the user structure of the source database may be inconsistent with the target database. For example, the user structure in the source database is zhangsan/bj/org, and the user structure in the target database is zhangsan1.bj. The difference in user structure leads to the inability to match the user parameters of the source database and the target database during data migration, so that the accurate migration of business data cannot be achieved. The user mapping relationship between the source database and the target database can be established by using the user combination information, so as to realize the unique matching of user parameters, and then realize the complete migration of business data.

In a typical example, the user structure system in the source database is zhangsan/bj/org, the system includes the user name Zhang San, the user registered name Zhangsan, the user organization is Beijing Branch, and the user department is the office. The user structure system of the target database is zhangsan1.bj, which includes user Zhang San, the user's registered name is Zhangsan, the user organization is Beijing Branch, and the user department is the office. One or more of user organization, user department, user name and user registration name can be passed to the target database based on the source database, and the user can be looked up by the combination of user organization and/or user department, and user name and/or user registration name, if The query data is unique, the information is completely matched, and the user structure system (such as the user system name) in the target database is returned to the user structure system field of the source database. If there are users with the same name in the same user department, you can return the fault-tolerant data, and then compare the user information according to the user position to confirm the final mapped user. The user mapping relationship can be established by writing back the fields of the user structure system.

In operation S220, the source database and the target database are connected based on the data connection configuration information.

According to an embodiment of the present disclosure, the source database and the target database may be heterogeneous databases. In some specific embodiments, the source database may be a non-relational database, and the target database may be a relational database. Typical non-relational databases can include document databases. The document files may be stored in a corresponding document database based on the file type. After the file data is migrated from the document database to the relational database, a document file is stored in the relational database in the form of a record.

In operation S230, data migration is performed based on the data migration configuration information and the user mapping.

After the data migration configuration information and user mapping are configured, data migration can be performed.

In the embodiments of the present disclosure, during data migration, in order to ensure the integrity of the data migration, parameter type data may be migrated first, and then service type data may be migrated. For example, parameter data can be extracted to the target database based on migration configuration information, user parameters can be matched based on user mapping, and business data associated with parameter data can be migrated to the target database based on user parameters. Wherein, both the current processor and the transfer personnel of the data association can be the users described in the embodiments of the present disclosure.

In operation S240, data migration verification is performed based on the data migration result.

According to the embodiments of the present disclosure, after data migration is completed, data migration verification can be performed, including automatically generating a check script and accessing the target database to check the correctness of the data migration result, thereby judging whether the data migration is successful. It can be understood that after data migration, it can be reported that the migration is successful or the migration is unsuccessful. When the migration is unsuccessful, the failure reason can be returned. Typical failure reasons can include network outages, source database exceptions and/or target database exceptions, etc. There can be corresponding exception handling methods for different failure reasons. It can be understood that after the verification is performed, a check log can be generated to visually check the data migration result.

According to an embodiment of the present disclosure, when the file data in the source database contains attachments, a step of migrating attachments may also be included.

FIG. 3 schematically shows a flowchart of a method for attachment migration according to an embodiment of the present disclosure.

As shown in FIG. 3 , the data migration method of this embodiment includes operations S310 to S350.

In operation S310, file data from the source database is acquired.

In operation S320, the file data is split into source files and source attachments.

In operation S330, the source attachment is stored to a file server.

In operation S340, the file path and identification information from the file server are obtained.

In operation S350, a mapping relationship between the target file in the target database and the source attachment in the file server is established based on the file path and the identification information.

According to the embodiments of the present disclosure, in order to improve data migration efficiency and reduce attachment storage overhead, attachments may be stored based on a file server. Specifically, the file data from the source database can be split to obtain source files and source attachments. The source files can be migrated and stored in the target database, and the source attachments can be stored in the file server. In order to ensure the accuracy and integrity of data migration, a unique mapping relationship between the target file and the source attachment can be established through the file path and identification information, where the target file is generated after the source file is migrated to the target database. The file path and identification information may include information such as the IP address and/or port of the file server, and may also include directory path information stored in the attachment file, and the like. The data migration platform can obtain the file path and identification information from the file server, automatically add it to the extracted SQL statement, and then write it into the target database to realize the connection between the target file and the source attachment.

According to an embodiment of the present disclosure, the source database may be stored in one source server, or may be distributed and stored in multiple source servers. Correspondingly, the target database may be stored in one target server, or may be distributed and stored in multiple target servers. Wherein, when the source database is distributed and stored in m source servers, where m is an integer greater than or equal to 2, and the target database is centrally stored in the target server, the attachment migration method may further include the steps shown in FIG. 4 .

FIG. 4 schematically shows a flowchart of an attachment migration method according to other embodiments of the present disclosure.

As shown in FIG. 4 , the data migration method of this embodiment includes operations S410 to S450.

In operation S410, file data from the source database is acquired.

In operation S420, the file data is split into source files and source attachments.

In operation S430, the source attachment is stored in the current source server temporary directory.

In operation S440, target attachment information from the target server is acquired.

In operation S450, a mapping relationship between the target file and the target attachment is established based on the target attachment information.

According to an embodiment of the present disclosure, the target file is generated after the source file is migrated to the target database. The target attachment information is generated based on the source attachment and the source file identification information, and the source file identification information is obtained from the temporary directory of the source server.

In the embodiment of the present disclosure, a plurality of source databases may be distributed and stored in m source servers based on a preset storage standard. For example, file data may be stored in different source databases based on file types, or source databases may be stored in different source servers based on the manager of the source databases. In some specific embodiments, the organization can be used as the classification standard of the origin server. Among them, the organization can be the same as the user organization. In some cases, the source databases used to store a certain type of file data in m source servers may all contain file data w containing source attachments, that is, there are m file data w, each of which contains source files (file body) and source attachments. After the m file data w is migrated to the target database, it can exist in the form of m records in the data table. Wherein, based on the data storage rules, the source file may contain a unique identifier, while the source attachment corresponding thereto does not contain source file identifier information. In order to improve the efficiency of data migration, reduce the storage overhead of attachments, not lose attachments, and maintain the integrity of file data after migration, when migrating file data w, the file data w from the source database can be split into source files and source files. appendix. Further, the source attachment obtained by splitting can be stored in the temporary directory of the current source server. The current source server temporary directory may generate source file identification information based on the source server and/or the source file, and further write the source file identification information into the source attachment. The temporary directory of the current source server can store the source attachment containing the identification information of the source file in the target database of the target server, and generate the target attachment information. It can be understood that the target attachment information may include identification information (eg, title) of the source attachment itself and identification information of the source file. The target database can write back the target attachment information to the data migration platform. After acquiring the target attachment information from the target database, the data migration platform can automatically add it to the extracted SQL statement and write it into the target database, thereby establishing the mapping relationship between the target file and the target attachment. The steps related to the execution of the current source server can be executed by each of the m source servers, thereby preventing the attachment file from being overwritten or lost when the source attachment's own identification information (eg title) is the same. The target file is generated after the source file is migrated to the target database. Target attachments can be saved on the target server where the target database is located, or on a separate file server. When stored in the file server, the mapping relationship between the target file in the target database and the target attachment in the file server can be established based on the file path and identification information generated by the file server.

In some specific embodiments, the source file identification information includes at least one of a source server identification, an organization identification, and a source file identification. The source server identifier may include a server name, a server number, and the like. Institution ID can include institution name, institution number, institution code, etc. The source file identifier can contain the source file number, source file name, etc. In some specific embodiments, the source file identifier may further include a time hash name, where the time hash name may be the generation time, modification time, release time, etc. of the source file. It can be understood that the type of source file identification information is not limited, as long as it can uniquely identify the source file and establish an association relationship between the source file and the source attachment.

The data migration method provided by the embodiments of the present disclosure realizes accurate matching of user parameters of the source database and the target database by configuring user mapping, and further realizes the accurate migration of business data. After the migration, the data permissions are accurate, and the problems can be smoothly presented in the new system. Further, by dividing and storing the source file data and establishing the mapping relationship between the target file and the target attachment with the target attachment information, the problem of file overwriting and loss in distributed data storage is avoided, and the integrity, accuracy and security of data migration are improved. sex.

Based on the above data migration method, the present disclosure also provides a data migration apparatus. The device will be described in detail below with reference to FIG. 5 .

FIG. 5 schematically shows a structural block diagram of a data migration apparatus according to an embodiment of the present disclosure.

As shown in FIG. 5 , the data migration apparatus 500 of this embodiment includes an acquisition module 510 , a connection module 520 , a migration module 530 and a verification module 540 .

The obtaining module 510 is configured to obtain configuration information including data connection configuration information, data migration configuration information, and user mapping. User mapping is used to match user parameters between the source database and the target database, and the matching result is used to migrate business data.

The connection module 520 is configured to connect the source database and the target database based on the data connection configuration information.

The migration module 530 is configured to perform data migration based on the data migration configuration information and the user mapping, wherein the data includes parameter type data and service type data.

The verification module 540 is configured to perform data migration verification based on the data migration result.

According to an embodiment of the present disclosure, any plurality of modules in the first acquisition module 510 , the connection module 520 , the migration module 530 and the verification module 540 may be combined into one module for implementation, or any one of the modules may be split into multiple modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the first acquisition module 510 , the connection module 520 , the migration module 530 and the verification module 540 may be at least partially implemented as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a A programmed logic array (PLA), system-on-chip, system-on-substrate, system-on-package, application-specific integrated circuit (ASIC), or hardware or firmware that can be implemented in any other reasonable manner by integrating or packaging a circuit, or It can be implemented in any one of the three implementation manners of software, hardware and firmware or in an appropriate combination of any of them. Alternatively, at least one of the first acquisition module 510 , the connection module 520 , the migration module 530 and the verification module 540 may be at least partially implemented as a computer program module, which can perform corresponding functions when executed.

FIG. 6 schematically shows a block diagram of an electronic device suitable for implementing a data migration method according to an embodiment of the present disclosure.

As shown in FIG. 6 , an electronic device 900 according to an embodiment of the present disclosure includes a processor 901 that can be loaded into a random access memory (RAM) 903 according to a program stored in a read only memory (ROM) 902 or from a storage portion 908 program to perform various appropriate actions and processes. The processor 901 may include, for example, a general-purpose microprocessor (eg, a CPU), an instruction set processor and/or a related chipset, and/or a special-purpose microprocessor (eg, an application-specific integrated circuit (ASIC)), and the like. The processor 901 may also include on-board memory for caching purposes. The processor 901 may include a single processing unit or multiple processing units for performing different actions of the method flow according to the embodiments of the present disclosure.

In the RAM 903, various programs and data necessary for the operation of the electronic device 900 are stored. The processor 901 , the ROM 902 and the RAM 903 are connected to each other through a bus 904 . The processor 901 performs various operations of the method flow according to the embodiment of the present disclosure by executing the programs in the ROM 902 and/or the RAM 903 . Note that the program may also be stored in one or more memories other than the ROM 902 and the RAM 903. The processor 901 may also perform various operations of the method flow according to the embodiments of the present disclosure by executing programs stored in the one or more memories.

According to an embodiment of the present disclosure, the electronic device 900 may also include an input/output (I/O) interface 905 which is also connected to the bus 904 . Electronic device 900 may also include one or more of the following components connected to I/O interface 905: input portion 906 including keyboard, mouse, etc.; including components such as cathode ray tube (CRT), liquid crystal display (LCD), etc., and An output section 907 of speakers and the like; a storage section 908 including a hard disk and the like; and a communication section 909 including a network interface card such as a LAN card, a modem, and the like. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the I/O interface 905 as needed. A removable medium 911, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is mounted on the drive 910 as needed so that a computer program read therefrom is installed into the storage section 908 as needed.

The present disclosure also provides a computer-readable storage medium. The computer-readable storage medium may be included in the device/apparatus/system described in the above embodiments; it may also exist alone without being assembled into the device/system. device/system. The above-mentioned computer-readable storage medium carries one or more programs, and when the above-mentioned one or more programs are executed, implement the method according to the embodiment of the present disclosure.

According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, such as, but not limited to, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM) , erasable programmable read only memory (EPROM or flash memory), portable compact disk read only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. In this disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, a computer-readable storage medium may include one or more memories other than ROM 902 and/or RAM 903 and/or ROM 902 and RAM 903 described above.

Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the method illustrated in the flowchart. When the computer program product runs in the computer system, the program code is used to make the computer system implement the data migration method provided by the embodiments of the present disclosure.

When the computer program is executed by the processor 901, the above-described functions defined in the system/apparatus of the embodiment of the present disclosure are performed. According to embodiments of the present disclosure, the systems, apparatuses, modules, units, etc. described above may be implemented by computer program modules.

In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted, distributed in the form of a signal over a network medium, and downloaded and installed through the communication section 909, and/or installed from a removable medium 911. The program code embodied by the computer program may be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

In such an embodiment, the computer program may be downloaded and installed from the network via the communication portion 909, and/or installed from the removable medium 911. When the computer program is executed by the processor 901, the above-described functions defined in the system of the embodiment of the present disclosure are performed. According to embodiments of the present disclosure, the above-described systems, apparatuses, apparatuses, modules, units, etc. may be implemented by computer program modules.

According to the embodiments of the present disclosure, the program code for executing the computer program provided by the embodiments of the present disclosure may be written in any combination of one or more programming languages, and specifically, high-level procedures and/or object-oriented programming may be used. programming language, and/or assembly/machine language to implement these computational programs. Programming languages include, but are not limited to, languages such as Java, C++, python, "C" or similar programming languages. The program code may execute entirely on the user computing device, partly on the user device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (eg, using an Internet service provider business via an Internet connection).

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code that contains one or more logical functions for implementing the specified functions executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It is also noted that each block of the block diagrams or flowchart illustrations, and combinations of blocks in the block diagrams or flowchart illustrations, can be implemented in special purpose hardware-based systems that perform the specified functions or operations, or can be implemented using A combination of dedicated hardware and computer instructions is implemented.

Those skilled in the art will appreciate that various combinations and/or combinations of features recited in various embodiments and/or claims of the present disclosure are possible, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments of the present disclosure and/or in the claims may be made without departing from the spirit and teachings of the present disclosure. All such combinations and/or combinations fall within the scope of this disclosure.

Embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only, and are not intended to limit the scope of the present disclosure. Although the various embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the present disclosure is defined by the appended claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art can make various substitutions and modifications, and these substitutions and modifications should all fall within the scope of the present disclosure.

Claims (12)

1. A method of data migration, comprising:

acquiring configuration information, wherein the configuration information comprises data connection configuration information, data migration configuration information and user mapping;

connecting the source database and the target database based on the data connection configuration information;

performing data migration based on the data migration configuration information and user mapping, wherein the data comprises parameter data and service data;

performing data migration check based on the data migration result;

the user mapping is used for realizing user parameter matching of the source database and the target database, and the matching result is used for realizing migration of the service data.

2. The data migration method of claim 1, wherein the user map includes user combination information including at least one of a user organization and a user department, and at least one of a user name and a user registration name.

3. The data migration method of claim 1, wherein the source database and target database are heterogeneous databases.

4. The data migration method of claim 3, wherein the source database is a non-relational database and the target database is a relational database.

5. The data migration method of claim 4, wherein when the file data in the source database contains an attachment, the method further comprises:

acquiring file data from a source database;

splitting the file data into a source file and a source attachment;

storing the source attachment to a file server;

acquiring a file path and identification information from a file server;

and establishing a mapping relation between a target file in the target database and the source attachment in the file server based on the file path and the identification information, wherein the target file is generated after the source file is migrated to the target database.

6. The data migration method of claim 4, wherein the source database is distributed and stored in m source servers, where m is an integer greater than or equal to 2, and the target database is centrally stored in the target server, the method further comprising:

acquiring file data from a source database;

splitting file data into a source file and a source attachment;

storing the source attachment to a current source server temporary directory;

acquiring target attachment information from a target server, wherein the target attachment information is generated based on the source attachment and source file identification information, and the source file identification information is acquired from the temporary directory of the source server;

and establishing a mapping relation between a target file and the target attachment based on the target attachment information, wherein the target file is generated after the source file is migrated to the target database.

7. The data migration method according to claim 6, wherein the source file identification information includes at least one of a source server identification, an organization identification, and a source file identification.

8. The data migration method of claim 7, wherein the source file identification further comprises a temporal hash name.

9. A data migration apparatus, comprising:

a first obtaining module configured to obtain configuration information, the configuration information including data connection configuration information, data migration configuration information, and user mapping;

a connection module configured to connect the source database and the target database based on the data connection configuration information;

the migration module is configured to perform data migration based on the data migration configuration information and user mapping, wherein the data comprises parameter data and service data;

a verification module configured to perform data migration verification based on the data migration result;

the user mapping is used for realizing user parameter matching of the source database and the target database, and the matching result is used for realizing migration of the service data.

10. An electronic device, comprising:

one or more processors;

a storage device for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-8.

11. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method of any one of claims 1 to 8.

12. A computer program product comprising a computer program which, when executed by a processor, implements a method according to any one of claims 1 to 8.

Images