Data mapping relation determination method and computer equipment

Abstract

The invention provides a data mapping relation determination method and computer equipment, and the method comprises the steps: determining a plurality of business object descriptions based on application access information of a target database, the plurality of business object descriptions comprising a first business object description which comprises a name and a target business object value of a target business object, based on table field change information of the target database, multiple pieces of table field change information are determined, and the multiple pieces of table field change information comprise first table field change information which comprises table field names and table field values before and after change of the target table field; and if a table field value contained in the first table field change information is matched with a target business object value contained in the first business object description, determining that a mapping relationship exists between the first business object description and a target table field. The method can effectively reduce the manpower and time input cost, improves the data mapping efficiency, does not need to be limited by a certain mapping rule, and has high flexibility.

Description

Technical Field

[0001] This application relates to the field of database technology, and in particular to a method for determining data mapping relationships and a computer device. Background Technology

[0002] In the process of integrating and replacing business systems, data migration between heterogeneous database systems is inevitable. However, the data migration flexibility of heterogeneous database systems is relatively low, which is not conducive to improving data migration efficiency. Summary of the Invention

[0003] The purpose of this application is to provide a method and computer device for determining data mapping relationships, so as to improve the efficiency and flexibility of database data mapping.

[0004] In a first aspect, embodiments of this application provide a method for determining data mapping relationships, the method comprising:

[0005] Based on the application access information of the target database, multiple business object descriptions are determined. The multiple business object descriptions include a first business object description, which includes the name and value of the target business object.

[0006] Based on the table field change information of the target database, determine the change information of multiple table fields. The change information of multiple table fields includes the change information of the first table field, which includes the table field name and table field value of the target table field before and after the change.

[0007] If the table field values ​​contained in the first table field change information match the target business object values ​​included in the first business object description, it is determined that there is a mapping relationship between the first business object description and the target table field.

[0008] In the method of this application embodiment, the application access information of the target database contains various operation information for the target data, enabling the determination of multiple business object descriptions based on the application access information of the target database. Since the first business object description includes the name and value of the target business object, and the first table field change information includes the name and value of the target table field before and after the change, if a mapping relationship exists between the first business object description and the target table field, the target business object value matches the target table field value. Therefore, it can be determined whether the table field value contained in the first table field change information matches the target business object value included in the first business object description. If they match, it indicates that a mapping relationship exists between the first business object description and the target table field.

[0009] As can be seen, the method of this application embodiment can automatically establish a mapping relationship between the first business object description of the target database and the table fields by using the matching relationship between the target business object value and the table field value as a bridge, thereby reducing labor and time costs and improving data mapping efficiency. Moreover, regardless of the speed of change of the target table fields, it can be reflected by the first business object description mapped to the table fields. That is to say, even if the table fields of the target database change very quickly, there is no need to update the mapping rules, and the mapping relationship between the first business object description and the table fields can be quickly determined. Therefore, the method for determining the data mapping relationship of this application embodiment is highly flexible and does not need to be limited to a certain mapping rule.

[0010] In one possible implementation, the application access information of the target database in this embodiment includes the business process parameterization data of the target database. This business process parameterization data contains descriptions of various possible business objects within the business processes of the target database; therefore, multiple business object descriptions can be determined based on the business process parameterization data of the target database.

[0011] In one possible implementation, the application access information of the target database in this embodiment includes the database interface data of the target database. This database interface data contains interfaces, input parameters, timestamps, etc. When requesting access to the database, the input parameters contain descriptions of various business objects. Therefore, multiple business object descriptions can be determined based on the database interface data of the target database.

[0012] In one possible implementation, the method of this application embodiment further includes: in response to a front-end business recording start instruction for the target database, obtaining a business execution script; and based on the business execution script, obtaining business process parameterized data of the target database. Here, the business execution script determined by the process recording information of the front-end business includes not only the execution order of each sub-business contained in the business, but also the business objects and business object values ​​involved in each sub-business. Therefore, the business process parameterized data of the target database can be determined based on the business execution script.

[0013] In one possible implementation, the method of this application embodiment further includes: obtaining database access logs from the application gateway layer of the target database; and determining database interface data based on the database access logs from the application gateway layer. During each operation of the target database, access to the target database is required through the application gateway layer, which records access logs for that target database, including interface information, input parameters, and timestamps. Therefore, database interface data can be determined based on the database access logs from the application gateway layer.

[0014] In one possible implementation, based on the table field change information of the target database, multiple table field change information is determined, including:

[0015] Based on the execution query information of the target database, obtain the table field metadata corresponding to the execution query information;

[0016] Based on the table field metadata corresponding to the executed query information and the field change information of the target database, obtain the field change information of multiple tables.

[0017] The method in this application embodiment can obtain table field metadata based on the execution query information of the target database, including both the metadata of table fields that have changed and the metadata of table fields that have not changed. Therefore, based on the table field metadata corresponding to the execution query information and combined with the field change information of the target database, the change information of multiple table fields corresponding to the execution query information in the time dimension can be determined.

[0018] In one possible implementation, based on application access information from the target database, multiple business object descriptions are determined, including:

[0019] Based on the business process parameterized data of the target database, the first type of business object description is determined; based on the database interface data of the target database, the second type of business object description is determined; considering that there may be matching data between the business process parameterized data and the database interface data, which can reflect the same business object description, multiple business object descriptions are determined based on the first type of business object description and the second type of business object description, thereby obtaining the set of business objects composed of the first type of business object description and the second type of business object description.

[0020] In one possible implementation, the difference between the timestamp carried by the change information of the first table field and the timestamp carried by the description of the first business object is less than a preset difference. This can both improve the matching success rate between the first table field and the first business object description and reduce matching errors.

[0021] Furthermore, by restricting the difference between the timestamps carried in the application access information of the target database and the timestamps carried in the table field change information of the target database, the mapping relationship between the first business object description and the target table fields can be determined more quickly.

[0022] Secondly, embodiments of this application also provide a method for determining data mapping relationships, the method comprising:

[0023] Obtain the mapping relationship between business object descriptions and table fields in two databases;

[0024] Based on the mapping relationship between the business object descriptions and table fields of the two databases, the mapping relationship between the business object descriptions and the mapping relationship between the table fields of the two databases are determined.

[0025] With the above technical solution, the mapping relationship between the business object descriptions of the two databases is already determined. Therefore, it is only necessary to determine whether a mapping relationship exists between the business object descriptions of the two databases and whether a mapping relationship exists between the table fields. This approach does not require a large amount of manpower and time, and can improve the migration efficiency of heterogeneous systems. Furthermore, the process of determining the data mapping relationship between the two databases is not limited to a certain mapping rule. Therefore, the heterogeneous database system in this embodiment of the application has a high degree of flexibility in data migration between the two databases.

[0026] In one possible implementation, the mapping relationship between business object descriptions and table fields in the two databases is determined based on the mapping relationship between business object descriptions and table fields in the two databases, including:

[0027] Based on the business object descriptions of the two databases, determine the semantic correlation between the business object descriptions of the two databases;

[0028] If the semantic relevance of the business object is greater than or equal to the first preset relevance, it is determined that there is a mapping relationship between the business object descriptions of the two databases.

[0029] Based on the mapping relationship between the object descriptions of the two databases and the mapping relationship between the business object descriptions of the two databases and the table fields, the mapping relationship between the table fields of the two databases is determined.

[0030] In one possible implementation, determining the mapping relationship between the business object descriptions and table fields of the two databases, based on the mapping relationship between the business object descriptions and table fields of the two databases, further includes:

[0031] If the semantic relevance of the business objects is less than the first preset relevance, the semantic relevance of the table fields corresponding to the business objects in the two databases is determined based on the table fields corresponding to the business objects in the two databases.

[0032] If the semantic relevance of a table field is greater than the second preset relevance, it is determined that there is a mapping relationship between the table fields of the two databases;

[0033] Based on the table fields in the two databases that have mapping relationships and the mapping relationship between the business object descriptions of the two databases and the table fields, it is determined that there is a mapping relationship between the business objects of the two databases.

[0034] This application embodiment considers that when the semantic correlation between business objects is relatively low, the table fields of two databases may have a high semantic correlation. Therefore, when there may be no mapping relationship between the business object descriptions of two databases, the semantic correlation of the table fields of the two databases can be determined based on the table fields corresponding to the business objects of the two databases. If the semantic correlation of the table fields is greater than or equal to a second preset correlation, it can be determined that there is a mapping relationship between the table fields of the two databases. Since the mapping relationship between the business object description, table fields, and interface data of each database has been determined, when it is determined that there is a mapping relationship between the table fields of the two databases, it can be determined that there is a mapping relationship between the business objects of the two databases.

[0035] In one possible implementation, the two databases in this application embodiment include a first database and a second database. The method further includes:

[0036] If there is an unmapped field in the first table in the first database, in response to a mapping status change operation for the field in the first table, display a list of table fields in the second database;

[0037] In response to a selection operation on the second table field in the table field list, determine the mapping relationship between the first table field and the second table field.

[0038] As can be seen, in the embodiments of this application, when there are unmapped first table fields in the first database, a mapping relationship between the first table fields in the first database and the second table fields in the second database can be established manually.

[0039] Thirdly, embodiments of this application provide a data mapping relationship determination apparatus, the apparatus comprising:

[0040] The first determining module is used to determine multiple business object descriptions based on application access information of the target database. The multiple business object descriptions include a first business object description. Based on table field change information of the target database, multiple table field change information is determined. The multiple table field change information includes a first table field change information. The first business object description includes the name and value of the target business object. The first table field change information includes the table field name and table field value of the target table field before and after the change.

[0041] The second determining module is used to determine that there is a mapping relationship between the first business object description and the target table field if the table field value contained in the first table field change information matches the target business object value included in the first business object description.

[0042] Fourthly, embodiments of this application also provide an apparatus for determining a data mapping relationship, wherein the data mapping relationship includes a data mapping relationship between two databases, and the apparatus includes:

[0043] The acquisition module is used to obtain the mapping relationship between the business object descriptions of the two databases and the table fields;

[0044] The determination module is used to determine the mapping relationship between the business object descriptions and the table fields of the two databases based on the mapping relationship between the business object descriptions and the table fields of the two databases.

[0045] Fifthly, embodiments of this application provide a computer device, including: a processor and a memory storing a program. The program includes instructions that, when executed by the processor, cause the processor to perform the method according to the first aspect of the embodiments of this application or any possible implementation thereof.

[0046] Sixthly, embodiments of this application also provide a computer storage medium storing computer instructions that, when executed on a computer device, cause the processor of the computer device to execute the method described in the second aspect of the embodiments of this application or any possible implementation thereof.

[0047] In a seventh aspect, embodiments of this application also provide a computer program product, including a computer program, wherein the computer program, when executed by a processor, implements the method described in the first aspect or any possible implementation thereof.

[0048] Eighthly, embodiments of this application also provide a computer program product, including a computer program, wherein the computer program, when executed by a processor, implements the method described in the second aspect or any possible implementation thereof.

[0049] The beneficial effects of the technical solutions of the third, fifth and seventh aspects of the embodiments of this application can be referred to the beneficial effects of the methods described in the first aspect or any possible implementation of the first aspect of the embodiments of this application, and will not be repeated here.

[0050] The beneficial effects of the technical solutions of the fourth, sixth and eighth aspects of the embodiments of this application can be referred to the beneficial effects of the methods described in the second aspect or any possible implementation of the second aspect of the embodiments of this application, which will not be repeated here. Attached Figure Description

[0051] Further details, features, and advantages of this application are claimed in the following description of exemplary embodiments in conjunction with the accompanying drawings, in which:

[0052] Figure 1 A schematic diagram of an example ERP system architecture in which various methods described herein may be implemented, according to exemplary embodiments of this application, is shown;

[0053] Figure 2 A schematic diagram of the architecture modules of the business object mapping component in an embodiment of the application is shown;

[0054] Figure 3 A schematic diagram illustrating the principle of business object mapping in an embodiment of this application is shown;

[0055] Figure 4 A flowchart illustrating a method for determining data mapping relationships in the case of vertical mapping according to an embodiment of this application is shown.

[0056] Figure 5 A flowchart illustrating another method for determining the data mapping relationship in the case of vertical mapping according to an embodiment of this application is shown.

[0057] Figure 6 A flowchart illustrating a method for determining data mapping relationships in the case of horizontal mapping according to an embodiment of this application is shown.

[0058] Figures 7A to 7C This illustration shows an interface diagram illustrating the manual mapping of table fields between database A and database B in an embodiment of this application.

[0059] Figure 8 A schematic block diagram of a functional module of an apparatus for determining data mapping relationships according to an exemplary embodiment of this application is shown;

[0060] Figure 9 A schematic block diagram of another functional module of a data mapping relationship determination device according to an exemplary embodiment of this application is shown;

[0061] Figure 10 A schematic block diagram of a chip according to an exemplary embodiment of this application is shown;

[0062] Figure 11 A structural block diagram of an exemplary computer device that can be used to implement embodiments of this application is shown. Detailed Implementation

[0063] Embodiments of this application will now be described in more detail with reference to the accompanying drawings. While some embodiments of this application are shown in the drawings, it should be understood that this application can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this application. It should be understood that the drawings and embodiments of this application are for illustrative purposes only and are not intended to limit the scope of protection of this application.

[0064] It should be understood that the steps described in the method embodiments of this application may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this application is not limited in this respect.

[0065] The term "comprising" and its variations as used herein are open-ended, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the following description. It should be noted that the concepts of "first", "second", etc., mentioned in this application are used only to distinguish different devices, modules, or units, and are not intended to limit the order of functions performed by these devices, modules, or units or their interdependencies.

[0066] It should be noted that the terms "a" and "a plurality of" used in this application are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0067] Before introducing the embodiments of this application, the relevant terms involved in the embodiments of this application are first explained as follows:

[0068] A heterogeneous database (HDB) is a collection of multiple independent database systems that can run on different computer architectures, operating systems, and database management systems, enabling data sharing and transparent access. Each database in a heterogeneous database system existed before being added to the collection, has its own DBMS, and maintains a certain degree of autonomy, including application characteristics, integrity controls, and security controls.

[0069] Enterprise Resource Planning (ERP) systems integrate a company's business functions such as procurement, production, sales, inventory, and finance onto a single information management platform, achieving standardized information data, integrated system operation, rationalized business processes, dynamic performance monitoring, and continuous management improvement.

[0070] Change Data Capture (CDC) records insert, update, and delete operations on SQL Server tables. When CDC is enabled, data is inserted into the log table during insert, update, and delete operations on the source table. CDC captures these changes into the change table through a capture process, and this data can be captured using query functions provided by CDC.

[0071] Audit logs are an important log type in MySQL databases, used to record historical database activities, including login, logout, table creation, and table deletion operations. Audit logs can be used to track malicious behavior or abnormal operations within the database.

[0072] This application provides a method and computer device for determining data mapping relationships to improve the efficiency and flexibility of database data mapping.

[0073] Figure 1 A schematic diagram of an example ERP system architecture in which various methods described herein can be implemented, according to exemplary embodiments of this application, is shown. Figure 1 As shown, the ERP system architecture 100 of this application embodiment includes an original system 100A and a target ERP system 100B, a console 101, a migration center 102, an intelligent identification center 103, an integration and docking center 104, a distribution / merging center 105, an operation and maintenance management center 106, an operation and maintenance service center 107, and a basic service / cloud network infrastructure center 108.

[0074] The console 101 in this embodiment serves as the main entry point for system operations, used to uniformly manage and schedule various modules in the ERP system, providing a global view of the operation interface and basic control functions, making it convenient for users to control the overall process. The migration center 102 can migrate the original system 100A (e.g., historical ERP, peripheral systems) to the target ERP system 100B, and has functions such as migration orchestration, migration monitoring, and migration verification.

[0075] Optionally, during migration orchestration, the migration steps and sequence of the original system 100A can be planned, and task dependencies can be defined to ensure the orderly progress of the migration. During migration monitoring, the migration process can be tracked in real time, collecting the migration task status (such as migration progress, error status, etc.) and performance data (migration rate, etc.) to facilitate timely problem detection. During migration verification, the target ERP system 100B can be checked, comparing the consistency and accuracy of business functions and data before and after the migration to confirm whether the migration results meet expectations and ensure migration quality.

[0076] The intelligent identification center 103 in this embodiment of the application has business function mapping, business object mapping, and business process mapping. Optionally, when performing business function mapping, the business functions of the original system 100A (historical ERP or peripheral system) can be sorted out, and the sorted business functions can be mapped to the business functions of the target ERP system to clarify how the business functions are migrated and adapted, ensuring that business operations continue in the new system. When performing business object mapping, the objects involved in the business (such as orders, customers, etc.) are identified and associated to ensure accurate conversion and transmission of business object data during system migration or integration. When performing business process mapping, the business processes of the original system 100A (such as procurement processes, production processes) are parsed, and the business processes of the original system 100A are mapped to the target ERP system 100B, so that the business processes of the original system 100A run smoothly in the target ERP system 100B, and also provide a basis for process optimization.

[0077] The integration and docking center 104 in this embodiment can realize data integration, interface integration, message integration, adaptation and conversion and traffic monitoring between the original system 100A (historical ERP, peripheral systems, etc.) and the target ERP system 100B.

[0078] Optionally, during data integration, data collection, cleaning, transmission, and fusion between the original system 100A (historical ERP, peripheral systems, etc.) and the target system can be achieved to ensure accurate data flow and sharing among various modules and systems.

[0079] During interface integration, the application programming interface (API) of the original system 100A is connected to the API of the target ERP system 100B, allowing the original system 100A and the target ERP system 100B to interact through a standardized interface. In this case, when using execution query information to operate on the original system 100A through its API, the execution query information can be transmitted to the target ERP system 100B through the standardized interface. This execution query information can then be used to perform relevant data operations on the target ERP system 100B. Therefore, when the original system 100A is migrated to the target ERP system 100B, users can operate the target ERP system 100B without any awareness of the migration process.

[0080] When performing message integration, the message communication between the original system 100A and the target ERP system 100B can include message sending and receiving, routing, conversion, etc., to ensure that business events (such as order approval notifications) are transmitted between the systems in a timely and accurate manner.

[0081] When performing adaptation and conversion, if the data formats and protocols between the original system 100A and the target ERP system 100B are incompatible, the data of the original system 100A and the target ERP system 100B can be converted and adapted to ensure seamless interaction between the original system 100A and the target ERP system 100B.

[0082] When monitoring traffic, the system can integrate data traffic and request frequency when the original 100A system is connected to the target system to understand the interaction load and prevent system performance problems caused by excessive traffic.

[0083] The traffic distribution / merging center 105 in this embodiment can allocate or aggregate business traffic and data flow according to business needs or system status. For example, some business requests can be distributed to the target ERP system for processing, while others can still be processed through the original system 100A; or multiple sources of data can be merged and processed in a unified manner to flexibly control system load and business flow.

[0084] The operation assurance management center 106 in this application embodiment focuses on the stable operation of the system, covering system fault early warning, emergency response plan execution, resource (server, storage, etc.) allocation and optimization, to ensure the reliable operation of the ERP system around the clock and reduce the risk of business interruption.

[0085] The operation and maintenance service center 107 in this embodiment provides daily operation support for the ERP system, including user problem response (such as operation consultation and fault reporting), system performance optimization (parameter tuning and configuration upgrade), regular inspection and maintenance, etc., to ensure that users can use the ERP system smoothly and maintain the ERP system in good condition.

[0086] The underlying support for the operation of the basic service / cloud network infrastructure center 108 in this application embodiment includes cloud computing resource (server, storage, network) configuration, network architecture construction (internal network and external network connection), and basic security protection (firewall, encryption, etc.), providing a stable and secure operating environment for the upper-layer ERP and related modules.

[0087] The ERP core in the target ERP system 100B of this application embodiment is the core layer of the ERP system, which includes a variety of ERP products, carries the core business processes of the enterprise, provides basic business functions and data management capabilities, and is the core engine of the enterprise's digital operation.

[0088] The business object mapping function in this application embodiment can be implemented through a business object mapping component. Figure 2 This illustration shows a schematic diagram of the architecture modules of the business object mapping component in an embodiment of the application. Figure 3 A schematic diagram illustrating the business object mapping principle of an embodiment of this application is shown. For example... Figure 2 and Figure 3 As shown, the business object mapping component 200 in this application embodiment includes a metadata management module 201A, a script execution engine 201B, a log access module 201C, a mapping analysis module 202, a semantic mapping module 203, and a storage device 204.

[0089] The metadata management module 201A can provide metadata management for table fields in the databases of the original system 100A and the target system. Table fields in the database can be obtained through this metadata management module 201A.

[0090] The Script Execution Engine 201B can create recording tasks, automatically traversing the front-end pages of the original system and the front-end of the target system to generate business execution scripts for two databases. By executing these scripts, the business process is automatically replayed, obtaining the form parameters associated with each operation in both databases, as well as the recording and playback logs associated with business object attributes. For example, the recording and playback logs for each database can contain parameterized data of the business process in the target database, which may include descriptions of business objects such as business object names and values, as well as operation times, but are not limited to these.

[0091] The 201C log access module can support the access of database access logs, database audit logs, recording and playback logs, and CDC change logs.

[0092] The mapping analysis module 202 can combine metadata, application access logs, database audit logs, recording and playback logs, and CDC change logs to vertically analyze the mapping relationship between object attributes and table fields within the same database.

[0093] The semantic mapping module 203 can generate data mapping relationships between two databases based on a mapping analysis algorithm. These data mapping relationships can include mapping relationships between business object descriptions and table field mapping relationships. The storage device 204 can store these data mapping relationships for use during database migration.

[0094] This application provides a method for determining data mapping relationships, which can be executed by a computer device or a chip applied to a computer device. The data mapping relationship is divided into vertical data mapping and horizontal data mapping. Vertical mapping can refer to various data mappings within a single database, while horizontal mapping can refer to various data mappings between two databases.

[0095] From the perspective of vertical data mapping, the data mapping relationship determination method of this application embodiment includes the mapping relationship between the business object description in the target database and the table fields. The following describes the data mapping relationship determination method using the mapping relationship between the first business object description and the target table fields as an example.

[0096] Figure 4 A flowchart illustrating a method for determining data mapping relationships in the case of vertical mapping, according to an embodiment of this application, is shown. Figure 4 As shown, the data mapping relationship determination method 400 of this application embodiment includes steps 401 to 403.

[0097] In step 401, based on the application access information of the target database, multiple business object descriptions are determined. These multiple business object descriptions include a first business object description, which includes the name and value of the target business object. Here, the first business object description can be any one of the multiple business object descriptions.

[0098] When performing operations on the front-end page of the target database, all operations will access the target database through the database gateway layer. Therefore, the application access information of the target database contains various operation information on the target data, which allows multiple business object descriptions to be determined based on the application access information of the target database.

[0099] In step 402, based on the table field change information of the target database, multiple table field change information is determined. This includes first table field change information, which comprises the table field name and value before and after the change. Here, the first table field change information can be any one of the multiple table field change information. Table fields can include table information (such as table model), field names, and field values; fields containing table information can be defined as table fields.

[0100] This application embodiment can enable CDC change logging to obtain a CDC change log. The CDC change log can record field change information of the target database during each operation, such as the field name and value of table fields before and after the change. Therefore, the field change information of the target database can be parsed from the CDC change log, and multiple table field change information can be determined based on the table field change information of the target database.

[0101] In step 403, if the table field values ​​contained in the first table field change information match the target business object values ​​included in the first business object description, a mapping relationship is determined between the first business object description and the target table field. This matching can be indirect, such as the target business object value being the same as the table field value, or it can be based on semantic similarity. Semantic similarity can be measured using cosine similarity or determined using a semantic similarity model.

[0102] In this embodiment, the multiple business object descriptions include a first business object description that includes the name and value of the target business object, and a first table field change information that includes the field name and value of the target table field before and after the change. If there is a mapping relationship between the first business object description and the target table field, the target business object value matches the target table field value. Therefore, it can be determined whether the table field value contained in the first table field change information matches the target business object value included in the first business object description. When the table field value contained in the first table field change information matches the target business object value included in the first business object description, it indicates that there is a mapping relationship between the first business object description and the target table field.

[0103] As can be seen, the method of this application embodiment can automatically establish a mapping relationship between the first business object description of the target database and the table fields by using the matching relationship between the target business object value and the table field value as a bridge, thereby reducing labor and time costs and improving data mapping efficiency. Moreover, regardless of the speed of change of the target table fields, it can be reflected by the first business object description mapped to the table fields. That is to say, even if the table fields of the target database change very quickly, there is no need to update the mapping rules, and the mapping relationship between the first business object description and the table fields can be quickly determined. Therefore, the method for determining the data mapping relationship of this application embodiment is highly flexible and does not need to be limited to a certain mapping rule.

[0104] In one possible implementation, the application access information of the target database includes the target database's business process parameterized data, the target database's database interface data, or both the target database's business process parameterized data and the target database's database interface data.

[0105] When the application access information of the target database includes parameterized business process data of the target database, the method in this embodiment further includes: obtaining a business execution script in response to a front-end business recording start instruction for the target database. The type of the business execution script can be common languages ​​such as Python and JavaScript, but is not limited to these.

[0106] The business execution script in this application embodiment includes not only the execution order of each sub-business contained in the business, but also the business objects and business object values ​​involved in each sub-business. Therefore, the recording and playback logs of the front-end page of the target database can be obtained based on the business execution script, which contain the business process parameterized data of the target database.

[0107] When the application access information of the target database includes the database interface data of the target database, the method in this application embodiment further includes: obtaining the database access log of the application gateway layer of the target database; determining the database interface data based on the database access log of the application gateway layer; the database interface data can be determined based on the database access log of the application gateway layer.

[0108] During each operation on the target database, access to the target database is required through the application gateway layer. The application gateway layer records the access logs for accessing the target database, which include the interface, input parameters, and timestamps. The input parameters contain a description of the business object. Therefore, the database interface data can be identified through the database access logs of the application gateway layer, and this database interface data contains a description of the business object.

[0109] When the application access information of the target database includes the target database's business process parameterized data and the target database's database interface data, considering that there may be matching data between the business process parameterized data and the database interface data, which can reflect the same business object description, for example, there may be a matching relationship between the business object values ​​contained in the business process parameterized data and the input parameters contained in the database interface data, therefore, based on the target database's business process parameterized data, a first type of business object description is determined; based on the first type of business object description and the second type of business object description, multiple business object descriptions are determined.

[0110] Since there may be matching data between the parameterized data of the business process and the database interface data, the process of determining multiple business object descriptions is essentially a process of merging the matching business object descriptions contained in the first type of business object description and the second type of business object description, so as to obtain a set of business object descriptions formed by the first type of business object description and the second type of business object description (e.g., multiple business object descriptions).

[0111] In one possible implementation, the difference between the timestamp carried by the change information of the first table field in this embodiment and the timestamp carried by the first business object description is less than a preset difference. For example, the preset difference can be 250ms to 350ms, such as 250ms, 300ms, or 350ms. This improves the matching success rate between the first table field and the first business object description while reducing matching errors. Furthermore, by constraining the difference between the timestamp carried by the application access information of the target database and the timestamp carried by the change information of the table field in the target database, the mapping relationship between the first business object description and the target table field can be determined more quickly.

[0112] To obtain the time-dimensional mapping relationship between table field change information and application access information, taking application access information including database interface data as an example, the time-dimensional mapping relationship between the executed query information and the database interface data can be determined based on the executed query information and the database interface data of the target database. Based on the time-dimensional mapping relationship between the executed query information and the database interface data, and the table field change information corresponding to the executed query information in the time dimension, the database interface data and table field change information that match the time information can be determined.

[0113] As can be seen, the method in this embodiment uses time information as a parameter and execution query information as a bridge to match the time information carried by the application access information of the target database with the time information carried by the table field change information of the target database. This allows for a faster determination of the mapping relationship between the first business object description and the target table fields.

[0114] Optionally, based on the execution query information of the target database, the table field metadata corresponding to the execution query information can be obtained; based on the table field metadata corresponding to the execution query information and the field change information of the target database, the table field change information corresponding to the execution query information in the time dimension can be obtained.

[0115] This application embodiment can enable the audit log recording function of the target database to obtain the audit log of the target database. By parsing the audit log of the target database, the execution query information of the target database can be obtained.

[0116] In one example, the execution query information of the target database may include the main SQL statement executed in each execution, which contains execution time and table information (i.e., table model), and the table information contains field metadata. In other words, the execution query information of the target database implicitly contains table information. Therefore, based on the execution query information of the target database, the table information corresponding to the execution query information can be obtained; and based on the table information corresponding to the execution query information, the table field metadata corresponding to the execution query information can be obtained.

[0117] In one example, the table field metadata obtained based on the table information corresponding to the executed query information includes both the metadata of the table fields that have changed and the metadata of the table fields that have not changed. Therefore, based on the table field metadata corresponding to the executed query information and combined with the field change information of the target database, the table field change information corresponding to the executed query information in the time dimension can be determined.

[0118] For example, when executing query information corresponds to table field metadata, the field metadata is associated with the execution time of the query information. The field change information of the target database includes the field change time, the field name before and after the change, and the field value. Therefore, by matching the field change time included in the field change information of the target database with the execution time included in the query information, the table field change information corresponding to the query information in the time dimension can be obtained.

[0119] Of course, the table field metadata obtained based on the table information corresponding to the executed query information includes both the metadata of table fields that have changed and the metadata of table fields that have not changed. Therefore, after obtaining the table field change information corresponding to the executed query information in the time dimension, there are still table fields that have not changed, and a time dimension mapping relationship has not been established with the executed query information. However, the table fields that have not changed can still be recorded and can be mapped in the horizontal data mapping process.

[0120] In an alternative approach, the method of this application embodiment, in addition to obtaining the mapping relationship between the first business object description and the target table fields, can also obtain the relationship between the first business object description, the target table fields, and the interface. Figure 5 A flowchart illustrating another method for determining the data mapping relationship in the case of vertical mapping, according to an embodiment of this application, is shown. Figure 5 As shown, the data mapping relationship determination method 500 of this application embodiment includes steps 501 to 506.

[0121] In step 501, the business process parameterized data, database interface data, table field change information, and execution query information of the target database are obtained. The methods for obtaining the business process parameterized data, database interface data, table field change information, and execution query information can be found in the preceding descriptions.

[0122] On the one hand, it is necessary to enable the audit log and CDC change log of the target database in advance to record the audit log and CDC change log of the target database. In order to use the audit log of the target database to parse the execution query information of the target database, and use the CDC change log to parse the table field change information of the target database.

[0123] On the other hand, it is necessary to obtain application access logs such as interface, timestamp, and input parameters for each operation request through the application gateway layer of the target database, so as to parse out the database interface data of the target database; and create a recording task through the script execution engine on the front-end page to obtain the business execution script of the front-end page. Then, by executing the business execution script, the parameterized data of the business process of the target database can be obtained.

[0124] In step 502, based on the database interface data and the execution query information of the target database, the mapping relationship between the execution query information and the interface in the time dimension is determined. This can be achieved by matching the timestamp carried in the database interface data and the timestamp carried in the execution query information. For example, if the difference between the timestamp carried in the database interface data and the timestamp carried in the execution query information is less than 300ms, the database interface data and the execution query information can be considered a match.

[0125] In step 503, based on the execution query information of the target database, the table model corresponding to the execution query information is determined, and based on the table model corresponding to the execution query information, the field metadata corresponding to the execution query information is determined. Here, the execution query information can be the execution of an SQL statement.

[0126] In step 504, based on the field metadata corresponding to the executed query information and the table field change information of the target database, the table field change information corresponding to the executed query information in the time dimension is determined. For example, the table field change information corresponding to the executed query information in the time dimension can be determined by comparing the time information carried by the executed query information and the time information carried by the table field change information. At the same time, it is also possible to identify a portion of the table fields corresponding to the executed query information that are not included in the table field change information.

[0127] In step 505, based on the business process parameterized data in the target database and the table field change information in the target database, the mapping relationship between the business object description and the table fields is determined. The process of determining the mapping relationship between the business object description and the table fields can be found in [the documentation / reference needed]. Figure 4 Related descriptions.

[0128] In step 506, based on the mapping relationship between the business object description and table fields, the changes in table fields corresponding to the executed query information in the time dimension, and the mapping relationship between the executed query information and the interface in the time dimension, the mapping relationship between the business object description, table fields, and interface is determined. After determining this mapping relationship, it can be saved in the database for later use in horizontal mapping.

[0129] The method for determining data mapping relationships provided in this application, from the perspective of horizontal data mapping, includes business object description mapping relationships between two databases, as well as table field mapping relationships between the two databases. For ease of description, the two databases will be defined as the first database and the second database below.

[0130] Figure 6 A flowchart illustrating a method for determining data mapping relationships in the case of horizontal mapping, according to an embodiment of this application, is shown. Figure 6 As shown, the data mapping relationship determination method 600 of this application embodiment includes steps 601 and 602.

[0131] In step 601, the mapping relationship between the business object description and table fields of the first database and the mapping relationship between the business object description and table fields of the second database are obtained.

[0132] For both the first and second databases, the mapping relationship between the business object description and the table fields can be found in the process of determining the data mapping relationship in the case of vertical mapping, which will not be detailed here.

[0133] In step 602, based on the mapping relationship between the business object descriptions and table fields in the first database and the mapping relationship between the business object descriptions and table fields in the second database, the mapping relationship between the business object descriptions and table fields in the first database and the second database is determined.

[0134] In this embodiment, the mapping relationships between business object descriptions and table fields in the first database and between business object descriptions and table fields in the second database have been determined. Therefore, it is only necessary to determine whether a mapping relationship exists between the business object descriptions of the first and second databases, and whether a mapping relationship exists between the table fields. This approach does not require significant manpower and time, and can improve the migration efficiency of heterogeneous systems. Furthermore, the process of determining the data mapping relationship between the two databases is not limited to a certain mapping rule; therefore, the heterogeneous database system in this embodiment offers high flexibility in data migration between the two databases.

[0135] In one alternative approach, a semantic similarity analysis model can be used to describe the semantic similarity of business objects and table fields between the first and second databases, directly outputting the mapping relationship between business objects and the mapping results of table fields.

[0136] In another alternative approach, the semantic relevance of business object descriptions between the first and second databases can be determined based on the business object descriptions in the first and second databases. In one example, a simple similarity tool, such as a commonly used word segmentation tool with similarity comparison capabilities, can be used to analyze the semantic relevance of business object descriptions between the first and second databases. Here, the similarity analysis of business object descriptions can be a similarity analysis of the names of business objects within the descriptions.

[0137] If the semantic relevance of a business object is greater than or equal to the first preset relevance (e.g., 70% to 90%), it indicates that the semantic relevance of the business object is relatively high, and it can be determined that there is a mapping relationship between the business object descriptions of the first database and the second database. If the semantic relevance of a business object is less than the first preset relevance, it indicates that the semantic relevance of the business object is relatively low, and there may be no mapping relationship between the business object descriptions of the first database and the second database.

[0138] If the semantic relevance of the business objects is less than the first preset relevance, it indicates that there may be no mapping relationship between the business object descriptions in the first database and the business object descriptions in the second database. However, considering that the difference in the names of the two business objects may be too great, resulting in a superficial lack of mapping relationship rather than a substantial one, if the semantic relevance of the business objects is less than the first preset relevance, the semantic relevance of the table fields between the first and second databases can be determined based on the table fields corresponding to the business objects in the first and second databases. Here, the semantic relevance of the table fields can be the semantic relevance of the table field names, and the method for determining the semantic relevance can refer to the method for determining the semantic relevance of the business objects.

[0139] If the semantic relevance of a table field is greater than the second preset relevance (e.g., 70%–90%), it indicates a relatively high semantic relevance between the table fields in the first and second databases. Therefore, it can be determined that a mapping relationship exists between the table fields in the first and second databases. This also proves, from another perspective, that a mapping relationship exists between the business object descriptions in the first and second databases, even if the surface differences between them are too large.

[0140] In one possible implementation, the method of this application embodiment can also manually select the mapping relationship of table fields. For example, if there is a first table field in the first database that is not mapped, in response to a mapping status change operation for the first table field, a list of table fields in the second database is displayed. In response to a selection operation for a second table field in the list of table fields, the mapping relationship between the first table field and the second table field is determined. Therefore, in this application embodiment, when there is a first table field in the first database that is not mapped, a mapping relationship between the first table field in the first database and the second table field in the second database can be established manually.

[0141] Figures 7A to 7C This illustration shows an interface diagram illustrating the manual mapping of table fields between database A and database B according to an embodiment of this application. The following is in conjunction with... Figures 7A to 7C Describe the process of manually mapping table fields between two databases using an example.

[0142] like Figure 7A As shown, after clicking the Auto Mapping Analysis Object component 701, the table fields of database A and database B can be automatically mapped. The mapping process can be found in the previous description. If you need to cancel the table field mapping between database A and database B, you can click the Reset component 703 to remove the mapping relationship.

[0143] like Figure 7A As shown, the new business object component 702A in database A supplements missing business objects for database A, and the new business object component 702B in database B supplements missing business objects for database B. For example, if a business object is missing in the fourth row of the mapping table in database B, it can be supplemented using the new business object component 702B.

[0144] In the mapping status field of the mapping tables in databases A and B, a value of "Mapped" in a row indicates that the field has been mapped, while a value of "Unmapped" indicates that the field has not been mapped. Taking the mapping table in database A as an example, the fifth row of the mapping status field has a value of "Unmapped." You can click the dropdown control "704" next to the fifth row value to display... Figure 7BThe table field list is 705.

[0145] like Figure 7B As shown, in the mapping table of database A, the fields displayed in table field list 705 are fields from database B. You can manually select the desired target field from table field list 705, such as `unit_code`, and use this target field as the field mapped to `VENDOR_SITE_ID`. At this point, through... Figure 7B The settings are such that the value of the fifth row of the mapping status field in the mapping table of data table A changes from... Figure 7A Unmapped in Figure 7C The mapped data is already present in the database.

[0146] The foregoing primarily describes the solutions provided in the embodiments of this application from the perspective of computer devices. It is understood that, in order to achieve the aforementioned functions, the computer device includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the various examples described in the embodiments herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0147] This application embodiment can divide a computer device into functional units based on the above method example. For example, it can divide each function into separate functional modules, or it can integrate two or more functions into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division; in actual implementation, there may be other division methods.

[0148] In the case of dividing each functional module according to its corresponding functions, an exemplary embodiment of this application provides a data mapping relationship determination device, which can be a computer device or a chip applied to a computer device. Figure 8 A schematic block diagram of a functional module of an apparatus for determining data mapping relationships according to an exemplary embodiment of this application is shown. Figure 8 As shown, the data mapping relationship determination device 800 includes:

[0149] The first determining module 801 is used to determine multiple business object descriptions based on application access information of the target database. The multiple business object descriptions include a first business object description. Based on table field change information of the target database, multiple table field change information is determined. The multiple table field change information includes the first table field change information. The first business object description includes the name and value of the target business object. The first table field change information includes the table field name and table field value of the target table field before and after the change.

[0150] The second determining module 802 is used to determine that there is a mapping relationship between the first business object description and the target table field if the table field value contained in the first table field change information matches the target business object value included in the first business object description.

[0151] In one possible implementation, the application access information of the target database includes parameterized business process data of the target database; and / or,

[0152] The application access information of the target database includes the database interface data of the target database.

[0153] In one possible implementation, the device 800 further includes: an acquisition module 803, configured to acquire a business execution script in response to a front-end business recording start instruction for the target database; and acquire business process parameterized data of the target database based on the business execution script.

[0154] In one possible implementation, the device 800 further includes an acquisition module 803, which acquires the database access logs of the application gateway layer of the target database; and acquires the database interface data based on the database access logs of the application gateway layer.

[0155] In one possible implementation, the difference between the timestamp carried by the change information of the first table field and the timestamp carried by the description of the first business object is less than a preset difference.

[0156] In one possible implementation, the first determining module is configured to determine a first type of business object description based on the business process parameterization data of the target database; determine a second type of business object description based on the database interface data of the target database; and determine multiple business object descriptions based on the first type of business object description and the second type of business object description.

[0157] In the case of dividing each functional module according to its corresponding functions, an exemplary embodiment of this application provides a data mapping relationship determination device, which can be a computer device or a chip applied to a computer device. Figure 9A schematic block diagram of another functional module of a data mapping relationship determination device according to an exemplary embodiment of this application is shown. Figure 9 As shown, the data mapping relationship determination device 900 includes:

[0158] Module 901 is used to obtain the mapping relationship between the business object descriptions and table fields of the two databases;

[0159] The determination module 902 is used to determine the mapping relationship between the business object descriptions and the table fields of the two databases based on the mapping relationship between the business object descriptions and the table fields of the two databases.

[0160] In one possible implementation, the determining module 902 is used to determine the semantic correlation of business objects in the two databases based on the business object descriptions of the two databases; if the semantic correlation of business objects is greater than or equal to a first preset correlation, it is determined that there is a mapping relationship between the business object descriptions of the two databases; and based on the mapping relationship between the object descriptions of the two databases and the mapping relationship between the business object descriptions of the two databases and the table fields, it determines the table field mapping relationship of the two databases.

[0161] In one possible implementation, the determining module 902 is further configured to: if the semantic correlation of the business object is less than a first preset correlation, determine the semantic correlation of the table fields of the two databases based on the table fields corresponding to the business objects of the two databases; if the semantic correlation of the table fields is greater than or equal to a second preset correlation, determine that there is a mapping relationship between the table fields of the two databases; and determine that there is a mapping relationship between the business objects of the two databases based on the table fields of the two databases that have a mapping relationship.

[0162] In one possible implementation, the two databases include a first database and a second database, and the device 900 further includes an interaction module 903, configured to, if there is an unmapped first table field in the first database, display a list of table fields in the second database in response to a mapping status change operation for the first table field; and, in response to a selection operation for a second table field in the list of table fields, determine the mapping relationship between the first table field and the second table field.

[0163] Figure 10 A schematic block diagram of a chip according to an exemplary embodiment of this application is shown. Figure 10 As shown, the chip 1000 includes one or more (including two) processors 1001 and a communication interface 1002. The communication interface 1002 can support the computer device to perform the data transmission and reception steps in the above method, and the processor 1001 can support the computer device to perform the data processing steps in the above method.

[0164] Optional, such as Figure 10 As shown, the chip 1000 also includes a memory 1003, which may include read-only memory and random access memory, and provides operation instructions and data to the processor. A portion of the memory may also include non-volatile random access memory (NVRAM).

[0165] In some implementations, such as Figure 10 As shown, processor 1001 executes corresponding operations by calling operation instructions stored in memory (which may be stored in the operating system). Processor 1001 controls the processing operations of any terminal device; processor can also be called a central processing unit (CPU). Memory 1003 may include read-only memory and random access memory, and provides instructions and data to processor 1001. A portion of memory 1003 may also include NVRAM. For example, in applications, memory, communication interfaces, and other components are coupled together via a bus system, which may include, in addition to a data bus, a power bus, a control bus, and a status signal bus, etc. However, for clarity, in... Figure 10 The general labeled all buses as Bus System 1004.

[0166] The methods disclosed in the embodiments of this application can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processor (DSP), an ASIC, a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams of the application in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods applied in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory; the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0167] An exemplary embodiment of this application also provides a computer device, including: at least one processor; and a memory communicatively connected to the at least one processor. The memory stores a computer program executable by the at least one processor, the computer program being executed by the at least one processor to cause the computer device to perform a method according to an embodiment of this application.

[0168] An exemplary embodiment of this application also provides a non-transitory computer-readable storage medium storing a computer program, wherein the computer program, when executed by a computer's processor, is used to cause the computer to perform a method according to an embodiment of this application.

[0169] An exemplary embodiment of this application also provides a computer program product, including a computer program, wherein, when executed by a computer's processor, the computer program is used to cause the computer to perform a method according to an embodiment of this application.

[0170] refer to Figure 11 The following is a structural block diagram of a computer device 1100 that can serve as a computer device or client of this application, which is an example of a hardware device that can be applied to various aspects of this application. The term "computer device" is intended to represent various forms of digital electronic computer devices, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. A computer device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the application described and / or claimed herein.

[0171] like Figure 11 As shown, computer device 1100 includes a computing unit 1101, which can perform various appropriate actions and processes according to a computer program stored in read-only memory (ROM) 1102 or a computer program loaded from storage unit 1108 into random access memory (RAM) 1103. The RAM 1103 may also store various programs and data required for the operation of device 1100. The computing unit 1101, ROM 1102, and RAM 1103 are interconnected via bus 1104. Input / output (I / O) interface 1105 is also connected to bus 1104.

[0172] like Figure 11As shown, multiple components in computer device 1100 are connected to I / O interface 1105, including: input unit 1106, output unit 1107, storage unit 1108, and communication unit 1109. Input unit 1106 can be any type of device capable of inputting information to computer device 1100. Input unit 1106 can receive input numerical or character information and generate key signal inputs related to user settings and / or function control of the computer device. Output unit 1107 can be any type of device capable of presenting information and may include, but is not limited to, a monitor, speaker, video / audio output terminal, vibrator, and / or printer. Storage unit 1108 may include, but is not limited to, hard disks and optical disks. Communication unit 1109 allows computer device 1100 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks, and may include, but is not limited to, modems, network cards, infrared communication devices, wireless communication transceivers, and / or chipsets, such as Bluetooth™ devices, WiFi devices, WiMax devices, cellular communication devices, and / or the like.

[0173] like Figure 11 As shown, computing unit 1101 can be various general-purpose and / or dedicated processing components with processing and computing capabilities. Some examples of computing unit 1101 include, but are not limited to, central processing unit (CPU), graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Computing unit 1101 performs the various methods and processes described above. For example, in some embodiments, the methods of the embodiments of this application can be implemented as computer software programs tangibly contained in a machine-readable medium, such as storage unit 1108. In some embodiments, part or all of the computer program can be loaded and / or installed on computer device 1100 via ROM 1102 and / or communication unit 1109. In some embodiments, computing unit 1101 can be configured to perform the methods of the embodiments of this application by any other suitable means (e.g., by means of firmware).

[0174] The program code used to implement the methods of this application may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing device, such that when executed by the processor or controller, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0175] In the context of this application, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0176] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device for displaying information to the user (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor); and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0177] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as a data server), or computing systems that include middleware components (e.g., an application server), or computing systems that include frontend components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with embodiments of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., a communication network). Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.

[0178] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other.

[0179] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a terminal, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video disc (DVD); or it can be a semiconductor medium, such as a solid-state drive (SSD).

[0180] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the spirit and scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A method for determining data mapping relationships, characterized in that, The method includes: Based on the application access information of the target database, multiple business object descriptions are determined, including a first business object description, which includes the name and value of the business object. Based on the table field change information of the target database, multiple table field change information is determined. The multiple table field change information includes first table field change information, which includes the table field name and table field value of the target table field before and after the change. If the table field values ​​contained in the first table field change information match the business object values ​​included in the first business object description, it is determined that there is a mapping relationship between the first business object description and the target table field.

2. The method according to claim 1, characterized in that, The application access information of the target database includes parameterized business process data of the target database; and / or, The application access information of the target database includes the database interface data of the target database.

3. The method according to claim 2, characterized in that, The method further includes: In response to the instruction to start recording of front-end business in the target database, the business execution script is obtained; Based on the business execution script, obtain the business process parameterized data from the target database.

4. The method according to claim 2, characterized in that, The method further includes: Obtain the database access logs of the application gateway layer of the target database; Based on the database access logs of the application gateway layer, obtain the database interface data.

5. The method according to claim 4, characterized in that, The difference between the timestamp carried by the change information of the first table field and the timestamp carried by the description of the first business object is less than a preset difference.

6. The method according to claim 2, characterized in that, The application access information based on the target database determines multiple business object descriptions, including: Based on the business process parameterization data in the target database, determine the description of the first type of business object; Based on the database interface data of the target database, determine the description of the second type of business object; Based on the first type of business object description and the second type of business object description, multiple business object descriptions are determined.

7. A method for determining data mapping relationships, characterized in that, The method includes: Obtain the mapping relationship between business object descriptions and table fields in two databases; Based on the mapping relationship between the business object descriptions and table fields of the two databases, the mapping relationship between the business object descriptions and the mapping relationship between the table fields of the two databases are determined.

8. The method according to claim 7, characterized in that, The process of determining the mapping relationship between business object descriptions and table fields in the two databases, based on the mapping relationship between business object descriptions and table fields in the two databases, includes: Based on the business object descriptions of the two databases, determine the semantic association degree of the business objects in the two databases; If the semantic relevance of the business object is greater than or equal to the first preset relevance, it is determined that there is a mapping relationship between the business object descriptions of the two databases. Based on the object description mapping relationship between the two databases and the mapping relationship between the business object descriptions and table fields of the two databases, the table field mapping relationship of the two databases is determined.

9. The method according to claim 8, characterized in that, The step of determining the mapping relationship between the business object descriptions and table fields of the two databases based on the mapping relationship between the business object descriptions and table fields of the two databases also includes: If the semantic relevance of the business object is less than the first preset relevance, the semantic relevance of the table fields of the two databases is determined based on the table fields corresponding to the business objects of the two databases. If the semantic relevance of the table field is greater than or equal to the second preset relevance, it is determined that there is a mapping relationship between the table fields of the two databases; Based on the table fields in the two databases that have a mapping relationship, it is determined that there is a mapping relationship between the business objects in the two databases.

10. A computer device, characterized in that, include: processor; as well as, Stored program memory, The program includes instructions that, when executed by the processor, cause the processor to perform the method according to any one of claims 1 to 6 or 7 to 9.

Images