Workload balancing in a distributed database

A method for transaction processing in a distributed database management system comprising two or more query processors with a common data source and at least one database client for managing a transaction including two or more queries, said method comprising:

• checking if a transaction can be processed by more than one query processor, wherein a tag indicating that the transaction is distributable is associated with the transaction, and a tag indicating that the transaction is a long running or a short running transaction is associated with the transaction;
• locating the optimum query processor for each query in the transaction based on workload of each query processor;
• directing each query to the new optimum query processor if the transaction can be processed by more than one query processor;
• and
• locking portions of the common data source, via a locking mechanism, at a query level to a new query processor, wherein the lock mechanism can be transferred to the new query processor when a transaction is transferred to a new query processor and using existing global lock and cache data, and the transaction is transferred as a whole.

A computer program product for transaction processing in a distributed database management system, the computer program product comprising a computer-readable storage medium having computer-readable program code embodied therewith, the computer-readable program code configured to perform:

• checking if a transaction can be processed by more than one query processor, wherein a tag indicating that the transaction is distributable is associated with the transaction, and a tag indicating that the transaction is a long running or a short running transaction is associated with the transaction;
• locating the optimum query processor for each query in the transaction based on workload of each query processor;
• directing each query to the new optimum query processor if the transaction can be processed by more than one query processor;
• and
• locking portions of the common data source, via a locking mechanism, at a query level to a new query processor, wherein the lock mechanism can be transferred to the new query processor when a transaction is transferred to a new query processor and using existing global lock and cache data, and the transaction is transferred as a whole.