JPH05108452A - Data base management system - Google Patents

Abstract

PURPOSE:To provide a data base management system that transmits a lock request from a client computer to a server computer for the number of communication times, which is less than the number of lock request times, and that can shorten the response time of transaction. CONSTITUTION:In the client computer 2, a lock request accumulation part 22 is provided at a DBMS interface part 21 used in a business program 5 and it accumulates the lock requests and collectively transmits them to the server computer 3. It is composed of a request reception part 31, a retrieval/update control part 32, a lock control part 33 and a transaction control part 34. The client computer 2 and the server computer 3 are connected by a communication network 4, and the received lock requests are collectively processed.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a database management system for controlling database access.

[0002]

2. Description of the Related Art FIG. 2 shows a client / server model data.
The conceptual diagram of a tabular system is shown. A data base system can be mentioned as a data management system that systematically integrates a plurality of data files and eliminates duplication of data items. This database system is a database server that centrally manages data and a database that provides an interface for accessing the database to application programs. There is a function-distributed system consisting of clients.

Client server model database
In the server system 1, a plurality of client computers 2-1, 2-2, 2-3 and the server computer 3 are connected by a communication network 4 as shown in FIG. Client computer 2-
Data base clients (DB clients) 6-1, 6-2, 6-3 are provided for 1, 2-2, 2-3, etc., respectively.
Is provided for each of the business programs 5-1, 5-2,
A data base request from 5-3 etc. is accepted.

The server computer 3 is provided with a database server (DB server) 7 for processing retrieval and update requests to the database 8. The database is
It is composed of Tables 9-1 and 9-2. Further, the table is composed of rows 10 and the like.

Here, the database server 7 accesses the database 8 based on the access request from the business programs 5-1, 5-2, 5-3, etc., and further the business program. A series of processing operations for the database 8 until the access of the database 8 is completed based on the release request from the database will be referred to as a transaction.

The business programs 5-1, 5-2, 5-
When the third or the like accesses the row 10 of the table 9-1 which constitutes the database 8, these are made accessible and then accessed. This state will be called a table and row lock state.

When the database server 7 recognizes a lock request from a plurality of users for the same table or row, the database server 7 allows access unless the lock mode conflicts. In this way, the requests of the business programs can be correctly processed without mutual interference of the transactions.

FIG. 3 shows a conventional DB client 6 and DB.
The block diagram of the server 7 is shown. As shown in the figure, the DB client 6 is provided with a DBMS interface unit 21. The DB server 7 is provided with a request receiving unit 31, a search / update control unit 32, a lock control unit 33, and a transaction control unit 34.

The DBMS interface unit 21 accepts a database request from the business program 5 and receives a database service.
Send to BA 7. Further, the DBMS interface unit 21
The business program 5 receives the processing result from the DB server 7.
Respond with the processing result.

The request receiving unit 31 receives a request from a client, and according to the content of the request, a search / update control 32,
The transaction is passed to the lock control unit 33 transaction and the control unit 34. Each control unit that receives the request responds with the result after performing the process according to the request.

[0011]

However, in the conventional DB client 6, the DBMS interface unit 2 is used.
When 1 receives a lock request to the table 9 or the row 10 from the business program 5, the request is immediately sent to the DB server 7 via the communication network 4. Therefore, there are usually multiple tables that can be searched or updated in one transaction, so 1
In one transaction, a plurality of communications are required between the DB client 6 and the DB server 7 for a lock request. Therefore, there is a problem that communication takes time and the response time of one transaction is delayed.

The present invention has been made in view of the above points, and eliminates the above problems and shortens the transaction response time by sending a lock request from a client to a server with a communication count less than or equal to the lock request count. The purpose is to provide a database management method capable of doing so.

[0013]

In order to solve the above problems, the present invention provides a DB of a DB client 6 as shown in FIG.
A lock request accumulating unit 22 is provided in the MS interface unit 21, and means for accumulating the lock requests from the business programs and transmitting them to the DB server 7 in a lump.

[0014]

According to the present invention, since a plurality of lock requests are accumulated and the requests are sent to the server in a lump, the number of lock requests is one.
It can be sent in a single communication, and the response time of the transaction can be shortened.

[0015]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail below with reference to the drawings. FIG. 1 shows a client computer 2 according to the present invention.
A functional block diagram of the server computer 3 is shown. In the database management system of the present invention, lock requests successively issued by the business program 5 are stored in the lock request storage unit 22. When a request that is not a lock request is made, the accumulated lock requests are first sent to the DB server 7 in succession, and after this succeeds, the request from the business program is sent to D
Send to B server 7.

The present invention is based on the DB clients 6-1, 6-2, 6-3 of the database system 1 shown in FIG.
Etc. will be realized. Therefore, the same parts as those described above with reference to FIGS. 2 and 3 are designated by the same reference numerals, and the duplicate description will be omitted.

FIG. 1 shows a functional block diagram of a client computer and a server computer according to the present invention. As shown in the figure, the DB client unit 6 is provided with a DBMS interface 21 and a lock request accumulating unit 22.

FIG. 4 is a flowchart of the DBMS interface section according to the present invention. First, a request from the business program 5 is accepted (step ST1). It is determined whether this request is a lock request for Table 9-1, Table 9-2, etc. (step ST2).

If the request is a lock request, the request is stored in the lock request storage unit 22 (step ST9), and the acceptance of the request is returned to the business program 5 (step ST10).
And then finish.

If the request is a request other than the lock request in step ST2, it is determined whether the lock request is stored in the lock request storage unit (step ST3). If stored, the stored lock request is sent to the DB server 7 (step ST4), and the lock request stored in the lock request storage unit 22 is cleared (step ST5). The response from the DB server 7 is judged (step ST6), and if the lock is not permitted, the lock is returned to the business program 5 (step ST11). If the lock is permitted in step ST6, the control proceeds to step ST7.

When it is determined in step ST3 that the lock request is not stored in the lock request storage unit 22, the control proceeds to step ST7. The request from the business program 5 is sent to the DB server 7 (step ST7), and the result is returned to the business program 5 (step ST8).

[0022]

As described in detail above, according to the present invention, the following effects are expected. Since multiple lock requests are stored and sent to the server all at once,
The lock request can be sent in a single communication, and the transaction response time can be shortened. Result of performance test by debit credit bench mark, 3 records
When a request to add one record update 1 record is issued, the conventional method requires four locks, but the method of the present invention can be processed by one lock.

[Brief description of drawings]

FIG. 1 is a functional block diagram of a client computer and a server computer according to the present invention.

FIG. 2 is a conceptual diagram of a client server model database system.

FIG. 3 is a functional block diagram of a conventional client computer and server computer.

FIG. 4 is a control flow chart of a DBMS interface unit.
It is

[Explanation of symbols]

 1 Data Base System 2-1 Client Computer 2-2 Client Computer 2-3 Client Computer 4 Communication Network 5-1 Business Program 5-2 Business Program 5-3 Business Program 6-1 Data Base Client 6-2 Data Base Client 6-3 Data Base Client 7 Data Base Server 8 Data Base 9-1 Table 9-2 Table

Claims (1)

[Claims] 1. A function distribution consisting of a database server for centrally managing data and a database client for providing an interface for accessing the database to an application program. Type database system, when controlling parallel execution of multiple transactions by lock control, it accumulates consecutive lock requests, and when non-lock requests are issued, this request is issued. Prior to processing, the accumulated lock requests are collectively transmitted to the database server, and the number of transmissions is reduced by performing the lock processing, and the database management method is characterized. ..