WO2017041637A1 - Procédé et dispositif d'exploitation de base de données - Google Patents

Procédé et dispositif d'exploitation de base de données Download PDF

Info

Publication number
WO2017041637A1
WO2017041637A1 PCT/CN2016/097266 CN2016097266W WO2017041637A1 WO 2017041637 A1 WO2017041637 A1 WO 2017041637A1 CN 2016097266 W CN2016097266 W CN 2016097266W WO 2017041637 A1 WO2017041637 A1 WO 2017041637A1
Authority
WO
WIPO (PCT)
Prior art keywords
database
operation instruction
instruction
database operation
execution
Prior art date
Application number
PCT/CN2016/097266
Other languages
English (en)
Chinese (zh)
Inventor
王晶昱
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2017041637A1 publication Critical patent/WO2017041637A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23—Updating
    • G06F16/2308—Concurrency control
    • G06F16/2315—Optimistic concurrency control

Definitions

  • the present application relates to the field of database technologies, and in particular, to a database operation method and apparatus.
  • Database Transaction refers to a series of operations performed as a single logical unit of work, either completely or completely.
  • a transaction consists of a series of database operation instructions, such as Structured Query Language (SQL) statements. There are splitting conditions and jumps between these database operation instructions, meaning that the transaction is in one transaction. There may be some database operation instructions that are skipped and not executed.
  • SQL Structured Query Language
  • the execution judgment can only be performed according to the execution logic, and the statement in the transaction is sequentially executed to implement the operation on the database. This type of transaction execution is less efficient, especially when the transaction settings read committed isolation level is less efficient and has lower transaction throughput.
  • aspects of the present application provide a database operation method and apparatus for improving transaction execution efficiency and increasing transaction throughput.
  • An aspect of the present application provides a database operation method, including:
  • the operation instruction belongs to the prediction execution data generated by the prediction execution when the database type instruction is modified
  • the database corresponding to the application server is controlled to actually execute the target transaction according to the database operation instruction recorded locally and the predicted execution data.
  • a database operating device including:
  • An obtaining module configured to acquire the application service in sequence during execution of a target transaction by the application server a database operation instruction in the target transaction to which the device executes;
  • a predictive execution module configured to perform predictive execution on the database operation instruction, return a predicted execution result to the application server, for the application server to determine a next database operation instruction to be executed, and locally record the database operation And predicting execution data generated by the prediction execution when the database operation instruction belongs to modifying a database class instruction;
  • control execution module configured to: when the transaction commit instruction in the target transaction is obtained, control the database corresponding to the application server to actually execute the target transaction according to the database operation instruction recorded locally and the predicted execution data .
  • the database operating device cooperates with the application server to join the predictive execution process in the process of executing the target transaction by the application server, and obtains and records all the database operation instructions that need to be executed in the target transaction in advance, and only for the instructions belonging to the modified database class.
  • the database operation instruction records the predicted execution data generated by the prediction execution to adapt to the read committed isolation level, provides conditions for the real execution of the transaction, and then controls the database corresponding to the application server to actually execute the target according to the recorded database operation instruction and the predicted execution data. Transactions help improve execution efficiency and increase transaction throughput.
  • FIG. 1 is a deployment diagram of a database application system in the prior art
  • FIG. 2 is a deployment diagram of a database application system according to an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a database operation method according to an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a database operating device according to an embodiment of the present application.
  • FIG. 1 is a deployment diagram of a database application system in the prior art.
  • the system includes an application server 10 and a database 20.
  • the database 20 may be one or multiple. Only one database 20 is shown by way of example in FIG.
  • the application server 10 executes transaction logic to sequentially apply database operation instructions in the transaction to the database 20. Because the database operation instructions that need to be executed in the transaction cannot be known in advance, the transaction execution efficiency is low, especially when the configuration read commit isolation level is configured, the execution efficiency is lower and the transaction throughput is lower.
  • the present application provides a new database application system, as shown in FIG. 2 .
  • the system adds a database operating device 30 between the application server 10 and the database 20.
  • the database operating device 30 is configured to execute the database operation method provided by the present application, and implement a new transaction execution logic under the isolation level of the read commit, that is, the prediction execution is performed on the transaction, and the database operation to be performed in the transaction is obtained in advance.
  • the instruction, the prediction of the execution path is implemented, and the read execution level is submitted only for the database execution instruction record of the database operation instruction record belonging to the modified database class instruction, and the database operation instruction generated based on the prediction execution is executed.
  • predicting execution data actually executing transactions on the database 20 which is beneficial to improve transaction execution efficiency and increase transaction throughput.
  • Transaction throughput is the number of transactions processed per unit of time.
  • the database operating device 30 is actually a logical processing device, which can be deployed separately, between the application server 10 and the database 20, or deployed at one end of the application server 10, or can be deployed in the database 20. Implemented at one end.
  • FIG. 3 is a schematic flowchart diagram of a database operation method according to an embodiment of the present application. As shown in FIG. 3, the method includes:
  • the present embodiment refers to a transaction that the application server needs to perform as a target transaction.
  • the target transaction mainly includes operation instructions for operating on the database, and in addition to the database operation instructions, some control instructions for controlling the execution state of the target transaction, such as a transaction start instruction, a transaction commit instruction, a transaction rollback instruction, and the like.
  • These instructions are actually statements written in the database language. Depending on the database language, these instructions can be statements written in different languages. For example, if SQL is used, the above database operation instructions and control instructions are actually a series of SQL statements.
  • the method provided in this embodiment is applicable to operating a database whose isolation level is read and submitted.
  • Some databases default to reading the isolation level that has been submitted.
  • the Oracle database defaults to read the isolation level that has been submitted.
  • Some databases do not read the isolation level by default.
  • the MySQL database is repeatable by default.
  • An isolation level Based on this, before performing the method provided in this embodiment, it can be determined whether the isolation level of the database is a read commit, and if not, the database needs to be pre-configured to read the isolation level. For example, you can configure the database to read this isolation level before the target server performs the target transaction.
  • the method provided in this embodiment can be executed to execute the target transaction in the database.
  • the specific process is as follows:
  • the application server controls the execution logic of the entire target transaction, and the target transaction can be executed in the existing manner.
  • the database operating device sequentially acquires database operation instructions in the target transaction executed by the application server during the execution of the target transaction by the application server.
  • the application server sends database operation instructions to the database in an existing manner to enable access to the database.
  • the database operating device can monitor the communication between the application server and the database to intercept the database operation instructions sent by the application server to the database.
  • the processing logic of the application server is slightly modified to change the processing logic that originally sent the database operation instructions to the database to the database operating device. Based on this, the database operating device can receive the database operation instruction actively issued by the application server.
  • the first instruction in the target transaction is a transaction start instruction, such as a begin transaction, based on which the database operation device obtains the database operation instruction executed by the application server.
  • the database operating device may receive a transaction start instruction in the target transaction actively issued by the application server before acquiring the database operation instruction executed by the application server, and according to the transaction start instruction, learn that the target transaction needs to be executed.
  • the first instruction of the target transaction is the database operation instruction, and does not include the step of obtaining the transaction start instruction.
  • the database operation device After acquiring the database operation instruction executed by the application server, the database operation device performs predictive execution on the acquired database operation instruction, returns the predicted execution result to the application server, and uses the server to determine the next database operation instruction to be executed.
  • the predicted execution result determines the execution path of the target transaction, where the execution path refers to the jump logic between the database operation instructions.
  • the purpose of controlling the execution logic of the entire target transaction by the application server is achieved by returning the predicted execution result to the application server.
  • the database operating device also needs to locally record the acquired database operation instruction, and record the predicted execution data generated by predictive execution of the database operation instruction when the database operation instruction belongs to the modified database type instruction.
  • the modified database class instruction refers to a database operation instruction that has a modification to the database, for example, an instruction starting with update, insert, etc.; generally, the instruction beginning with select is not a modified database type instruction.
  • the predicted execution data mainly refers to some data in the process of predictive execution of database operation instructions.
  • the database operating device can locally create a memory library, and store the acquired database operation instructions and predicted execution data into the memory library. Further, if the predicted execution data does not include the predicted execution result, the predicted execution result may also be stored in the memory bank.
  • reading the committed isolation level only guarantees that writing multiple data is atomic, and does not lock when reading, which can improve the concurrency of the system and improve the efficiency of transaction execution.
  • this embodiment only records the prediction execution data generated by the prediction execution for the database operation instruction belonging to the modified database class instruction, but does not Record the predicted execution data corresponding to the database operation instruction that does not modify the database class instruction. It can be seen that in the case that the reading has been submitted to the isolation level, the amount of recorded data is relatively small, so that in the subsequent process of executing the target transaction in the database in the database operation instruction and the prediction execution data based on the local record. The amount of data to be processed is relatively small, which is beneficial to further improve execution efficiency and performance, and increase transaction throughput.
  • the operation of the database operation instruction on the database is mainly to access the data in the database, then the data environment of the database operation instruction can be simulated, and the database operation instruction is predicted and executed based on the simulated data environment. Further, considering that the database operation instruction that is not a modification of the database class instruction does not cause a change of the database, the database operation instruction can be directly predicted and executed in the database, which can save the operation of the simulation data environment, and is relatively simple to implement. Conducive to saving resources and improving execution efficiency. However, For database operation instructions belonging to the modified database class instructions, since it will cause changes in the database (mainly refers to the data in the database is changed), it is necessary to simulate the data environment and perform prediction execution in the simulated data environment.
  • the data environment of the database operation instruction is simulated in the locally created memory library, and the database operation instruction is predicted and executed based on the simulated data environment;
  • the database operation instruction is executed in the database to perform prediction execution on the database operation instruction.
  • a data environment simulating a database operation instruction in a locally created memory library, and an implementation manner of predicting execution of the database operation instruction based on the simulated data environment includes:
  • the obtained database operation instruction is split into a read instruction and a write instruction, and the read instruction is run on a real database, that is, the read instruction is executed in the database to obtain a read data set (ReadSet), and the read data set is stored.
  • the read instruction is executed in the database to obtain a read data set (ReadSet), and the read data set is stored.
  • the write instruction is applied to the memory library to implement predictive execution of the database operation instruction, that is, the write instruction is executed in the memory library to modify the read data set, for example, to update or query the related data in the read data set.
  • executing a write instruction to modify the read data set may generate a result data set (affectRowInMemdb), the result data set including a predicted execution result.
  • the database operation device may locally record the read data set read by the read instruction and the result data set generated by executing the write instruction.
  • the predicted execution data may include a read data set and a result data set, or may also include partial data in the read data set and the result data set, such as some data that can have a beneficial effect on actually executing the target transaction in the database. For example, various indexes of some values, such as a primary index, a secondary index, a primary key value, and the like.
  • the database operation device acquires the transaction commit instruction in the target transaction (that is, the application server executes to the transaction commit instruction)
  • the database corresponding to the locally recorded database operation instruction and the predicted execution data may be used to control the database corresponding to the application server to actually execute the target transaction.
  • an optional implementation manner of controlling the database corresponding to the actual execution target transaction of the application server includes:
  • the database operating device sends the locally recorded database operation instruction to the database to indicate the database Executing a database operation instruction, and receiving an actual execution result of the database operation instruction returned by the database; then, comparing the actual execution result of the database operation instruction with the predicted execution result, and if the actual execution result is the same as the predicted execution result, sending a transaction to the database
  • the instruction is submitted for the database to submit the target transaction; if the actual execution result is different from the predicted execution result, a transaction rollback instruction is sent to the database for the database to roll back the target transaction.
  • the database operation instruction can be executed sequentially according to the execution logic of the transaction, which causes frequent interaction between the application server and the database, which is A lot of network resources will be consumed in the remote application scenario.
  • all the database operation instructions that need to be executed by the target transaction that is, the database operation instructions of the local record
  • the database operation instruction of the local record has been obtained in advance by the prediction execution process, so the database operation instruction of the local record is sent to the database to instruct the database to execute the database.
  • the database operation instruction of the local record can be simultaneously and/or sent to the database, which is conducive to saving network resources.
  • the database can also operate in parallel, which is beneficial to further improve transaction execution efficiency and increase transaction throughput.
  • all the database operation instructions of the local record can be sent to the database together with the locally recorded predicted execution data.
  • the database operation device may determine whether the target transaction is based on the locally recorded database operation instruction. For a stand-alone transaction; if the result of the determination is yes, according to the locally recorded database operation instruction and the predicted execution data, the single-machine transaction logic is used to control the database to actually execute the target transaction; if the judgment result is no, the database operation instruction according to the local record and Predictive execution data, with distributed transaction processing logic to control the database to actually execute the target transaction.
  • the database operation instruction obtained during the prediction execution process can identify whether the target transaction is a stand-alone transaction or a distributed transaction. For example, it can be determined whether the operation object of the database operation instruction recorded locally acts on the same physical device. If the determination result is yes, the target transaction can be determined to be a stand-alone transaction; if the determination result is no, the target transaction can be determined as Distributed transactions.
  • the processing logic of distributed transactions is different from the processing logic of stand-alone transactions, the processing logic of single-machine transactions is relatively simple, for example, it does not involve problems such as read-write and lock, so the resources consumed are relatively small. based on Therefore, in this embodiment, by identifying whether the target transaction is a stand-alone transaction, the processing logic of the single-machine transaction is processed when it is recognized as a stand-alone transaction, instead of uniformly processing the distributed transaction processing logic as in the prior art, which is advantageous for improving processing. Efficiency, saving processing costs.
  • the database operation device acquires a transaction rollback instruction in the target transaction (that is, the application server performs a transaction rollback instruction)
  • the database operation instruction of the local record and the prediction execution data may be deleted, for example, Clear the local memory library directly to implement the rollback operation.
  • the target transaction since the target transaction is not actually executed in the database, the database does not need to perform a rollback operation. It can be seen that in the case of transaction rollback, the transaction efficiency can be improved by using the method of this embodiment.
  • the database operating device cooperates with the application server to join the predictive execution process in the process of executing the target transaction by the application server, and the execution path of the target transaction can be obtained in advance during the predictive execution process. That is, the database operation instruction that really needs to be executed, and only the prediction execution data generated by the prediction execution of the database operation instruction belonging to the modified database class instruction is adapted to read the submitted isolation level, and the condition for the real execution transaction is provided, and then the record is based on the record.
  • the database operation instruction and the prediction execution data actually execute the target transaction, for example, based on the prediction execution data, related data information can be acquired in advance and jumps between instructions can be reduced, etc., thereby improving execution efficiency and increasing transaction throughput.
  • the isolation level of the database is the isolation level that the read has been submitted.
  • the SQL code for the inventory reduction transaction is as follows, the text in parentheses is a comment:
  • the application server is responsible for the entire logic of the inventory reduction transaction, and the database operation device (or may also be referred to as an execution server) only obtains the start transaction executed by the application server, and needs to be executed. SQL statements, as well as commit/rollback instructions.
  • the database operating device creates a memory library locally
  • the database operation device will get the rollback statement.
  • the application server executes the commit command at this time.
  • the inventory reduction transaction is executed in the database based on the SQL statement in the local memory library and the predicted execution data, and the transaction execution process is actually performed.
  • the locally recorded SQL statement and the predicted execution data are as follows:
  • the database operating device can submit all the SQL statements in the local memory library to the database at one time, and the database performs the execution based on this, which is beneficial to save network resources consumed by the transmission of the SQL statement.
  • This real execution will also return the execution result.
  • FIG. 4 is a schematic structural diagram of a database operating device according to an embodiment of the present application. As shown in FIG. 4, the apparatus includes an acquisition module 41, a prediction execution module 42, and a control execution module 43.
  • the obtaining module 41 is configured to sequentially acquire a database operation instruction in the target transaction executed by the application server during the execution of the target transaction by the application server.
  • the prediction execution module 42 is configured to perform predictive execution on the database operation instruction, return the predicted execution result to the application server to supply the server to determine the next database operation instruction to be executed, and locally record the database operation instruction and the database operation instruction belongs to The predicted execution data generated by the prediction execution is recorded when the database class instruction is modified.
  • the control execution module 43 is configured to, when acquiring the transaction commit instruction in the target transaction, control the database corresponding to the application server to actually execute the target transaction according to the locally recorded database operation instruction and the predicted execution data.
  • the database operating device further includes: a configuration module, configured to configure the database to read the submitted isolation level before the application server performs the target transaction.
  • the obtaining module 41 is specifically configured to: intercept a database operation instruction sent by the application server to the database; or receive a database operation instruction that is actively sent by the application server.
  • the obtaining module 41 is further configured to: before acquiring the database operation instruction in the target transaction executed by the application server, intercepting a transaction start instruction in the target transaction sent by the application server to the database; or receiving the application The transaction start instruction in the target transaction that the server actively delivers.
  • the prediction execution module 42 is specifically configured to:
  • the database operation instruction acquired by the obtaining module 41 belongs to the modified database class instruction, the data environment of the database operation instruction is simulated in the locally created memory library, and the database operation instruction is predicted and executed based on the simulated data environment;
  • the database operation instruction acquired by the obtaining module 41 does not belong to the modified database class instruction, the database operation instruction is executed in the database to perform prediction execution on the database operation instruction.
  • the prediction execution module 42 simulates the data environment of the database operation instruction in the locally created memory library, and operates the database based on the simulated data environment.
  • the instruction performs the operation of predictive execution it is specifically used to:
  • a write instruction is executed in the memory bank to modify the read data set.
  • control execution module 43 is specifically configured to:
  • the database operation instruction of the local record is sent to the database to instruct the database to execute the database operation instruction, and receives the actual execution result of the database operation instruction returned by the database;
  • the transaction commit instruction is sent to the database for the database to submit the target transaction
  • control execution module 43 can avoid the error of the transaction execution process by comparing the actual execution result with the predicted execution result, and is beneficial to improving the success probability of the transaction execution.
  • control execution module 43 can be used to: simultaneously send the database operation instruction of the local record to the database, which is beneficial to save network resources.
  • control execution module 43 can send all the database operation instructions recorded locally together with the locally recorded predicted execution data to the database, which is beneficial to save network resources.
  • control execution module 43 is specifically configured to:
  • the single-machine transaction logic is used to control the database to actually execute the target transaction
  • the database actually controls the target transaction by the distributed transaction logic according to the locally recorded database operation instruction and the predicted execution data. Because the processing logic of distributed transactions is different from the processing logic of stand-alone transactions, the processing logic of single-machine transactions is relatively simple, for example, it does not involve problems such as read-write and lock, so the resources consumed are relatively small. Based on this, the control execution module 43 performs processing by using the processing logic of the single-machine transaction when identifying the target transaction as a stand-alone transaction, which is beneficial to improve processing efficiency and save processing cost.
  • the predictive execution module 42 is further configured to: delete the locally recorded database operation instruction and the predicted execution data when the transaction rollback instruction in the target transaction is acquired.
  • the database operating device provided in this embodiment may be deployed separately, and may be located between the application server and the database, or may be deployed on one end of the application server, or may be deployed on one end of the database.
  • the database operating device cooperates with the application server to join the predictive execution process in the process of executing the target transaction by the application server, and obtains and records all the data that the target transaction needs to execute in advance.
  • the library operates on instructions and records the predicted execution data generated by the prediction execution only for the database operation instructions belonging to the modified database class instruction to adapt to the read committed isolation level, providing conditions for the real execution of the transaction, and then based on the recorded database operation instructions and predictions. Executing data and controlling the database corresponding to the application server to actually execute the target transaction is beneficial to improve execution efficiency and increase transaction throughput.
  • the disclosed system, apparatus, and method may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.
  • the above-described integrated unit implemented in the form of a software functional unit can be stored in a computer readable storage medium.
  • the software functional unit described above is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to perform the methods described in various embodiments of the present application. Part of the steps.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'invention concerne un procédé et un dispositif d'exploitation de base de données. Le procédé consiste à : dans un processus d'exécution d'une transaction cible d'un serveur d'application, acquérir des instructions d'exploitation de base de données séquentiellement dans la transaction cible exécutée par le serveur d'application (301) ; réaliser une exécution spéculative des instructions d'exploitation de base de données et renvoyer le résultat de l'exécution spéculative au serveur d'application pour que le serveur d'application détermine une instruction d'exploitation de base de données suivante à exécuter, et enregistrer localement l'instruction d'exploitation de base de données et, si l'instruction d'exploitation de base de données appartient à un type de modification d'instructions de base de données, enregistrer des données d'exécution spéculative générées par l'exécution spéculative (302) ; et lorsqu'une instruction d'engagement de transaction dans la transaction cible est acquise, commander une base de données correspondant au serveur d'application pour exécuter réellement la transaction cible selon l'instruction d'exploitation de base de données enregistrée localement et les données d'exécution spéculative (303).
PCT/CN2016/097266 2015-09-08 2016-08-30 Procédé et dispositif d'exploitation de base de données WO2017041637A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510568369.7 2015-09-08
CN201510568369.7A CN106503027B (zh) 2015-09-08 2015-09-08 数据库操作方法及装置

Publications (1)

Publication Number Publication Date
WO2017041637A1 true WO2017041637A1 (fr) 2017-03-16

Family

ID=58240569

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/097266 WO2017041637A1 (fr) 2015-09-08 2016-08-30 Procédé et dispositif d'exploitation de base de données

Country Status (2)

Country Link
CN (1) CN106503027B (fr)
WO (1) WO2017041637A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111930830A (zh) * 2020-06-22 2020-11-13 心有灵犀科技股份有限公司 一种基于共享数据库的分布式事务数据处理方法及系统

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111198872B (zh) * 2020-01-06 2021-06-11 中科驭数（北京）科技有限公司 数据库处理事务的方法及装置
CN111580938B (zh) * 2020-03-27 2023-04-14 浪潮通用软件有限公司 一种工作单元的事务处理方法、装置、设备及介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090187534A1 (en) * 2008-01-21 2009-07-23 International Business Machines Corporation Transaction prediction modeling method
CN101587447A (zh) * 2008-05-23 2009-11-25 国际商业机器公司 支持事务存储的系统及基于预测的事务执行方法
CN102203779A (zh) * 2011-05-03 2011-09-28 华为技术有限公司 更新数据的方法和控制装置
US20140214880A1 (en) * 2013-01-29 2014-07-31 Nec Laboratories America, Inc. System and methods for Predicting Query Execution Time for Concurrent and Dynamic Database Workloads

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB0318196D0 (en) * 2003-08-02 2003-09-03 Ibm A method apparatus and computer program for processing a queue of messages
CN106503007B (zh) * 2015-09-08 2019-07-23 阿里巴巴集团控股有限公司 数据库操作方法及装置
CN106897306B (zh) * 2015-12-21 2019-04-30 阿里巴巴集团控股有限公司 数据库操作方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090187534A1 (en) * 2008-01-21 2009-07-23 International Business Machines Corporation Transaction prediction modeling method
CN101587447A (zh) * 2008-05-23 2009-11-25 国际商业机器公司 支持事务存储的系统及基于预测的事务执行方法
CN102203779A (zh) * 2011-05-03 2011-09-28 华为技术有限公司 更新数据的方法和控制装置
US20140214880A1 (en) * 2013-01-29 2014-07-31 Nec Laboratories America, Inc. System and methods for Predicting Query Execution Time for Concurrent and Dynamic Database Workloads

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111930830A (zh) * 2020-06-22 2020-11-13 心有灵犀科技股份有限公司 一种基于共享数据库的分布式事务数据处理方法及系统

Also Published As

Publication number Publication date
CN106503027A (zh) 2017-03-15
CN106503027B (zh) 2020-02-21

Similar Documents

Publication Publication Date Title
WO2017041639A1 (fr) Procédé et dispositif de fonctionnement de base de données
WO2017107811A1 (fr) Procédé et dispositif d'exploitation de base de données
EP3446242B1 (fr) Génération et exécution de plan de requête dans un système de gestion de base de données relationnelle à l'aide d'une base de données relationnelle temporelle
US10649995B2 (en) Methods and systems for optimizing queries in a multi-tenant store
CN106897123B (zh) 数据库操作方法及装置
US9256643B2 (en) Technique for factoring uncertainty into cost-based query optimization
TWI774643B (zh) 資料庫操作方法及裝置
WO2017041637A1 (fr) Procédé et dispositif d'exploitation de base de données
KR102244887B1 (ko) Sql 쿼리 추천 방법 및 시스템
TWI725110B (zh) 資料庫操作方法及裝置
TWI805544B (zh) 資料庫操作方法及裝置
US10929395B2 (en) Data modification in hypothetical planning
TWI735512B (zh) 資料庫操作方法及裝置
US11521089B2 (en) In-database predictive pipeline incremental engine
US20160004747A1 (en) Join query execution method and device, and storage medium
TW201828116A (zh) 資料庫操作方法及裝置
CN112970011A (zh) 记录查询优化中的谱系
CN116226092A (zh) 数据库更新方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16843575

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16843575

Country of ref document: EP

Kind code of ref document: A1