JP2013149173A - Query conversion device, database server, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To cause a plurality of systems corresponding to different table layouts to read/write data with respect to a common database.SOLUTION: A communication unit 101 communicates with a plurality of terminal devices (systems) via a network 30. A storage unit 102 stores a conversion definition file 1022 in which a conversion content for converting a query issued from a terminal device into a query accommodating to specifications of a commodity management DB 1021 is defined for every system. When receiving the query issued from the terminal device, the query conversion unit 1031 acquires a conversion content corresponding to the system from the conversion definition file 1022 and converts the received query on the basis of the acquired conversion content. The query conversion unit 1031 supplies a DBMS (DataBase Management System) processing unit 1032 with the query after the conversion.

Description

  The present invention relates to a query conversion device, a database server, and a program for converting a query issued from a system so as to correspond to a specific database.

  For example, in a basic business system of a company or the like, there are many cases in which the table layout of a database shared by a plurality of systems is inevitably changed due to introduction of a new system or expansion of management information. In this case, if the system has a very large change load to accommodate the new layout, such as a large amount of program modifications, and the benefits of the new layout are not so great, the system can be used with the old layout specifications. Is a good idea. Accordingly, there are many cases in companies and the like that take such a measure that such a system continues to access the database of the old layout instead of the database of the new layout.

  As in the above case, the contents of the data are the same, but when using multiple databases with different layouts in combination, work such as synchronization in batch processing is required to maintain data consistency. is there. Therefore, there is a problem that it is difficult to reflect information between systems in real time, and that the risk of inconsistency cannot be said to be low.

  On the other hand, for example, Patent Document 1 proposes a data storage device that converts a data file from a legacy system according to the specifications of an integrated database and then stores the data file in the database.

JP 2001-297017 A

  However, the above Patent Document 1 does not mention at all how a legacy system acquires data from the above integrated database. Therefore, the technique described in Patent Document 1 is not an effective solution to the conventional problem.

  The present invention has been made in view of such circumstances, and provides a query conversion device and the like that enable a plurality of systems corresponding to different table layouts to read and write data to a common database. The purpose is to do.

In order to achieve the above object, a query conversion apparatus according to the present invention provides:
A communication unit that communicates with a plurality of systems via a predetermined network;
A storage unit for storing a conversion definition file in which conversion contents for converting a query issued from the system into a query that can correspond to a specific database specification are defined for each system;
When a query issued from the system is received, the conversion content corresponding to the system is acquired from the conversion definition file stored in the storage unit, and the received query is converted based on the acquired conversion content And a query conversion unit that supplies the converted query to a database management system corresponding to the specific database.

  According to the present invention, a plurality of systems corresponding to different table layouts can read / write data from / to a common database.

It is a figure showing the whole information management system composition provided with DB server concerning an embodiment of the present invention. It is a block diagram which shows the structure of DB server of this embodiment. It is a figure which shows the structure of merchandise information. It is FIG. (1) for demonstrating the conventional information management system. It is FIG. (2) for demonstrating the conventional information management system. It is a figure for demonstrating the function of a query conversion part. It is a figure which shows an example of the conversion content defined in the conversion definition file. It is a flowchart which shows the procedure of a query conversion process. It is a figure for demonstrating other embodiment (the 1) of this invention. It is a figure which shows an example of the conversion content defined by the conversion definition file in other embodiment (the 1) of this invention. It is FIG. (The 1) for demonstrating other embodiment (the 2) of this invention. It is FIG. (2) for demonstrating other embodiment (the 2) of this invention. It is a figure which shows an example of the conversion content defined by the conversion definition file in other embodiment (the 2) of this invention.

  Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a diagram illustrating an overall configuration of an information management system 1 including a DB server 10 according to the present embodiment. The information management system 1 is a system for managing some common information (for example, product information) in a basic business system such as a company. The information management system 1 includes a DB (database) server 10 and a plurality of terminal devices 20. The DB server 10 and each terminal device 20 are connected to a predetermined network 30 such as an intranet, for example, and are configured to be able to transmit / receive data to / from each other.

  Each terminal device 20 is an information processing device used in each of a plurality of business systems (for example, a production management system, a sales management system, an inventory management system, etc.) that constitute the core business system. Each terminal device 20 has a hardware configuration equivalent to that of a general personal computer.

  As shown in FIG. 2, the DB server 10 includes a communication unit 101, a storage unit 102, and a control unit 103. Each unit is connected to each other via a bus 104. The communication unit 101 includes a communication interface such as a network card, and communicates with each terminal device 20 according to a predetermined communication method via the network 30 under the control of the control unit 103.

  The storage unit 102 is configured by a readable / writable nonvolatile semiconductor memory such as a hard disk drive (HDD) or a flash memory, for example. A product management DB 1021 is constructed in the storage unit 102. The product management DB 1021 is a database in which information (product information) about products handled by the company or the like is registered. In this embodiment, the product information includes items such as a product ID, a product name, a release date, remarks 1 and 2 as shown in FIG.

  In addition, the storage unit 102 stores a conversion definition file 1022. The conversion definition file 1022 is a data file in which contents for converting a query issued from the terminal device 20 of each system constituting the core business system so as to be compatible with the specifications of the product management DB 1021 are defined. is there. Here, the specification of the product management DB 1021 mainly means a table layout specification (for example, data type of each item). In addition to the above, the storage unit 102 stores various data, programs, and the like.

  The control unit 103 includes a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), and the like, and controls the communication unit 101 and the storage unit 102 via the bus 104.

  Functionally, the control unit 103 includes a query conversion unit 1031 and a DBMS processing unit 1032. The query conversion unit 1031 is a function realized by the CPU executing a query conversion program stored in the ROM or the storage unit 102. The DBMS processing unit 1032 is a function realized by the CPU executing a program for DBMS stored in the ROM or the storage unit 102.

  When the query conversion unit 1031 receives a query issued (transmitted) from the terminal device 20 of each system, the query conversion unit 1031 refers to the conversion definition file 1022 and converts it into a query according to the specifications of the product management DB 1021. Then, the query conversion unit 1031 supplies the converted query to the DBMS processing unit 1032.

  The DBMS processing unit 1032 plays a role as a DBMS (DataBase Management System) for managing and operating the product management DB 1021. The function of the DBMS processing unit 1032 is the same as the function in the well-known DBMS. The DBMS processing unit 1032 accesses the product management DB 1021 and performs data reading or writing processing based on the query supplied from the query conversion unit 1031. Then, the DBMS processing unit 1032 notifies the query conversion unit 1031 of the processing result. The query conversion unit 1031 transmits the notification content from the DBMS processing unit 1032 to the issuing terminal device 20 (that is, the system) as response data for the issued query.

  Here, in the conventional information management system of this type, a case where a system that accesses an old specification database and a system that accesses a new specification database coexist will be described. In FIG. 4, the product management DB 1021A indicates a database including the old specification table A, and the product management DB 1021B indicates a database including the new specification table B. In this description, in order to facilitate understanding, in the tables A and B, only some of the items of the product information (product ID, release date) are shown.

  In this example, it is shown that the data type of the product ID and the release date is a character string type in the table A of the old specification, and the data type of the product ID and the release date is shown in the table B of the new specification. , Respectively, are numerical and date types.

  In the above case, for example, a query as shown in FIG. 5 is issued from each terminal device of the legacy system that continuously accesses the product management DB 1021A and the system corresponding to the new specification that accesses the product management DB 1021B. The

  As described above, when old and new databases (product management DB 1021A and product management DB 1021B) having the same data contents but different layouts are used in parallel, batches are used to maintain data consistency in both databases. It is necessary to synchronize the product management DB 1021A and the product management DB 1021B by processing or the like.

  On the other hand, in the information management system 1 of this embodiment, as shown in FIG. 6, the query from the terminal device 20A of the system A corresponds to the specification of the product management DB 1021B by the query conversion unit 1031. Converted. In this case, the conversion contents of the system A described in the conversion definition file 1022 are shown in FIG.

  By automatically converting the query by the query conversion unit 1031, the system A can continue processing with the layout specification of the table A, and the reading and writing of data are shared by the new product management DB 1021B. can do.

  Note that the query conversion unit 1031 supplies the query to the DBMS processing unit 1032 as it is because there is no need to convert the query from the terminal device 20B of the system B corresponding to the new specification. For example, the conversion definition file 1022 includes information indicating that the system B is a system compatible with the new specification, and the query conversion unit 1031 determines whether the system B supports the new specification based on the information. May be determined. Alternatively, whether or not the system B supports the new specification may be determined based on whether or not the conversion content for the system B is defined in the conversion definition file 1022.

  FIG. 8 is a flowchart illustrating a procedure of query conversion processing executed by the query conversion unit 1031. When the query conversion unit 1031 receives a query issued from the terminal device 20 of any system (step S101; YES), the query conversion unit 1031 refers to the conversion definition file 1022 to determine whether the query needs to be converted. (Step S102).

  As a result, when it is determined that query conversion is necessary (step S102; YES), the query conversion unit 1031 converts the query based on the conversion content for the issuing system defined in the conversion definition file 1022. That is, the contents of the query are changed so as to correspond to the specifications of the product management DB 1021 (step S103). The query conversion unit 1031 supplies the converted query to the DBMS processing unit 1032 (step S104). On the other hand, if it is determined that query conversion is not necessary (step S102; NO), the query conversion unit 1031 supplies the received query as it is to the DBMS processing unit 1032 (step S105).

  When the DBMS processing unit 1032 receives the supply of the query from the query conversion unit 1031, the DBMS processing unit 1032 accesses the product management DB 1021 and performs data reading or writing processing based on the content of the query. Then, the DBMS processing unit 1032 notifies the query conversion unit 1031 of the processing result. When receiving the processing result notification from the DBMS processing unit 1032 (step S106; YES), the query conversion unit 1031 generates response data based on the processing result notification (step S107). Such response data includes information indicating whether the reading or writing has been normally completed, and also includes the read data when the reading has been normally completed.

  The query conversion unit 1031 transmits the generated response data to the terminal device 20 of the system that issued the query (step S108). Then, the process of the query conversion unit 1031 returns to step S101, and the series of processes described above are repeatedly executed.

  As described above, the DB server 10 according to the present embodiment holds the conversion definition file 1022 in which the conversion contents of the query are defined for each system so as to be compatible with the specifications of the product management DB 1021. Then, the query conversion unit 1031 of the DB server 10 changes the content of the query issued from the system based on the conversion content defined in the conversion definition file 1022. Therefore, for example, a system where it is better to perform processing with the old layout specification can continue processing with the old specification. In addition, since it is not necessary to use the old-specification database and the new-specification database in parallel, there is no need for synchronization work for maintaining data consistency.

  In addition, this invention is not limited to the said embodiment, Of course, the various change in the range which does not deviate from the summary of this invention is possible.

  For example, as shown in FIG. 9, the commodity management DB 1021 which is a common database is configured to include a main table C1 and an auxiliary table C2, and processing is performed with a layout (table C) different from the layout of the main table C1. The system C may be supported. In the case of FIG. 9, the conversion contents of the system C described in the conversion definition file 1022 are shown in FIG.

  In this case, for example, even when the layout size of the table actually held in the database is smaller than the table required by the newly added system or the like (the number of items is insufficient, the number of digits is small). Therefore, it is possible to cope without rebuilding the database.

  Further, as shown in FIGS. 11 and 12, the commodity management DB 1021, which is a common database, is configured to include a read-only main table D1 and a readable / writable auxiliary table D2, and internally, data deletion and It may be possible to cope with the system D that performs processing using the table D that can also perform writing. In the cases of FIGS. 11 and 12, the conversion contents of the system C described in the conversion definition file 1022 are shown in FIG.

  In this way, it is possible to appropriately perform writing while maintaining high-speed reading.

  Alternatively, the query conversion function may be separated from the DB server 10 and the function may be performed by another device (query conversion device).

  In addition, by applying the query conversion program executed by the DB server 10 of the above embodiment to an existing personal computer, database server, or the like, it is possible to cause these to function as a query conversion device or a database server according to the present invention. is there.

  Such a program distribution method is arbitrary, for example, a computer-readable recording medium such as a CD-ROM (Compact Disk Read-Only Memory), a DVD (Digital Versatile Disk), an MO (Magneto Optical Disk), or a memory card. It may be stored and distributed in a network, or distributed via a communication network such as the Internet.

  Various embodiments and modifications can be made to the present invention without departing from the broad spirit and scope of the present invention. Further, the above-described embodiment is for explaining the present invention, and does not limit the scope of the present invention. That is, the scope of the present invention is shown not by the embodiments but by the claims. Various modifications within the scope of the claims and within the scope of the equivalent invention are considered to be within the scope of the present invention.

1 Information Management System 10 DB Server 20 Terminal Device 30 Network 101 Communication Unit 102 Storage Unit 103 Control Unit 104 Bus 1021 Product Management DB
1022 Conversion definition file 1031 Query conversion unit 1032 DBMS processing unit

Claims (3)

A communication unit that communicates with a plurality of systems via a predetermined network;
A storage unit for storing a conversion definition file in which conversion contents for converting a query issued from the system into a query that can correspond to a specific database specification are defined for each system;
When a query issued from the system is received, the conversion content corresponding to the system is acquired from the conversion definition file stored in the storage unit, and the received query is converted based on the acquired conversion content And a query conversion unit that supplies the converted query to a database management system corresponding to the specific database,
A query conversion apparatus characterized by that. A communication unit that communicates with a plurality of systems via a predetermined network;
A database,
A database management system corresponding to the database;
A storage unit for storing a conversion definition file in which conversion contents for converting a query issued from the system into a query that can correspond to the specifications of the database are defined for each system;
When a query issued from the system is received, the conversion content corresponding to the system is acquired from the conversion definition file stored in the storage unit, and the received query is converted based on the acquired conversion content And a query conversion unit that supplies the converted query to the database management system,
A database server characterized by that. A communication unit that communicates with a plurality of systems via a predetermined network;
A storage unit that stores a conversion definition file in which conversion contents for converting a query issued from the system into a query that can correspond to a specification of a specific database are defined for each system; ,
When a query issued from the system is received, the conversion content corresponding to the system is acquired from the conversion definition file stored in the storage unit, and the received query is converted based on the acquired conversion content And a program that functions as a query conversion unit that supplies the converted query to a database management system corresponding to the specific database.

Images