JPH1196050A - Data base management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To always optimize a data base by making it possible to access data of comparatively high using frequency stored in an active data base and properly substituting data stored in a store data base. SOLUTION: Parts data of CAD are dividedly stored in the active data base 7 and the store data base 8. Data of high using frequency are stored in the data base 7. When a condition such as the using frequency of data is changed by an inquiry request, a data management part 5 substitutes data in accordance with a condition set up by a configuration file 6.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a database management system capable of efficiently and quickly accessing a large amount of data.

[0002]

2. Description of the Related Art CAD systems are used in various fields as software for creating drawings using a computer. For example, when the CAD system is used for designing a printed circuit board or the like, a database storing a component library is referred to at the time of design to obtain necessary figures and characteristics of components. This database stores connection image data, electrical characteristic data, and the like for tens to hundreds of thousands of circuit components. While operating the CAD workstation, the designer inquires of this database for necessary component data, and uses the data for design and drawing / editing.

[0003] The design of a printed circuit board requires an extremely large number of component data. However, some databases that store a large amount of data require a relatively long access time to retrieve individual component data. In this case, the designer creates a list of necessary component data, edits the inquiry request, and performs batch processing. On the database side, after processing such as retrieval is completed for all data satisfying the inquiry request, the result is notified to the designer.

[0004]

However, the above-mentioned prior art has the following problems to be solved.
When performing circuit design or the like, there are a case where the necessary data is inquired by the batch processing as described above and a case where it is desired to extract necessary component data in real time as much as possible. Since the necessary component data can be obtained quickly, the design work time can be reduced, and the product development speed can be increased. However, the amount of data required for such a design is increasing more and more, and in the conventional system, the search speed cannot be increased unless the performance of the computer that manages the database is improved.

[0005]

The present invention employs the following structure to solve the above problems. <Configuration 1> An inquiry request processing unit that receives an inquiry request for referring to the database, a utilization database that is first referred to in response to the inquiry request and stores data equal to or less than a predetermined amount, and stored in the utilization database. Stores data other than the data used, and refers to the utilization database and refers to the warehouse database when there is no corresponding data, and refers to the utilization database or the warehouse database in response to the inquiry request, and provides a predetermined response. And a data management unit for exchanging data between the utilization database and the warehouse database when the state of the data stored in the storage database changes.

<Structure 2> In the system described in Structure 1, the data management unit, when the inquiry request received by the inquiry request processing unit is a data search request,
First, the utilization database is searched, and if there is no corresponding data in this utilization database, the warehouse database is searched, and if there is any data in the warehouse database, the result is returned to the request source, and When the amount of data stored in the utilization database exceeds a predetermined value, the least-used data among the data stored in the utilization database is transferred to the warehouse database. A database management system for performing data exchange so as to move to a database.

<Configuration 3> In the system described in Configuration 1, when the inquiry request received by the inquiry request processing unit is a new data registration request, the data management unit registers the corresponding data in the utilization database. On the other hand, when the amount of data stored in the utilization database exceeds a predetermined value set in advance, data exchange is performed so that the least frequently used data among the data stored in the utilization database is moved to the warehouse database. A database management system characterized by executing.

<Structure 4> In the system described in Structure 1, the data management unit, when the inquiry request received by the inquiry request processing unit is a data deletion request,
When the corresponding data is deleted from the utilization database,
When the amount of data stored in the utilization database falls below a predetermined value set in advance, the data exchange is performed so that the most frequently used data among the data stored in the warehouse database is moved to the utilization database. A database management system characterized by executing.

[0009]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiments of the present invention will be described below using specific examples. FIG. 1 is a block diagram of a database management system according to the present invention. This system is, for example, CA
It is used to store component library data used in the design of D. CAD workstation 1 shown in the figure
Is a workstation used for designing an integrated circuit using a CAD system. Here, as shown in the figure, for example, component library design, circuit design, board design, integrated circuit (LSI) design, and the like are performed. And
During these operations, search, register,
Make an inquiry request such as deletion.

In order to accumulate data necessary for such an inquiry request and enable access, a system having a configuration 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 a utilization database 7 and a warehouse database 8, as shown in FIG. The utilization database 7 stores frequently used data, for example, about 5000 to 10000 data.

On the other hand, the warehouse database 8 stores data having a relatively low frequency of use other than the data. The amount of data to be stored in the warehouse database 8 is, for example, several hundred thousand. There is no particular limitation on this data amount.

The inquiry request processing unit 3 is a part for receiving an inquiry request regarding retrieval of data stored in the database, new registration, deletion of data, and the like. To this end, the inquiry request processing unit 3 includes a search unit 3-1, a registration unit 3-2, and a deletion unit 3-3. The data management unit 5 receives a request from the inquiry request processing unit 3 and uses the utilization database 7 and the warehouse database 8.
The number of accesses to the data stored in the data storage unit, and when the state of the data changes as a result of the access, the data exchange process is performed. Criteria for the data exchange processing are stored in the configuration file 6.

For example, in CAD design, out of the hundreds of thousands of stored component data, there are thousands of component data actually used. Therefore, for example, data that has never been accessed for the past one year or more is stored in the warehouse database 8, and data accessed within one year is stored in the utilization database 7. If about 5000 to 10,000 data are stored in the utilization database 7, this kind of component data can be accessed sufficiently quickly by a general database management system computer. That is,
It is possible to respond to the query processing in real time and at high speed so that the designer does not feel stress.

If there are hundreds of thousands of data and all of them are to be searched, a relatively long processing time is required for each search, and in real-time processing, the stress given to the designer is large. In many cases, they had to rely on batch processing. Here, the amount of data stored in the utilization database 7 is sufficiently reduced in this way, and the speed of the inquiry process is improved to a level that does not pose a practical problem. In this way, the design work can be speeded up.

For this purpose, the configuration file 6 has, for example, a size SA capable of storing a maximum SA of 10,000 and a minimum of 5,000 data as shown in the lower part of FIG. Is set to In addition, the maximum value of the size SS of the warehouse database is set to infinity because the storage capacity may be increased as needed. Further, the configuration file 6 has a standard for exchanging data between the utilization database 7 and the warehouse database 8. The replacement period ST is based on this criterion. For example, data that has not been used for one year or more 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, there will be a standard of nine months or more.

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 for storing data, the data is transferred from the warehouse database 8 to the utilization database 7. This is because data retrieval can be performed in a wider area. In this case, among the data stored in the warehouse database, relatively frequently used data may be moved.

Further, among the data stored in the warehouse database 8, those for which a search request has been made are transferred to the utilization database 7. These criteria are set in the configuration file 6. In addition to this, a setting is made as to whether such replacement processing is performed in real time or in batch. For this purpose, attribute data 11 including the registration date and time and the date and time of previous access is added to each data.

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 and shown.
The size SA of the utilization database may be set freely within a range that can be accessed at a sufficiently high speed for practical use.
This is experimentally determined by the performance of the database management device, the access speed of the storage device, and the like. Also, it greatly depends 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 frequency of use of the data stored in the utilization database 7 and the frequency of use of the data stored in the warehouse database 8. Therefore, as a result of comparing the frequency of use for each data, for example, the replacement period may be several months or several years.

The execution format refers to an agreement between a timing at which it is determined that replacement is necessary and a timing at which the replacement is actually executed. Desirably real-time,
The number of data that can be stored in the utilization database is not set to be exactly 10,000, and a slight variation is possible. Therefore, batch processing may be used to reduce the load on the system due to the data replacement and to prevent the search processing from being hindered.

FIG. 3 shows a flowchart of an inquiry request processing operation. Hereinafter, the operation of the system of the present invention will be described in order. First, when an inquiry request is received 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 in step S2 and subsequent steps. If the request is a search request, a search request flag is set in step S2, and the data management instruction is executed. The data management instruction is sent to the data management unit 5 shown in FIG.

In step S3, if there is a registration request, a registration request flag is set, and in step S4, if there is a deletion request, a deletion request flag is set, and a necessary data management request is set. The data is passed to the data management unit 5. The configuration file is created using a text editor or the like with the contents described above. The data management unit 5 shown in FIG. 1 reads the contents of the configuration file 6 together with data access and other processes, sets the read data as table data, and operates as set.

FIG. 4 shows an operation flowchart of the data management process. In step S1 of the figure, first, the data management unit 5 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, the default value prepared in advance is read and the process 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.

When the utilization database 7 becomes full, it is necessary to move any data to the warehouse database 8. At this time, data with no access for one year or more is preferentially moved. However, even when there is no data that has not been accessed for one year or more, data may need to be transferred. At this time, stepwise standards such as 9 months, 6 months, and 3 months are set. As a result, less frequently used data is moved to the warehouse database 8.

In FIG. 4, when the setting of the configuration data is completed, the retrieval data processing in step S4 or the registered data processing in step S5, and step S6
Is performed, and finally the process proceeds to step S7, where a search result is output to the request source. FIGS. 5, 6, and 7 show specific flowcharts of the search data processing, the registration data processing, and the deletion data processing.

FIG. 5 is an operation flowchart of the search data processing. First, in step S10, when receiving the search request, the data management unit 5 first searches the utilization database 7 for data matching the search key. This is because data that is frequently used has a high probability of being stored in the utilization database 7. Another reason is to perform the search processing at a higher speed. Here, in step S11, it is determined whether or not there is data. If there is data, the process proceeds to step S15, and the content of the search data is returned. This enables data retrieval in real time.

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 related art. As a result, if it is determined in step S13 that there is data,
Proceeding to step S16, the result is returned to the source of the inquiry. If it is determined that there is no data, the process proceeds to step S14, and a response that there is no registered data is returned to the inquiry source.

The data matching the search key is searched from the warehouse database, and if the content of the search data is returned in step S6, the process proceeds to step S17, where the data is replaced. That is, since the data searched in the warehouse database is the data searched latest, it is transferred to the utilization database 7. And
If the data amount stored in the utilization database 7 does not exceed 10,000, the processing is terminated. However, if the size of the utilization database exceeds 10,000, the infrequently used data exceeding the period specified in the replacement period is transferred from the utilization database to the warehouse database. After performing such a replacement process, the process ends.

FIG. 6 shows a flowchart of the registration data processing operation. 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 for which registration has been requested is likely to be used immediately, registration to the utilization database 7 is performed. Then, in step S22, a registration end message is returned to the request source.

Next, in step S23, the number of cases in the utilization database 7 is checked. The next step S24 checks whether the number of registered data items exceeds 10,000.
Judge in. If there are more than 10,000,
The exchange process is performed on the data in the utilization database 7 and the data in the warehouse database 8 as described above (step S25). In this way, more frequently used data is stored in the utilization database.

FIG. 7 shows a flowchart of the deletion data processing. First, when a request for data deletion is received from the inquiry request processing unit 3, the data management unit 5 searches the utilization database 7 for data that matches the deletion key first (step S31). Here, in step S32, it is determined whether or not there is data. If there is no data, the process proceeds to step S33 to search the warehouse database 8 for data matching the deletion key. Then, in step S34, it is determined whether or not there is data again. 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.

On the other hand, if data exists, step S3
At 6, the corresponding data is deleted from the warehouse database 8. If there is data corresponding to the warehouse database, the process ends in this way. It should be noted that there is no significant difference in the function of the data deletion process whether the search is performed first from the utilization database 7 or the warehouse database 8 is searched first.

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. Then, the process proceeds to step S38 to check the number of the utilization databases after the deletion. 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.

As described above, each data includes attribute data 11 including the registration date and time and the last access date and time.
Is added. By referring to this, the relatively frequently used data stored in the warehouse database 8 is transferred to the utilization database 7, and the efficiency of data retrieval in the utilization database is increased.

[0034]

According to the present invention described above, frequently used data is stored in a database, and relatively infrequently used data is stored in a warehouse database. Is executed, the data is replaced with reference to the configuration file, so that the actual data search can be narrowed down to the utilization database 7 and the search speed can be increased. This allows real-time access, for example C
Work such as AD design can be made faster and more efficient.

The work of registering new data takes much longer than the process of searching and displaying data. If such processing can be performed at high speed in real time,
In the case where a new design is to be performed after the registration of the data, the waiting time of the designer is reduced. Thus, the total design work period can be shortened.

Further, by adding attribute data such as the registration date and time and the last access date and time to each data in the database, the usage status of the data can be accurately grasped, and the data can be easily organized, managed and deleted. And it can be performed accurately.

[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 a flowchart of an inquiry request processing operation.

FIG. 4 is an operation flowchart of a data management process.

FIG. 5 is a search data processing flowchart.

FIG. 6 is a registration data processing flowchart.

FIG. 7 is a flowchart of a deletion data process.

[Explanation of symbols]

 Reference Signs List 1 workstation 3 inquiry request processing unit 5 data management unit 6 configuration file 7 utilization database 8 warehouse database 11 attribute data

Claims (4)

[Claims] An inquiry request processing unit for receiving an inquiry request for referring to a database, a utilization database which is first referred to in response to the inquiry request and stores data equal to or less than a predetermined amount, and stored in the utilization database A data base other than the stored data is stored, and a warehouse database referred to when there is no corresponding data by referring to the utilization database, and a prescribed response is referred to by referring to the utilization database or the warehouse database in response to an inquiry request. And a data management unit for exchanging data between the utilization database and the warehouse database when there is a change in the state of the data stored therein. 2. The system according to claim 1, wherein the data management unit receives the inquiry request received by the inquiry request processing unit.
In the case of a data search request, the utilization database is searched first, and if there is no corresponding data in this utilization database, the warehouse database is searched. The result is returned to the request source, and the corresponding data is moved from the warehouse database to the utilization database. If the amount of data stored in the utilization database exceeds a predetermined value set in advance, of the data stored in the utilization database, A database management system, wherein data is exchanged so that least frequently used data is moved to a warehouse database. 3. The system according to claim 1, wherein the data management unit receives the inquiry request received by the inquiry request processing unit,
In the case of a new data registration request, the corresponding data is registered in the utilization database, and if the amount of data stored in the utilization database exceeds a predetermined value set in advance, of the data stored in the utilization database, A database management system characterized in that data is exchanged so that infrequently used data is moved to a warehouse database. 4. The system according to claim 1, wherein the data management unit receives the inquiry request received by the inquiry request processing unit,
In the case of a data deletion request, when the corresponding data is deleted from the utilization database, and when the amount of data stored in the utilization database falls below a predetermined value set in advance, of the data stored in the warehouse database, A database management system characterized in that data is exchanged so that the most frequently used data is moved to a utilization database.