JP3623873B2 - Database management system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a database management system that can efficiently access a large amount of data at high speed.
[0002]
[Prior art]
The CAD system is used in various fields as drawing creation software using a computer. For example, when this CAD system is used for designing a printed circuit board or the like, a database in which a component library is stored is referred to at the time of design, and necessary figures, characteristics, and the like of the components are obtained. This database stores image data for connection, electrical characteristic data, and the like regarding tens of thousands to hundreds of thousands of circuit components. The designer inquires of this database about necessary parts data while operating the CAD workstation, and uses it for design, drawing editing, and the like.
[0003]
The design of a printed circuit board requires an extremely large amount of component data. However, some databases storing a large amount of data require a relatively long access time for retrieving individual component data. In this case, the designer creates a list of necessary part data, edits the inquiry request, and performs batch processing. The database side notifies the designer of the result after the processing such as retrieval is completed for all data satisfying the inquiry request.
[0004]
[Problems to be solved by the invention]
By the way, the conventional techniques as described above have the following problems to be solved. When performing circuit design or the like, there are a case where it is sufficient to inquire of necessary data by batch processing as described above, and a case where it is desired to extract necessary part data in real time as much as possible. Since the necessary parts data can be obtained quickly, the design work time can be shortened and the product development speed can be increased.
However, the amount of data required for such a design is increasing, and the conventional system cannot increase the search speed unless the performance of the computer that manages the database is improved.
[0005]
[Means for Solving the Problems]
The present invention adopts the following configuration in order to solve the above points.
<Configuration 1>
The present invention relates to a utilization database that stores frequently used data within a range of a set maximum number and a set minimum number, a warehouse database that stores less frequently used data, a data search request from a request source, and a new registration In a database management system comprising an inquiry request processing unit that accepts either a request or a deletion request, and a data management unit that manages the utilization database and the warehouse database in response to any of the requests, the data management unit includes: Search the utilization database in response to a search request, and send the data to the request source if the corresponding data exists. If the corresponding data does not exist, search the warehouse database next and the corresponding data exists. Then, the data is transmitted to the request source, and the transmitted data is stored in the warehouse database. When the data is moved to the utilization database and the number of data in the utilization database exceeds the set maximum number by the movement, the least frequently used data in the utilization database is moved to the warehouse database, and in response to the new registration request When new data is registered in the utilization database and the number of data in the utilization database exceeds the set maximum number in the registration, the least frequently used data in the utilization database is moved to the warehouse database, and the deletion request is made On the other hand, deleting the corresponding data in the utilization database, and moving the most frequently used data in the warehouse database to the utilization database when the number of data in the utilization database falls below the set minimum number by the deletion, A database management system characterized by that.
[0009]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described using specific examples.
<Concrete example>
FIG. 1 is a block diagram of a database management system according to the present invention.
This system is used, for example, to store part library data used for CAD design. A CAD workstation 1 shown in the figure is a workstation used for designing an integrated circuit using a CAD system. Here, for example, as shown in the figure, a part library design, a circuit design, a board design, an integrated circuit (LSI) design, etc. are performed. Then, during these operations, inquiry requests such as retrieval, registration, and deletion of data relating to parts are made.
[0010]
In order to accumulate data necessary for such an inquiry request and enable access, a system configured as shown in the figure is prepared.
This system includes an inquiry request processing unit 3, a data management unit 5, a configuration file 6, a utilization database 7 and a warehouse database 8. The data is stored separately in the utilization database 7 and the warehouse database 8 as shown in FIG. The utilization database 7 stores frequently used data, for example, about 5000 to 10000.
[0011]
On the other hand, in the warehouse database 8, data with a relatively low use frequency other than the data is stored. The amount of data to be stored in the warehouse database 8 is several hundred thousand, for example. This data amount is not particularly limited.
[0012]
The inquiry request processing unit 3 is a part that receives an inquiry request relating to search of data stored in the database, new registration, or deletion of data. For this purpose, the inquiry request processing unit 3 includes a search unit 3-1, a registration unit 3-2, and a deletion unit 3-3. Data management unit 5 receives a request to query request processing unit 3, when utilizing the database 7 and warehouse database 8 is stored in the data access soot Rutotomoni, the state of the result data of the access has changed, the data This is the part that executes the replacement process. The reference for the data replacement process is stored in the configuration file 6.
[0013]
For example, in CAD design, there are thousands of parts data actually used out of more than a hundred thousand parts data stored. Therefore, for example, data that has never been accessed for the past year or more is stored in the warehouse database 8, and data accessed within one year is stored in the utilization database 7. If the utilization database 7 stores about 5000 to 10,000 pieces of data, this kind of component data can be accessed at a sufficiently high speed by a general database management system computer. That is, it becomes possible to answer the inquiry process at high speed in real time so that the designer does not feel stress.
[0014]
If there are hundreds of thousands of data and all of them are targeted for search, a relatively long processing time is required for each search. In fact, real-time processing places a lot of stress on the designer, and batch processing. There were many cases that had to be relied on. Here, the amount of data stored in the utilization database 7 is sufficiently reduced in this way, and the speed for query processing is improved to a practically satisfactory level. In this way, the design work can be speeded up.
[0015]
For this purpose, in the configuration file 6, for example, as shown in the lower part of FIG. 1, the size SA of the utilization database is set to a size that can store a maximum of 10,000 data and a minimum of 5000 data. ing. Further, the size SS of the warehouse database is set to infinity because the storage capacity may be increased as necessary. Further, the configuration file 6 is provided with a reference for exchanging data between the utilization database 7 and the warehouse database 8. The replacement period ST is based on this standard. For example, data that has not been used for more than one year is transferred from the utilization database 7 to the warehouse database 8. If there is no data that has not been used for more than one year, a standard of 9 months or more is set.
[0016]
On the other hand, if the amount of data stored in the utilization database is less than the maximum value and there is still room to store the data, the data is transferred from the warehouse database 8 to the utilization database 7. This is because data can be searched in a wider range. In this case, it is only necessary to move relatively frequently used data stored in the warehouse database.
[0017]
Further, among the data stored in the warehouse database 8, data that has been requested for retrieval is transferred to the utilization database 7.
These standards are set in the configuration file 6 in advance. In addition, it is set whether such replacement processing is performed in real time or in batch.
For this purpose, attribute data 11 including the date and time of registration, the date and time of last access, and the like is added to each data.
[0018]
FIG. 2 is an explanatory diagram of the description contents of the configuration file.
Here, the contents of the configuration file shown in FIG. 1 are generalized. The size SA of the utilization database may be freely set as long as it can be accessed at a sufficiently high speed in practice. This is experimentally determined by the performance of the database management device, the access speed of the storage device, and the like. It also varies greatly depending on the data size to be accessed. The size SS of the warehouse database is determined by the system. The replacement period ST is set by comparing the use frequency of the data stored in the utilization database 7 and the data stored in the warehouse database 8. Therefore, as a result of comparing the use frequency for each data, for example, the replacement period may be several months or several years.
[0019]
The execution format refers to an agreement between the timing for determining that replacement is necessary and the timing for actually executing replacement. Although it is desirable to be real-time, the number of data that can be stored in the utilization database is not strictly set to 10,000, and some variation is possible. Therefore, batch processing may be used in order to reduce the load on the system associated with data replacement and prevent the search processing from being hindered.
[0020]
FIG. 3 shows an inquiry request processing flowchart.
Hereinafter, the operation of the system of the present invention will be described in order.
First, when there is an inquiry request from a workstation or the like, the inquiry request is read in step S1, and processing corresponding to the content of the request is executed after step S2. If the request is a search request, in step S2, a search request flag is set and the data management instruction is executed. The data management instruction is sent to the data management unit 5 shown in FIG.
[0021]
In step S3, if there is a registration request, a registration request flag is set. In step S4, if there is a deletion request, a deletion request flag is set. Pass to 5. The configuration file is created using a text editor or the like with the contents already described. The data management unit 5 shown in FIG. 1 reads the contents of the configuration file 6 together with data access and other processing, sets it as table data, and operates according to the setting.
[0022]
FIG. 4 shows an operation flowchart of the data management process.
In step S1 in the figure, the data management unit 5 first reads the contents of the configuration file 6. If it is determined in step S2 that the content of the data is valid, the process proceeds to search registration or deletion processing. On the other hand, if the content of the data is invalid or does not exist, a default value prepared in advance is read and processing is performed (step S3). In the configuration data shown in FIG. 1, 9 months, 6 months, and 3 months are entered in the replacement period ST for the following reason.
[0023]
When the utilization database 7 is full, it is necessary to move any data to the warehouse database 8. At this time, data whose access period is one year or more is preferentially transferred. However, it may be necessary to move data even when there is no data that has not been accessed for more than one year. At this time, stepwise standards such as 9 months, 6 months, and 3 months are set. As a result, data that is less frequently used is transferred to the warehouse database 8.
[0024]
In FIG. 4, when the setting of the configuration data is completed, either the search data process in step S4, the registration data process in step S5, or the delete data process in step S6 is executed, and the process finally proceeds to step S7. Search results are output for the original. FIG. 5, FIG. 6, and FIG. 7 show specific flowcharts of the search data processing, registration data processing, and deletion data processing.
[0025]
FIG. 5 is an operation flowchart of search data processing.
First, in step S10, when receiving a search request, the data management unit 5 first searches the utilization database 7 for data that matches the search key. This is because in the case of frequently used data, the probability of being stored in the utilization database 7 is high. This is because the search process is performed at a higher speed. Here, in step S11, it is determined whether there is data. If there is data, the process proceeds to step S15, and the contents of the search data are returned. This enables data retrieval in real time.
[0026]
On the other hand, if the data does not exist in the utilization database 7, the process proceeds from step S11 to step S12. Then, data matching the search key is searched from the warehouse database 8. In this case, since a large amount of data is stored in the warehouse database 8, a relatively time-consuming search is performed as in the prior art. As a result, if it is determined in step S13 that there is data, the process proceeds to step S16, and the result is returned to the inquiry source. If it is determined that the data does not exist, the process proceeds to step S14, and a reply that there is no registered data is returned to the inquiry source.
[0027]
If data matching the search key is searched from the warehouse database and the contents of the search data are returned in step S6, the process proceeds to step S17, and data replacement processing is executed. That is, since the data searched in the warehouse database is the latest searched data, it is transferred to the utilization database 7. If the amount of data stored in the utilization database 7 does not exceed 10,000, the process ends here. However, when the size of the utilization database exceeds 10,000, the data with low frequency of use exceeding the period specified by the replacement period is transferred from the utilization database to the warehouse database. Such a replacement process is executed, and the process ends.
[0028]
FIG. 6 shows a registration data processing operation flowchart.
If there is a registration request, the data management unit 5 registers the registration request data in the utilization database in step S21. Since the data requested to be registered has a high probability of being used immediately, registration in the utilization database 7 is executed. In step S22, a registration end message is returned to the request source.
[0029]
Next, in step S23, the number of utilization databases 7 is checked. In the next step S24, it is determined whether or not the number of registered data items exceeds 10,000. If the number exceeds 10,000, the replacement process is executed for the data in the utilization database 7 and the warehouse database 8 as described above (step S25). In this way, data that is used more frequently is accumulated on the utilization database side.
[0030]
FIG. 7 shows a deletion data processing flowchart.
First, when a request for data deletion is received from the inquiry request processing unit 3, the data management unit 5 first searches the utilization database 7 for data that matches the deletion key (step S31). Here, in step S32, it is determined whether there is data. If there is no data, the process proceeds to step S33, and data matching the deletion key is searched from the warehouse database 8. In step S34, it is determined again whether there is data. If there is no data, the process proceeds to step S35, and an answer indicating no data is returned. That is, a reply that there is no data to be deleted is returned to the request source.
[0031]
On the other hand, if data exists, the corresponding data is deleted from the warehouse database 8 in step S36. If there is corresponding data in the warehouse database, the processing is thus completed. It should be noted that there is no significant functional difference between the data deletion process and the retrieval from the utilization database 7 or the retrieval from the warehouse database 8 first.
[0032]
On the other hand, if it is determined in step S32 that there is data to be deleted in the utilization database, the process proceeds to step S37, where the data is deleted, and a deletion end notification is made. In step S38, the number of utilization databases after deletion is checked. Here, in step S39, it is determined whether the data amount is 5000 or less. If the number is 5000 or less, the process proceeds to step S40, and data is transferred from the warehouse database 8 to the utilization database 7.
[0033]
As described above, the attribute data 11 including the registration date and time and the last accessed date and time is added to each data. By referring to this, the data stored in the warehouse database 8 is moved to the utilization database 7 relatively frequently, and the efficiency of data retrieval in the utilization database is increased.
[0034]
【The invention's effect】
According to the present invention described above, frequently used data is stored in the database, and data that is relatively infrequently used is stored in the warehouse database, and when search, registration, deletion processing, etc. are executed, Since the configuration file is referred to and the data is exchanged, the search speed can be increased by narrowing down the substantial data search to the utilization database 7. As a result, real-time access becomes possible, and operations such as CAD design can be speeded up and made efficient.
[0035]
Also, new data registration takes much longer than the process of searching for and displaying data. If such processing can be performed at high speed in real time, the waiting time of the person in charge of design is reduced when a new design is made after waiting for registration of the data. As a result, the total design work period can be shortened.
[0036]
In addition, by adding attribute data such as registration date / time and date / time of previous access to each data in the database, it is possible to accurately grasp the usage status of data and to easily and accurately organize, manage, and delete data. It becomes possible to do.
[Brief description of the drawings]
FIG. 1 is a block diagram of a database management system according to the present invention.
FIG. 2 is an explanatory diagram of description contents of a configuration file.
FIG. 3 is an operation flowchart of an inquiry request process.
FIG. 4 is an operation flowchart of a data management process.
FIG. 5 is a flowchart of search data processing.
FIG. 6 is a registration data processing flowchart.
FIG. 7 is a flowchart of deletion data processing.
[Explanation of symbols]
1 Workstation 3 Inquiry Request Processing Unit 5 Data Management Unit 6 Configuration File 7 Utilization Database 8 Warehouse Database 11 Attribute Data

Claims (1)

Utilization database that stores frequently used data within the range of the maximum number and minimum number of settings, warehouse database that stores data that is not frequently used, and data retrieval requests, new registration requests, and deletion requests from the request source In a database management system comprising an inquiry request processing unit that accepts any of the above, and a data management unit that manages the utilization database and the warehouse database in response to any of the requests,
The data management unit
In response to the search request, the utilization database is searched. When the corresponding data exists, the data is transmitted to the request source. When the corresponding data does not exist, the warehouse database is searched, and the corresponding data is found. If present, the data is transmitted to the request source, the transmitted data is moved from the warehouse database to the utilization database, and if the number of data in the utilization database exceeds the set maximum number in the movement, Move the least frequently used data to the warehouse database,
In response to the new registration request, new data is registered in the utilization database. When the number of data in the utilization database exceeds the set maximum number in the registration, the least frequently used data in the utilization database is moved to the warehouse database. Let
In response to the deletion request, corresponding data in the utilization database is deleted, and when the number of data in the utilization database falls below the set minimum number by the deletion, the most frequently used data in the warehouse database is deleted from the utilization database. Move to
A database management system characterized by that.

Images