JP2009122966A - Database assignment device, database assignment method, program, and recording medium - Google Patents

Database assignment device, database assignment method, program, and recording medium Download PDF

Info

Publication number
JP2009122966A
JP2009122966A JP2007296264A JP2007296264A JP2009122966A JP 2009122966 A JP2009122966 A JP 2009122966A JP 2007296264 A JP2007296264 A JP 2007296264A JP 2007296264 A JP2007296264 A JP 2007296264A JP 2009122966 A JP2009122966 A JP 2009122966A
Authority
JP
Japan
Prior art keywords
database
distribution
processing
processing request
databases
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
JP2007296264A
Other languages
Japanese (ja)
Other versions
JP5269394B2 (en
Inventor
Tatsutoshi Murata
龍俊 村田
Original Assignee
Nomura Research Institute Ltd
株式会社野村総合研究所
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nomura Research Institute Ltd, 株式会社野村総合研究所 filed Critical Nomura Research Institute Ltd
Priority to JP2007296264A priority Critical patent/JP5269394B2/en
Publication of JP2009122966A publication Critical patent/JP2009122966A/en
Application granted granted Critical
Publication of JP5269394B2 publication Critical patent/JP5269394B2/en
Application status is Expired - Fee Related legal-status Critical
Anticipated expiration legal-status Critical

Links

Images

Abstract

<P>PROBLEM TO BE SOLVED: To provide a database assignment device which automatically selects a database and improves efficiency in business work processing and users' satisfaction. <P>SOLUTION: In a service-providing system 1, users 5 make a request for database processing to a service-provider 3, and the service-provider 3 has an application server 13, a database assignment device 15 and a plurality of databases which correspond to different purposes. The database assignment device 15 holds assignment definition information 23 which correlates assignment conditions for requests for database processing with assignment destination databases. The database assignment device 15 acquires database-processing requests from the users 5 via the application server 13. The database assignment device 15 determines assignment destination databases, on the basis of the assignment definition information 23 and the database-processing requests, and assigns the database processing requests to the adequate databases. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a database distribution device that determines an appropriate database from a plurality of databases and distributes processing requests in response to processing requests to the database.

2. Description of the Related Art Conventionally, a service provider's server that provides predetermined information to a user performs processing such as search, reference, and update regarding information held in response to a request sent from the user's terminal device.
For example, as an example of a service provider, a server of a securities-related provider performs processing such as reference and registration of stock price information, asset management information, registration information, and log information stored in a database in response to a user request. .

  In order for a service provider to provide the latest information promptly and safely in response to requests from a large number of users, it is necessary to increase the capacity, performance and reliability of a database for storing information. In addition, when access from a large number of users' terminal devices is concentrated, in order for the service provider to provide comfortable information to the user, the service provider's server and the database are improved. Large capacity is required.

  In addition, service providers may use a mirror database that is created by duplicating information stored in the original database at a predetermined time in order to avoid business interruption due to a database failure. In addition, the service provider may copy a part of the information in the original database at a predetermined time and create and use a plurality of duplicate databases for each information type.

  Note that a web server that provides a service via a network stores logs relating to transaction results on the web, screen transition processing, information reference, and the like. By saving the log, we will improve security by responding to inquiries regarding transactions from users, checking the operation of the web server, and monitoring unauthorized access.

There is a system in which a log output from an application of each client (user terminal device) is transmitted to a center server, and an application operation of each client is monitored. In this system, there is a log management method in which the center server adjusts the timing of log transmission from each client (see, for example, [Patent Document 1]).
Also, for the problem that the log information storage area becomes full, analyze the stored log information, edit the less important one, move it to a separate file as a statistical information log, and store it. There is a log information storage method in which log information is efficiently stored in a file area by leaving it as it is (see, for example, [Patent Document 2]).

JP 2002-41330 A Japanese Patent Laid-Open No. 10-275098

  As described in [Patent Document 1], a log management method for adjusting the timing of log transmission from each client to collect logs and storing them in a database, and a method for processing and storing logs according to importance according to [Patent Document 2] Various methods for collecting logs and storing them in a database have been proposed. However, when a service provider acquires a processing request for a database, no proposal has been made regarding selecting an appropriate database in which information corresponding to a user's processing request is stored without imposing a processing load on the server.

  In addition, in order to reduce the access load on the database, when the service provider has a plurality of databases (original database and a plurality of mirror databases), the server of the service provider applies to each database as needed in addition to the original business processing. There is a problem that a processing load is required to monitor load information and select an appropriate database. In addition, the processing load on the server has caused a problem that the service efficiency of the service provider's server is reduced.

  When an appropriate database is selected from a plurality of databases in response to a processing request from a user and used, the service provider server needs to determine and access an access destination database each time. Therefore, there is a problem that the processing load is applied to the server and the processing programming of the server is complicated. As a result, there has been a problem that the workload of changing the processing programming of the server and the workload of the maintenance work are applied.

  Also, when access from a large number of user terminal devices concentrates on the service provider's server, the server will preferentially perform processing related to access from, for example, a user with priority or a branch terminal device of the service provider. However, there is a problem that the processing load is applied and the preferential processing cannot be executed.

  The present invention has been made in view of the above-described problems, and an object of the present invention is to provide a database distribution device that can automatically perform database selection and improve business processing efficiency and user satisfaction. To do.

  In order to achieve the above-described object, the first invention is a database distribution device that is connected to a plurality of databases, acquires processing requests for the databases, and distributes the processing requests to at least one of the plurality of databases. Distribution definition information holding means for holding distribution definition information for associating a distribution condition of a request with a distribution destination database, and the plurality of databases based on the acquired processing request with reference to the distribution definition information A database allocation method, comprising: an allocation destination determination unit that determines the allocation destination database, and an allocation unit that allocates the acquired processing request to the determined allocation destination database. It is a minute device.

The database includes an original database that stores master data and a derivative database that is created based on at least a part of information stored in the original database. As for the update and creation of the derived database, the original database and the derived database may be updated simultaneously at the transaction level (simultaneous update), or the original database is replicated simultaneously with the update of the original database using the replication function provided by the database. Then, the derived database may be created (replication), or the original database may be duplicated by batch processing at a predetermined timing to create the derived database (fixed point copy).
The processing request for the database is a request for inquiry and search for information stored in the database, registration of information in the database, update / change processing of registered information, and the like.
In the processing request distribution condition, a condition for distributing the processing request is set in a database suitable for the content of the processing request.

  The database distribution device according to the first aspect of the present invention is connected to a plurality of databases and holds distribution definition information for associating distribution conditions of processing requests with distribution destination databases. The database distribution device acquires a processing request for the database, refers to the distribution definition information, determines a distribution destination database from a plurality of databases, and distributes the acquired processing request.

The distribution condition of the processing request may include a distribution condition related to the processing type or processing target of the processing request. The process type is a process content for information stored in the database, and includes information reference, update, registration, search, and the like. The processing target is information content stored in the database, and is, for example, market price price information and chart information, user authentication information, user asset information, and the like.
The distribution destination database determining means may determine the distribution destination database by detecting a processing type or a processing target from the acquired processing request.

The processing request distribution condition may include a time period, a database load, a database failure status, a search range, and a distribution condition related to a user attribute or a terminal device attribute that has made the processing request. The time zone is a time zone when the processing request is acquired from the user terminal device. The database load is an access load status to each database. The database failure status indicates whether or not a failure (hardware and software failure) has occurred in the database. The user attribute is, for example, a user identification code, and may be capable of determining the priority of the user and the presence or absence of a trading account. The search range is a search range of information designated from the user terminal device. The terminal device attribute may be, for example, a terminal device identification code that can determine whether the terminal device belongs to a storefront, a branch, or the like, or to a general user.
The distribution destination database determination means may acquire information regarding the time zone, the database load, the search range, the attribute of the user who made the processing request, or the attribute of the terminal device, and may determine the distribution destination database.

The distribution definition information may be stored in association with whether or not the distribution destination database can be selected by the user who made the processing request or the terminal device. If the allocation destination database determination unit determines that the allocation destination database can be selected, the allocation destination database may be selected by the user who made the processing request or the terminal device.
The plurality of databases may have a hierarchical structure based on the creation time of the database or the database information type (market price, authentication,...).

The database distribution device includes a plurality of individual database distribution devices including a distribution definition information holding unit, a distribution destination determination unit, and a distribution unit, and the attribute of the user who made the load or processing request of the individual database distribution device Or based on the information regarding the attribute of a terminal device, you may distribute a process request to an individual database distribution device.
The distribution definition information holding means of the individual database distribution device may hold different distribution definition information.

  In the first invention, the database distribution device can automatically select a database according to a processing request and improve business processing efficiency.

  A second invention is a database distribution method in a database distribution device that is connected to a plurality of databases, acquires processing requests for the databases, and distributes the processing requests to at least one of the plurality of databases. A distribution definition information holding step for holding distribution definition information for associating a distribution condition with a distribution destination database; referring to the distribution definition information; and from among the plurality of databases based on the acquired processing request A database distribution method comprising: a distribution destination determination step for determining the distribution destination database; and a distribution step for distributing the acquired processing request to the determined distribution destination database. is there.

  The second invention is an invention relating to a database distribution method for distributing a processing request to a database according to a processing request distribution condition.

  A third invention is a program that is connected to a plurality of databases, and that can be executed in a database distribution device that acquires processing requests for the databases and distributes the processing requests to at least one of the plurality of databases, wherein the database distribution device A distribution definition information holding means for holding distribution definition information for associating a distribution condition of the processing request with a distribution destination database, referring to the distribution definition information, and based on the acquired processing request It is a program for functioning as a distribution destination determination unit that determines the distribution destination database from a plurality of databases, and a distribution unit that distributes the acquired processing request to the determined distribution destination database.

According to a fourth aspect of the present invention, there is provided a computer-readable recording medium that records a program that is connected to a plurality of databases, acquires a processing request for the database, and distributes the processing request to at least one of the plurality of databases. The database distribution device refers to the distribution definition information holding means for storing distribution definition information for associating the distribution condition of the processing request with the distribution destination database, the distribution definition information, An allocation destination determining unit that determines the allocation destination database from the plurality of databases based on the acquired processing request; an allocation unit that distributes the acquired processing request to the determined allocation destination database; It is a computer-readable recording medium which recorded the program for functioning as.
Note that the above program may be distributed by being held on a recording medium such as a CD-ROM, or the program can be transmitted and received via a communication line.

  According to the present invention, it is possible to provide a database distribution device that can automatically perform database selection and improve business processing efficiency and user satisfaction.

  Hereinafter, a preferred embodiment of the database distribution device 15 according to the present invention will be described in detail with reference to the accompanying drawings. The database distribution device 15 is one of devices included in the service provider 3 in the service providing system 1. In the following description and the accompanying drawings, the same reference numerals are given to components having substantially the same functional configuration, and redundant description will be omitted.

(1. Configuration of service providing system 1)
First, the configuration of the service providing system 1 will be described with reference to FIG.
FIG. 1 is a configuration diagram of a service providing system 1.

(1-1. Service providing system 1)
The service providing system 1 is configured by connecting a WEB server 11 belonging to a service provider 3 and terminal devices 9 belonging to a plurality of users 5 to a network 7. The network 7 is the Internet, an intranet, or the like.
The service provider 3 is a provider that provides predetermined information to the user 5 via the network 7.

(1-1. Service provider 3)
The service provider 3 includes a WEB server 11, an application server 13, a database distribution device 15, a database A17, a database B19, and the like. The WEB server 11 transmits and receives various types of information to and from the terminal device 9 of the user 5 and other servers (not shown) via the network 7. The application server 13 performs various types of information processing related to service provision.

When the database distribution device 15 acquires a processing request from the application server 13 to the database, the database distribution device 15 distributes the processing request to an appropriate database. Details of the database distribution device 15 will be described later.
Database A17 and database B19 hold various information related to service provision. Details of the database A17 and the database B19 will be described later. Note that the storage information of the database A17 shown in FIG. 1 is updated in real time, and the storage information of the database A17 is copied to the database B19 at a predetermined timing.

(1-2. Database distribution device 15)
When the database distribution device 15 acquires a processing request from the application server 13 to the database, the database distribution device 15 distributes the processing request to an appropriate database. Therefore, the application server 13 does not need to perform processing for selecting an appropriate database.

  The database distribution device 15 is stored in the distribution destination determination unit 21, the distribution unit 22, the time zone acquisition unit 25, the database load information acquisition unit 27, the user attribute acquisition unit 29, the terminal device attribute acquisition unit 31, and the storage unit 205. Distribution definition information 23 and the like. The database distribution device 15 includes the time zone acquisition unit 25, the database load information acquisition unit 27, the user attribute acquisition unit 29, and the terminal device attribute acquisition unit 31 as necessary.

The distribution destination determination unit 21 acquires a processing request from the application server 13 to the database, and determines a database to which the processing request is distributed based on the distribution definition information 23.
The distribution unit 22 distributes the processing request to the database determined by the distribution destination determination unit 21.
The distribution definition information 23 is information that associates a distribution condition of a processing request acquired from the application server 13 with a distribution destination database. The distribution definition information 23 is stored in the storage unit 205 of the database distribution device 15.

  The time zone acquisition unit 25 acquires information related to the time zone when the database distribution device 15 acquires the processing request.

  The database load information acquisition unit 27 acquires information regarding the database load status of the service provider 3. The database load information acquisition unit 27 also acquires the database failure status.

  The user attribute acquisition unit 29 acquires information related to the attribute of the user 5 who has made a processing request to the service provider 3. The user attribute is, for example, a user ID for identifying the user 5.

  The terminal device attribute acquisition unit 31 acquires information related to the attribute of the terminal device 9 that has made a processing request to the service provider 3. The terminal device attribute 73 is, for example, a terminal device ID that identifies the affiliation of the terminal device 9 (for example, a store related to the service provider 3 or a general user).

(1-3. Database)
The service providing event person 3 has a plurality of databases. FIG. 1 shows a database A17 whose stored information is updated in real time, and a database B19 in which at least a part of the information stored in the database A17 is replicated at a predetermined timing. The database A17 is a source database that stores master data, and the database B19 is a derivative database created in a derivative manner based on the database A17.
As for the update and replication of the database B19, the database A17 and the database B19 may be updated simultaneously at the transaction level (simultaneous update), or the database A17 is replicated simultaneously with the update of the database A17 using the replication function provided in the database. Then, the database B19 may be created (replication), or the database A19 may be duplicated by batch processing at a predetermined timing to create the database B19 (fixed point copy). The predetermined timing is set to a timing suitable for each type of information, such as a timing three times a day, a timing immediately after the end of the service of the service provider 3, and the like. Note that all the stored information in the database A17 may be duplicated, or a part of the stored information may be duplicated.

The database A17 stores information such as market price information 33, authentication information 35, asset information 37, log information 39, registration information 41, and the like. The information stored in the database A17 is always the latest information.
In the market price information 33, the market price information of stocks within the securities trading time is updated as needed. The market price information 33 after the end of the securities transaction is held until the next securities transaction is started and updated.

The authentication information 35 is a user ID or the like of the user 5 sent from the terminal device 9 and is verification information at the time of authentication.
The asset information 37 is information related to the owned assets for each user 5. Within the actual working hours of the service provider 3, the asset information 37 is updated as needed when the status of owned assets changes.

The log information 39 is information related to the communication history and transaction history between the user 5 and the service provider 3. The log information 39 is updated at any time within the service hours of the service provider 3.
The registration information 41 stores information related to registration of the user 3 and the terminal device 9. The registration information 41 includes, for example, the name, address, email address, transaction account number, etc. of the user 3. The registration information 41 is updated within the working hours of the service provider 3.

  The database B19 holds information such as market price information 43, authentication information 45, asset information 47, log information 49, registration information 51, and the like. The market price information 43, authentication information 45, asset information 47, log information 49, and registration information 51 are based on the market price information 33, authentication information 35, asset information 37, log information 39, and registration information 41 stored in the database A17, respectively. It has been created.

(2. Hardware configuration)
Next, the hardware configuration of the database distribution device 15 will be described with reference to FIG.
FIG. 2 is a hardware configuration diagram of the database distribution device 15. Note that the hardware configuration in FIG. 2 is an example, and various configurations can be adopted depending on the application and purpose.

  The database distribution device 15 is configured by connecting a CPU 201, a memory 203, a storage unit 205, a display unit 207, an input unit 209, an output unit 211, and a communication unit 213 via a system bus 215.

  A CPU 201 (Central Processing Unit) is a device that performs operation control of arithmetic devices (four arithmetic operations, comparison operations, etc.), hardware and software.

  The memory 203 is a memory such as a RAM and a ROM. A RAM (Random Access Memory) stores a ROM (Read Only Memory), an OS (Operating System) program read from the storage unit 205, an application program, and the like. The RAM functions as a main memory and work area for the CPU 201.

  The storage unit 205 is a device that stores various data, and is, for example, a hard disk. The storage unit 205 stores a program executed by the CPU 201, data necessary for program execution, an OS, various databases, and the like.

  The display unit 207 is a display device, such as a CRT monitor or a liquid crystal panel. The display unit 207 includes a logic circuit (such as a video adapter) for realizing the video function of the computer.

  The input unit 209 is an input device for various data, such as a keyboard and a mouse. The output unit 211 is an output device for various data, for example, a printer. A drive device that performs data input / output with various media can also be used as the input unit 209 and the output unit 211.

The communication unit 213 is a communication control device that connects and communicates with an external device via the system bus 215. For example, Internet communication using TCP / IP is possible.
The system bus 215 is a path that mediates transmission / reception of control signals, data signals, and the like between the devices.

The database distribution device 15 loads programs (application programs, OS programs, etc.) stored in the storage unit 205, ROM, or storage medium into the RAM of the memory 203, and executes various processes under the control of the CPU 201. To do.
Note that the hardware configurations of the terminal device 9, the WEB server 11, and the application server 13 belonging to the user 5 are the same as the hardware configuration of the database distribution device 15, and thus the description thereof is omitted.

(3. Operation of database distribution device 15)
(3-1. Distributing condition: Distributing process by processing object 53 and processing type 55)
Next, the operation of the database distribution device 15 will be described with reference to FIGS. 3 and 4.

FIG. 3 is a diagram showing the distribution definition information 23.
In the distribution definition information 23, for each combination of the processing target 53 and the processing type 55, which are the distribution conditions of the processing request, a corresponding distribution destination database 57 is set. The processing target 53 is a type of information stored in the database, such as “market price information”, “authentication information”, “asset information”, and the like. The process type 55 is the content of the process for the information stored in the database, such as “reference”, “update”, “search”, and the like.

  FIG. 4 is a flowchart showing the operation of the database distribution device 15. FIG. 1 shows the configuration of the service providing system 1 to which the database distribution device 15 belongs, and FIG. 3 shows the distribution definition information 23 provided in the database distribution device 15.

  The terminal device 9 of the user 5 sends a processing request to the WEB server 11 of the service provider 3 via the network 7 (step 1001). For example, the terminal device 9 sends “reference to market price information of a predetermined stock name” to the WEB server 11 as a processing request.

  The WEB server 11 acquires the processing request and sends it to the application server 13. Since the processing request is a processing request for the database, the database distribution device 15 acquires the processing request from the application server 13 as a database processing request (step 1002).

  The database distribution device 15 detects the processing object 53 and the processing type 55 as database distribution conditions from the acquired database processing request (step 1003). “Market price information” is detected as the processing object 53 and “reference” is detected as the processing type 55.

  The distribution destination determination unit 21 of the database distribution device 15 refers to the distribution definition information 23 (FIG. 3) registered in the storage unit 205 and detects the processing target 53 (“market price information”) and the processing. Based on the type 55 (“reference”), the distribution destination database 57 is determined (step 1004). From the processing object 53 (“market price information”) and the processing type 55 (“reference”), the distribution destination database 57 to which the database processing request is distributed is determined as “database B19”.

Next, the distribution means 22 of the database distribution device 15 sends a database processing request to the determined distribution destination database 57 (step 1005).
The database distribution device 15 performs database processing on the processing target 53 (“market price information 43”) stored in the database B19 (step 1006), and returns the database processing result to the application server 13 (step 1007). That is, the database distribution device 15 refers to the market price information 43 (processing target 53) of a predetermined stock brand designated from the terminal device 9 (processing type 55), and returns the result to the application server 13.

  Note that the application server 13 may perform processing after the distribution unit 22 of the database distribution device 15 sends a database processing request to the distribution destination database 57 (step 1006 and step 1007).

  The terminal device 5 of the user 5 receives the database processing result via the application server 13 and the WEB server 11 (step 1008).

Through the above process, the database distribution device 15 distributes the processing request to the distribution request database based on the distribution definition information 23 for associating the distribution condition of the processing request for the database with the distribution destination database 57 and the processing request. 57 is determined.
As described above, the database distribution device 15 can automatically determine the distribution destination database 57 suitable for the distribution condition of the processing request for the database.

Therefore, since the distribution destination database suitable for the processing request is automatically determined from the plurality of databases, the business processing efficiency of the service provider 3 is improved. Further, since the application server 13 can execute the processing program without being influenced by the distribution destination of the database, it is possible to reduce the workload of creating and correcting the processing program of the application server 13.
Further, the addition or change of the distribution condition in the distribution destination database according to the processing request can be easily realized by the operation of adding or changing the distribution condition of the distribution definition information 23.

(3-2. Distribution conditions: distribution process with time zone 61 added)
Next, the operation of the database distribution device 15 when the time zone 61 is added to the distribution condition will be described with reference to FIGS. 5 and 6.
FIG. 5 is a diagram showing the distribution definition information 59, and FIG. 6 is a part of a flowchart showing the determination process of the distribution destination database 57. The database distribution device 15 executes the flowchart shown in FIG. 6 instead of step 1004 of the flowchart (FIG. 4).

  FIG. 5 is a diagram showing the distribution definition information 59 when the processing request distribution condition includes the time zone 61 when the processing request is acquired. The time zone 61 is added to the distribution condition of the distribution definition information 23 (FIG. 3), and distribution definition information 59 (FIG. 5) is created.

  In the distribution definition information 59, a distribution destination database 57 corresponding to each combination of the processing target 53, the processing type 55, and the time zone 61, which is the distribution condition of the processing request, is set. For example, when the processing target 53 is “market price information”, if the stock exchange is in a trading time zone, the database A17 whose market price information is updated in real time is designated as the distribution destination database 57. If the stock exchange is outside the trading time zone, the database B19 whose stored information is updated at a predetermined timing is designated as the distribution destination database 57.

Further, when the processing object 53 is “authentication information” or “assets information”, whether or not the service provider 3 is within the actual working hours (“9:00 to 17:00”) is divided by the time zone 61. The distribution destination database 57 can be set in the distribution definition information 59.
The distribution destination determination unit 21 determines the distribution destination database 57 that distributes the processing requests based on the time zone 61 acquired by the time zone acquisition unit 25 and the distribution definition information 59.

The database distribution device 15 detects the processing conditions (processing target 53 and processing type 55) from the database processing request acquired from the terminal device 9 (FIG. 4: up to step 1003). When the processing request sent from the terminal device 9 is “reference to market price information of a predetermined stock name”, “market price information” is detected as the process target 53 and “reference” is detected as the process type 55.
Next, the time zone acquisition means 25 of the database distribution device 15 acquires the time zone 61 from the current time (step 2001). It is assumed that the current time is “10:00”.

The distribution destination determination unit 21 of the database distribution device 15 refers to the distribution definition information 59 (FIG. 5) and determines the distribution destination database 57 based on the processing target 53, the processing type 55, and the time zone 61. (Step 2002). The distribution destination database 57 that distributes database processing requests from the processing object 53 (“market price information”), the processing type 55 (“reference”), and the time zone 61 (“9:00 to 11:00”) is “database A17”. To be determined.
The subsequent processing returns to step 1005 in FIG.

Through the above process, the database distribution device 15 determines the processing request distribution destination database 57 based on the distribution definition information 59 including the item of the time zone 61 and the processing request.
As described above, the database distribution device 15 can distinguish the necessity of real-time information by adding the time zone 61 to the distribution condition, and can efficiently distribute processing requests to an appropriate database. For example, the database distribution device 15 can reduce an excessive access load to the database A17 having a high real-time property by distributing database processing requests that do not require a real-time property to the database B19. Therefore, the database distribution device 15 can improve the overall processing efficiency for processing requests to the database.

(3-3. Distribution conditions: distribution processing with database load information 65 added)
Next, the operation of the database distribution device 15 when the database load information 65 is added to the distribution condition will be described with reference to FIGS. 7 and 8.
FIG. 7 is a diagram showing the distribution definition information 63, and FIG. 8 is a part of a flowchart showing the determination process of the distribution destination database 57. The database distribution device 15 executes the flowchart shown in FIG. 8 instead of step 1004 of the flowchart (FIG. 4).

  FIG. 7 is a diagram showing the distribution definition information 63 when the database load information 65 is included in the distribution condition of the processing request. The database load information 65 is added to the distribution condition of the distribution definition information 23 (FIG. 3), and the distribution definition information 63 (FIG. 7) is created.

  In the distribution definition information 63, for each combination of the processing target 53, the processing type 55, and the database load information 65 which are the distribution conditions of the processing request, a corresponding distribution destination database 57 is set. For example, the load range of the database A17 whose stored information is updated in real time is set in the database load information 65. When the number of accesses to the database A17 increases and the database load exceeds a predetermined value, the distribution destination database 57 to which processing requests are distributed can be changed.

  The distribution destination determination unit 21 determines the distribution destination database 57 to which the processing request is distributed based on the database load information 65 and the distribution definition information 63 acquired by the database load information acquisition unit 27.

  The database distribution device 15 detects the processing conditions (processing target 53 and processing type 55) from the database processing request acquired from the terminal device 9 (FIG. 4: up to step 1003). When the processing request sent from the terminal device 9 is “reference to market price information of a predetermined stock name”, “market price information” is detected as the process target 53 and “reference” is detected as the process type 55.

  Next, the database load information acquisition unit 27 of the database distribution device 15 acquires the database load information 65 from the database A17 and the database B19 (step 3001). It is assumed that the acquired load of the database A17 is “50%”.

The distribution destination determination means 21 of the database distribution device 15 refers to the distribution definition information 63 (FIG. 7), and sets the distribution destination database 57 based on the processing target 53, the processing type 55, and the database load information 65. Determination is made (step 3002). From the processing target 53 (“market price information”), the processing type 55 (“reference”), and the database load information 65 (“database A: 20 to 100%”), the distribution destination database 57 that distributes database processing requests is “database B19”. Determined.
The subsequent processing returns to step 1005 in FIG.

Through the above process, the database distribution device 15 determines a processing request distribution destination database 57 based on the distribution definition information 63 including the items of the database load information 65 and the processing request.
Thus, the database distribution device 15 can reduce the concentration of access to a specific database and the access load by adding the database load information 65 to the distribution condition and monitoring the database load information. it can.

  In addition to the database load information 65, the distribution definition information 63 may include a distribution condition related to the database failure status (hardware and software failure). As a result, the database distribution device 15 can monitor the failure status of the database and immediately remove the database in which the failure has occurred from the distribution database 57. Therefore, the database distribution device 15 can prevent a decrease in processing efficiency even if a database failure occurs.

(3-4. Distribution condition: distribution process with user attribute 69 added)
Next, the operation of the database distribution device 15 when the user attribute 69 is added to the distribution condition will be described with reference to FIGS.
FIG. 9 is a diagram showing the distribution definition information 67, and FIG. 10 is a part of a flowchart showing the determination process of the distribution destination database 57. The database distribution device 15 executes the flowchart shown in FIG. 10 instead of step 1004 of the flowchart (FIG. 4).

  FIG. 9 is a diagram showing the distribution definition information 67 when the user attribute 69 is included in the distribution condition of the processing request. The user attribute 69 is added to the distribution condition of the distribution definition information 23 (FIG. 3), and distribution definition information 67 (FIG. 9) is created.

  In the distribution definition information 67, for each combination of the processing target 53, the processing type 55, and the user attribute 69, which are the processing request distribution conditions, a corresponding distribution destination database 57 is set. For example, the user 5 having the priority right is discriminated by the user ID, and the high-order database (for example, a database having a large capacity, high real-time property, high processing speed, high-level hierarchical structure, etc.) is allocated to distribute processing requests. It can be specified in the destination database 57.

  The distribution destination determination unit 21 determines the distribution destination database 57 to which the processing request is distributed based on the user attribute 69 and the distribution definition information 69 acquired by the user attribute acquisition unit 29.

  The database distribution device 15 detects the processing conditions (processing target 53 and processing type 55) from the database processing request acquired from the terminal device 9 (FIG. 4: up to step 1003). When the processing request sent from the terminal device 9 is “reference to market price information of a predetermined stock name”, “market price information” is detected as the process target 53 and “reference” is detected as the process type 55.

  Next, the user attribute acquisition unit 29 of the database distribution device 15 acquires the user attribute 69 of the terminal device 9 that acquired the database processing request (step 4001). It is assumed that the user attribute 69 is a user ID “U050”. It is assumed that the user 5 having the priority right can be identified by the user ID, for example. For example, the user 5 with the user ID “U001 to U100” can be identified as a special user having a priority having a trading account, and the user 5 with the user ID “U101 to U500” can be identified as a general user.

The distribution destination determination unit 21 of the database distribution device 15 refers to the distribution definition information 67 (FIG. 9) and determines the distribution destination database 57 based on the processing target 53, the processing type 55, and the user attribute 69. (Step 4002). The distribution destination database 57 that distributes database processing requests from the processing object 53 (“market price information”), the processing type 55 (“reference”), and the user attribute 69 (“user ID: U001 to U100”) is assigned to “database A17”. It is determined.
The subsequent processing returns to step 1005 in FIG.

Through the above process, the database distribution device 15 determines the distribution destination database 57 of the processing request based on the distribution definition information 67 including the item of the user attribute 69 and the processing request.
Thus, the database distribution device 15 can prioritize access to the database by identifying the specific user 5 by adding the user attribute 69 to the distribution condition. Therefore, the satisfaction of the user 5 can be improved.

(3-5. Distributing condition: Distributing process with terminal device attribute 73 added)
Next, the operation of the database distribution device 15 when the terminal device attribute 73 is added to the distribution condition will be described with reference to FIGS. 11 and 12.
FIG. 11 is a diagram showing the distribution definition information 71, and FIG. 12 is a part of a flowchart showing the determination process of the distribution destination database 57. The database distribution device 15 executes the flowchart shown in FIG. 12 instead of step 1004 of the flowchart (FIG. 4).

  FIG. 11 is a diagram illustrating distribution definition information 71 when the terminal device attribute 73 is included in the distribution condition of the processing request. The terminal device attribute 73 is added to the distribution condition of the distribution definition information 23 (FIG. 3), and distribution definition information 71 (FIG. 11) is created.

  In the distribution definition information 71, for each combination of the processing target 53, the processing type 55, and the terminal device attribute 73 which are the distribution conditions of the processing request, a corresponding distribution destination database 57 is set. For example, the terminal device 9 placed in the store or branch of the service provider 3 is identified by the terminal device ID, and a higher-level database (for example, a database having a large capacity, high real-time property, high processing speed, etc.) is processed. The request can be specified in the distribution destination database 57 that distributes the request.

The distribution destination determination unit 21 determines the distribution destination database 57 to which the processing request is distributed based on the terminal device attribute 73 and the distribution definition information 71 acquired by the terminal device attribute acquisition unit 31.
As the terminal device attribute 73, a MAC (Media Access Control) address may be used as the identification ID instead of the terminal device ID.

  The database distribution device 15 detects the processing conditions (processing target 53 and processing type 55) from the database processing request acquired from the terminal device 9 (FIG. 4: up to step 1003). When the processing request sent from the terminal device 9 is “reference to market price information of a predetermined stock name”, “market price information” is detected as the process target 53 and “reference” is detected as the process type 55.

  Next, the terminal device attribute acquisition unit 31 of the database distribution device 15 acquires the terminal device attribute 73 of the terminal device 9 that acquired the database processing request (step 5001). It is assumed that the terminal device attribute 73 is a terminal device ID “S0010”. The terminal device 9 having the priority right can be identified by, for example, the terminal device ID. For example, the terminal device 9 having the terminal device ID “S0001 to S0999” is the terminal device 9 disposed at the store or branch of the service provider 3, and the terminal device 9 having the terminal device ID “T0001 to T9999” is to the general user. It can be distinguished as the terminal device 9 to which it belongs.

The distribution destination determination means 21 of the database distribution device 15 refers to the distribution definition information 71 (FIG. 11) and creates the distribution destination database 57 based on the processing object 53, the processing type 55, and the terminal device attribute 73. Determination is made (step 5002). From the processing object 53 (“market price information”), the processing type 55 (“reference”), and the terminal device attribute 73 (“terminal device ID: S0001 to S0999”), the distribution destination database 57 that distributes database processing requests is “database A17. Determined.
The subsequent processing returns to step 1005 in FIG.

Through the above process, the database distribution device 15 determines the processing request distribution destination database 57 based on the distribution definition information 71 including the item of the terminal device attribute 73 and the processing request.
As described above, the database distribution device 15 can prioritize access to the database by determining the specific terminal device 9 by adding the terminal device attribute 73 to the distribution condition. Therefore, even when access to the database is concentrated, it is possible to reduce a decrease in the business efficiency of the store 3 and the branch of the service provider 3.

(3-6. Distributing condition: Distributing process in which user 5 has a selection right)
Next, the operation of the database distribution device 15 when the user 5 has a selection right according to the distribution condition will be described with reference to FIGS. 13 to 15.
FIG. 13 is a diagram showing the distribution definition information 74, and FIG. 14 is a part of a flowchart showing the determination process of the distribution destination database 57.
FIG. 15 is a diagram showing a screen 75 displayed on the terminal device 9 of the user 5.

In the distribution definition information 74 (FIG. 13), an item for the user 5 to select the base 57 as the distribution destination data is provided. Further, the database distribution device 15 executes the flowchart shown in FIG. 14 instead of step 1004 of the flowchart (FIG. 4).
The distribution definition information 74 in FIG. 13 shows the case where the database load information 65 is added to the distribution conditions of the distribution definition information 23 (FIG. 3). The number of types of additional items of conditions is not limited.

The database distribution device 15 detects the processing conditions (processing target 53 and processing type 55) from the database processing request acquired from the terminal device 9 (FIG. 4: up to step 1003). When the processing request sent from the terminal device 9 is “reference to market price information of a predetermined stock name”, “market price information” is detected as the process target 53 and “reference” is detected as the process type 55.
Next, the database load information acquisition unit 27 of the database distribution device 15 acquires the database load information 65 from the database A17 and the database B19 (step 6001).

  The distribution destination determination means 21 of the database distribution device 15 refers to the distribution definition information 74 (FIG. 13), and determines the distribution destination database 57 based on the processing object 53, the processing type 55, and the database load information 65. Determination is made (step 6002). If the distribution database 57 is not selected by the user 5 (NO in step 6003), for example, if the processing target 53 ("market price information"), the processing type 55 ("reference"), and the load on the database A17 is "10%" For example, from the database load information 65 (“database A: 0 to 20%”), the distribution destination database 57 to which the database processing request is distributed is determined as “database A17”.

  When the load on the database A17 is “40%”, the processing load 53 (“database A:”) is obtained from the processing target 53 (“market price information”), the processing type 55 (“reference”), and the load on the database A17 is “40%”. 20 to 50% "), the distribution destination database 57 is determined to be" database A or B (user selection) ". Accordingly, the user 5 selects the distribution destination database 57 (YES in step 6003).

The distribution destination determination unit 21 displays a database selection screen 77 on the screen 75 (FIG. 15) of the terminal device 9 of the user 5. When the user 3 selects a desired database from the database selection screen 77 and clicks the “OK” button 79, the distribution destination database 57 is selected according to the intention of the user 5 (step 6004).
The subsequent processing returns to step 1005 in FIG.

Through the above process, the database distribution device 15 determines a processing request distribution destination database 57 based on the distribution definition information 74 and the processing request. The distribution destination database 57 may be selected by the user 5.
As described above, the database distribution device 15 enables the user 5 to improve user satisfaction by allowing the user 5 to select the distribution destination database 57.

(3-7. Distributing condition: Distributing process with search range 78 added)
Next, the operation of the database distribution device 15 when the search range 78 is added to the distribution condition will be described with reference to FIGS. 16 to 17.
FIG. 16 is a diagram showing the distribution definition information 76, and FIG. 17 is a part of a flowchart showing the determination process of the distribution destination database 57. The database distribution device 15 executes the flowchart shown in FIG. 17 instead of step 1004 of the flowchart (FIG. 4).

  FIG. 16 is a diagram showing the distribution definition information 76 when the search range 78 is included in the distribution condition of the processing request. The search range 78 is added to the distribution condition of the distribution definition information 23 (FIG. 3), and distribution definition information 76 (FIG. 16) is created.

  In the distribution definition information 76, for each combination of the processing target 53, the processing type 55, and the search range 78, which are the distribution conditions of the processing request, a corresponding distribution destination database 57 is set. For example, if the processing target 53 is “market price information”, the processing type 55 is “search”, and the search range 78 specified by the terminal device 9 is “after November 1, 2007”, the distribution destination to which the processing request is distributed. Database 57 is set to “Database A”.

  The database distribution device 15 detects the processing conditions (processing target 53 and processing type 55) from the database processing request acquired from the terminal device 9 (FIG. 4: up to step 1003). When the processing request sent from the terminal device 9 is “search for market price information of a predetermined stock name”, “market price information” is detected as the process target 53 and “search” is detected as the process type 55.

  Next, the database distribution device 15 acquires the designated search range 78 from the processing request sent from the terminal device 9 (step 7001). If the search range is “November 2, 2007 to November 5, 2007”, the search range 78 set in the distribution definition information 76 corresponds to “after November 1, 2007”.

The distribution destination determination means 21 of the database distribution device 15 refers to the distribution definition information 76 (FIG. 16) and determines the distribution destination database 57 based on the processing object 53, the processing type 55, and the search range 78. (Step 7002). From the processing target 53 (“market price information”), the processing type 55 (“search”), and the search range 78 (“after November 1, 2007”), the distribution destination database 57 that distributes database processing requests is “database A17”. To be determined.
The subsequent processing returns to step 1005 in FIG.

Through the above process, the database distribution device 15 determines a processing request distribution destination database 57 based on the distribution definition information 76 and the processing request.
As described above, the database distribution device 15 can quickly distribute the processing request to an appropriate database by adding the search range 78 to the distribution condition.

(4. Configuration of multiple databases)
Next, the configuration of a plurality of databases that the service provider 3 has will be described with reference to FIGS.

(4-1. Multiple derivative databases 83)
FIG. 18 is a diagram showing a plurality of derived databases 83.
The service provider 3-1 includes the WEB server 11-1, the application server 13-1, the database distribution device 15-1, the original database 81, and derived databases 83-1 to 83 that are derived from the original database 81. -4 etc. The same information as the information stored in the original database 81 is duplicated in the derived databases 83-1 to 83-4 (the duplication process is indicated by a dotted line).

  As described above, the service provider 3-1 includes the original database 81 and the plurality of derived databases 83-1 to 83-4, so that even when processing requests from a large number of terminal devices 9 are concentrated, The database distribution device 15-1 can appropriately reduce the processing efficiency by distributing the processing request to the original database 81 and the plurality of derived databases 83-1 to 83-4.

  Further, even if a problem occurs in either the original database 81 or the derived databases 83-1 to 83-4, other databases are supplemented at the time of repair, so that maintenance can be easily performed, and the service provider 3-1 A reduction in processing efficiency can be prevented.

(4-2. Multiple Derived Databases 87 with Different Types of Stored Information)
FIG. 19 is a diagram showing a plurality of derived databases 87 having different storage information types.
The service provider 3-2 includes the WEB server 11-2, the application server 13-2, the database distribution device 15-2, the original database 85, and the derived databases 87-1 to 87 derived from the original database 85. -4 etc. Information stored in the original database 85 is duplicated in the derived databases 87-1 to 87-4 for each type of stored information (duplication processing is indicated by a dotted line). For example, “market price information” is stored in the derivative database 87-1, “authentication information” is stored in the derivative database 87-2, “asset information” is stored in the derivative database 87-3, and “log information” is stored in the derivative database 87-4. Is done.

  As described above, by providing a plurality of derived databases 87-1 to 87-4 having different types of information to be stored, the database distribution device 15-2 can efficiently distribute database processing requests to appropriate databases. . In addition, since the derivative databases 87-1 to 87-4 store various information stored in the original database 85 in a distributed manner, it is not necessary to have a large capacity and high performance. There is.

(4-3. Derived database 91 having a hierarchical structure in time)
FIG. 20 is a diagram showing a derived database 91 having a temporal hierarchical structure.
The service provider 3-3 is derived from the WEB server 11-3, the application server 13-3, the database distribution device 15-3, the original database 89, and the original database 89 in a stepwise manner. Databases 91-1 to 91-3 are included (replication processing is indicated by dotted lines). Also, the derivative database 91-1 and the derivative database 93 may be created or updated simultaneously in time based on the original database 89.

  Various information stored in the derived database 91-1 is copied to the derived database 91-2 and further to the derived database 91-3 at a predetermined timing step by step over time. Accordingly, the original database 89 and the derived databases 91-1 to 91-3 are sequentially formed in a hierarchical structure.

  As described above, by providing the plurality of derived databases 91-1 to 91-3 that have a hierarchical structure in time, the database distribution device 15-3 efficiently converts the database processing request into an appropriate database according to the purpose. Can be distributed. For example, if the database processing request acquired from the user 5 has a low real-time property, the database processing request is distributed to the derived database 91-3 that is temporally down (low real-time property).

  This has the effect of improving the processing efficiency of the service provider 3-3. Further, by distributing the processing requests to an appropriate database according to the purpose of the database processing request, concentration of access to a specific database can be prevented.

(4-4. Combination of multiple databases)
Note that the service provider 3 may include a plurality of derived databases described in FIGS. 18 to 20 in appropriate combination.
For example, a plurality of derived databases 87-1 to 87-3 (FIG. 19) having different storage information types may be provided with a plurality of derived databases each having a temporal hierarchical structure.

(5. Multiple individual database distribution devices)
Next, the configuration of the database distribution device 15 included in the service provider 3 will be described with reference to FIGS. 21 and 22.

(5-1. Multiple equivalent individual database distribution devices 97)
FIG. 21 is a diagram showing a database distribution device 15-4 including a plurality of individual database distribution devices 97.
The service provider 3-4 includes a WEB server 11-4, an application server 13-4, a database distribution device 15-4, a database A17-1, and a database B19-1 (replication processing is indicated by a dotted line).

  The database distribution device 15-4 includes individual database distribution devices 97-1 to 97-3 having equivalent functions. The load balancer 95-1 distributes the database processing request sent from the application server 13-4 to the individual database distribution devices 97-1 to 97-3.

  The individual database distribution devices 97-1 to 97-3 include distribution definition information 101-1 to 101-3 for defining distribution conditions for database processing requests and distribution means 99-1 to 99-3, respectively. . The database processing request distribution processing by the individual database distribution devices 97-1 to 97-3 is the same as the processing of the database distribution device 15 described in FIG.

  Since the database distribution device 15-4 includes the individual database distribution devices 97-1 to 97-3 having the same function, the processing concentration of the distribution processing of the database processing request can be distributed. -4 processing load can be reduced. In addition, even if any of the individual database distribution devices 97-1 to 97-3 has a problem, since the other individual database distribution device 97 compensates at the time of repair, maintenance management can be easily performed. A decrease in the processing efficiency of the provider 3-4 can be prevented.

(5-2. Multiple individual database distribution devices 97 having different distribution definition information)
FIG. 22 is a diagram showing a database distribution device 15-4 including a plurality of individual database distribution devices 97 having different distribution definition information. Since the constituent elements are the same as those of the database distribution device 15-4 shown in FIG. 21, the same reference numerals are given and the description thereof is omitted.

  The database distribution device 15-4 includes a plurality of individual database distribution devices 97-1 to 97-3 having different distribution definition information 101-1 to 101-3. The load balancer 95-1 distributes the database processing request sent from the application server 13-4 to the individual database distribution devices 97-1 to 97-3.

  The distribution definition information 101-1 included in the individual database distribution device 97-1 is a setting for distributing all database processing requests to the database A17-1. For example, when access to database processing requests from a large number of terminal devices 9 is concentrated on the service provider 3-4, the load balancer 95-1 or the application server 13-4 determines the terminal device 9 having priority. The database processing request acquired from the terminal device 9 having the priority right is preferentially distributed to the individual database distribution device 97-1.

  In this way, the database distribution device 15-4 shown in FIG. 22 sends a database processing request acquired from the specific terminal device 9 to the database A17-2 with high real-time properties via the individual database distribution device 97-1. Can be preferentially assigned. Therefore, it is possible to improve the business efficiency of the specific terminal device 5 belonging to the store or branch of the service provider 3-4.

(6. Others)
As long as the database distribution device 15 is arranged between a server computer belonging to the service provider 3 and a plurality of databases, an arbitrary device configuration is possible.
For example, you may comprise the WEB server 11, the application server 13, and the database distribution apparatus 15 which are shown in FIG. 1 as one server computer.
Further, a processing program that realizes the function of the database distribution device 15 may be incorporated in the WEB server 11 or the application server 13.

  The distribution definition information 23 (FIG. 1) includes at least one of a processing target 53, a processing type 55, a time zone 61, database load information 65, a user attribute 69, a terminal device attribute 73, and a search range 78 as a distribution condition. The distribution definition information may be created by adding the above, or the distribution definition information may be created by combining a plurality of distribution conditions.

(7. Effects, etc.)
As described above in detail, the database distribution device 15 according to the embodiment of the present invention automatically determines the distribution destination database 57 suitable for the distribution condition of the processing request for the database, so that the business processing efficiency Can be improved.
In addition, the application server 13 can execute a processing program that does not depend on the database allocation destination, so that the workload of creating or correcting the processing programming of the application server 13 can be reduced.

  In addition, when the service provider 3 includes a database having high real-time characteristics and other databases, the database distribution device 15 distributes database processing requests that do not require real-time characteristics to other databases, so that the real-time characteristics can be improved. An excessive access load to a high database can be reduced. Therefore, the database distribution device 15 can improve the overall processing efficiency for the database processing request.

Further, the database distribution device 15 can reduce the concentration of access to a specific database and improve the overall processing efficiency by monitoring database load information and using it as a database distribution condition. it can.
Further, when the service provider 3 includes a higher database and other databases, the database distribution device 15 preferentially distributes the database processing requests from the specific user 5 to the higher database, so that the specific user 5 can be improved.

  In addition, the database distribution device 15 preferentially distributes database processing requests from specific terminal devices 9 arranged in the store or branch of the service provider 3 to the higher level database, so that the business of the service provider 3 is performed. The decrease in efficiency can be reduced.

In addition, the database distribution device 15 enables the user 5 to improve user satisfaction by allowing the user 5 to select the distribution destination database 57.
In addition, the service provider 3 has a plurality of databases, and the database distribution device 15 distributes database processing requests appropriately according to the characteristics of the database (real-time property, stored information type, hierarchical structure, etc.). Can be reduced.

  In addition, when the service provider 3 includes a plurality of databases, the cost burden on the equipment can be reduced if it is not necessary to increase the capacity and performance of the database derived from the original database.

  The preferred embodiments of the database distribution device according to the present invention have been described above with reference to the accompanying drawings, but the present invention is not limited to such examples. It will be apparent to those skilled in the art that various changes or modifications can be conceived within the scope of the technical idea disclosed in the present application, and these are naturally within the technical scope of the present invention. Understood.

Configuration diagram of service providing system 1 The figure which shows the hardware constitutions of the database distribution apparatus 15 The figure which shows distribution definition information 23 A flowchart showing the operation of the database distribution device 15 The figure which shows distribution definition information 59 The flowchart which shows the determination process of the distribution destination database 57 The figure which shows distribution definition information 63 The flowchart which shows the determination process of the distribution destination database 57 The figure which shows distribution definition information 67 The flowchart which shows the determination process of the distribution destination database 57 The figure which shows distribution definition information 71 The flowchart which shows the determination process of the distribution destination database 57 The figure which shows distribution definition information 74 The flowchart which shows the determination process of the distribution destination database 57 The figure which shows the database selection screen 77 The figure which shows distribution definition information 76 The flowchart which shows the determination process of the distribution destination database 57 Diagram showing multiple derivative databases 83 The figure which shows several derivative databases 87 from which storage information types differ The figure which shows the derivative database 91 which makes a hierarchical structure in time The figure which shows the database distribution apparatus 15-4 which consists of several separate database distribution apparatuses 97 The figure which shows the database distribution apparatus 15-4 which consists of several separate database distribution apparatuses 97 which have different distribution definition information

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ......... Service provision system 3, 3-1 to 3-4 ......... Service provider 5 ......... User 7 ......... Network 9 ......... Terminal device 11, 11-1 to 11-4 ... ... WEB server 13, 13-1 to 13-4 ... Application server 15, 15-1 to 15-4 ... Database allocation device 17, 17-1 ... Database A (original database)
19, 19-1 ... Database B (derived database)
21... Allocation destination determination means 22, 99-1 to 99-3... Allocation means 23, 59, 63, 67, 71, 74, 76, 101-1 to 101-3. Definition information 25 ......... Time zone acquisition means 27 ......... Database load information acquisition means 29 ......... User attribute acquisition means 31 ......... Terminal device attribute acquisition means 33, 43 ......... Market price information 35, 45 ......... Authentication information 37, 47 ......... Asset information 39, 49 ......... Log information 41, 51 ......... Registration information 53 ......... Processing target 55 ......... Processing type 57 ......... Distribution destination database 61 ......... Time zone 65... Database load information 67... User attribute 73... Terminal device attribute 75... Screen 77... Database selection screen 78 .... Search range 79 ..... OK button 81, 85, 89 ……… Original database 83-1 to 83-4, 87-1 to 87-4, 91-1 to 91-3, 93 ......... Derived database 95-1 ......... Load balancer 97-1 to 97-3 ......... Individual Database distribution device 201 ... …… CPU
203 ......... Memory 205 ......... Storage unit 207 ......... Display unit 209 ......... Input unit 211 ......... Output unit 213 ......... Communication unit 215 ......... System bus

Claims (12)

  1. A database distribution device that is connected to a plurality of databases, acquires processing requests for the databases, and distributes the processing requests to at least one of the plurality of databases,
    A distribution definition information holding means for holding distribution definition information for associating the distribution condition of the processing request with a distribution destination database;
    A distribution destination determination unit that refers to the distribution definition information and determines the distribution destination database from the plurality of databases based on the acquired processing request;
    A distribution means for distributing the acquired processing request to the determined distribution destination database;
    A database distribution device comprising:
  2. The processing request distribution condition includes a distribution condition related to at least one of a processing type or a processing target of the processing request,
    2. The distribution destination database determination unit according to claim 1, wherein the distribution destination database determination unit determines the distribution destination database by detecting at least one of the processing type and the processing target from the acquired processing request. Database sorting device.
  3. The processing request distribution condition includes a time zone, a database load, a database failure status, a search range, a distribution condition related to at least one of a user attribute or a terminal device attribute that performed the processing request,
    The distribution destination database determination means acquires information on at least one of the time zone, the database load, the attribute of the user who made the processing request, or the attribute of the terminal device, and determines the distribution destination database The database distribution device according to claim 1, wherein the database distribution device is a database distribution device.
  4. The distribution definition information holding unit further holds whether or not the distribution destination database can be selected by the user or the terminal device that has made the processing request,
    The distribution destination database determination unit, when determining that the distribution destination database can be selected, causes the user or terminal device that has made the processing request to select the distribution destination database. The database distribution device according to any one of claims 1 to 3.
  5.   5. The system according to claim 1, wherein the plurality of databases include an original database and a derived database that is derived from at least any information stored in the original database. The database distribution device according to the above.
  6.   The derived database is updated simultaneously with the original database, or is created by duplicating the original database simultaneously with the update of the original database, or is created by duplicating the original database at a predetermined timing. 6. The database distribution device according to claim 1, wherein the database distribution device is characterized in that:
  7.   7. The database according to claim 1, wherein the plurality of databases have a hierarchical structure based on a creation time of the database or an information type (market price, authentication,...) Of the database. Database sorting device.
  8. A plurality of individual database distribution devices including the distribution definition information holding unit, the distribution destination determination unit, and the distribution unit;
    The processing request is distributed to the individual database distribution device based on information on at least one of an attribute of a user who has made the processing request or an attribute of a terminal device or an attribute of a terminal device. The database distribution device according to any one of claims 1 to 7.
  9.   9. The database distribution device according to claim 8, wherein distribution definition information holding means of the plurality of individual database distribution devices hold different distribution definition information.
  10. A database distribution method in a database distribution apparatus that is connected to a plurality of databases, acquires processing requests for the databases, and distributes the processing requests to at least one of the plurality of databases,
    A distribution definition information holding step for holding distribution definition information for associating the distribution condition of the processing request with a distribution destination database;
    A distribution destination determination step of referring to the distribution definition information and determining the distribution destination database from the plurality of databases based on the acquired processing request;
    A distribution step for distributing the acquired processing request to the determined distribution destination database;
    A database distribution method comprising:
  11. A program that is connected to a plurality of databases and that can be executed in a database distribution device that acquires processing requests for the databases and distributes the processing requests to at least one of the plurality of databases,
    The database distribution device;
    A distribution definition information holding means for holding distribution definition information for associating the distribution condition of the processing request with a distribution destination database;
    A distribution destination determination unit that refers to the distribution definition information and determines the distribution destination database from the plurality of databases based on the acquired processing request;
    A distribution means for distributing the acquired processing request to the determined distribution destination database;
    Program to function as.
  12. A computer-readable recording medium that is connected to a plurality of databases, records a program that can be executed in a database distribution device that acquires processing requests for the databases and distributes the processing requests to at least one of the plurality of databases,
    The database distribution device;
    A distribution definition information holding means for holding distribution definition information for associating the distribution condition of the processing request with a distribution destination database;
    A distribution destination determination unit that refers to the distribution definition information and determines the distribution destination database from the plurality of databases based on the acquired processing request;
    A distribution means for distributing the acquired processing request to the determined distribution destination database;
    The computer-readable recording medium which recorded the program for functioning as.
JP2007296264A 2007-11-15 2007-11-15 Database distribution device, database distribution method, program, and recording medium Expired - Fee Related JP5269394B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2007296264A JP5269394B2 (en) 2007-11-15 2007-11-15 Database distribution device, database distribution method, program, and recording medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2007296264A JP5269394B2 (en) 2007-11-15 2007-11-15 Database distribution device, database distribution method, program, and recording medium

Publications (2)

Publication Number Publication Date
JP2009122966A true JP2009122966A (en) 2009-06-04
JP5269394B2 JP5269394B2 (en) 2013-08-21

Family

ID=40815054

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2007296264A Expired - Fee Related JP5269394B2 (en) 2007-11-15 2007-11-15 Database distribution device, database distribution method, program, and recording medium

Country Status (1)

Country Link
JP (1) JP5269394B2 (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2011238072A (en) * 2010-05-11 2011-11-24 Nippon Telegr & Teleph Corp <Ntt> Database management device, database system, and method and program for database management
JP2012238155A (en) * 2011-05-11 2012-12-06 Chugoku Electric Power Co Inc:The Directory information providing device, information processing system, directory information providing method, and program
JP2013080294A (en) * 2011-09-30 2013-05-02 Fujitsu Ltd Control program, data access control device, and data control method
JP2013206145A (en) * 2012-03-28 2013-10-07 Hitachi Solutions Ltd Server device and data provision system
JP2015118645A (en) * 2013-12-20 2015-06-25 株式会社野村総合研究所 Data distribution management system

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003099347A (en) * 2001-09-25 2003-04-04 Nippon Telegr & Teleph Corp <Ntt> Distributed server selecting system
JP2004110241A (en) * 2002-09-17 2004-04-08 Hitachi Kokusai Electric Inc Business supporting system
JP2004246778A (en) * 2003-02-17 2004-09-02 Nippon Telegr & Teleph Corp <Ntt> Method for load distribution of data base system, and load distribution controller, and control program for realizing this method
JP2004280528A (en) * 2003-03-17 2004-10-07 Hitachi Ltd Database system, server, inquiry inputting method, and data updating method
JP2007179300A (en) * 2005-12-28 2007-07-12 Nomura Research Institute Ltd Distribution system, distributed processing program and distributed processing method

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2003099347A (en) * 2001-09-25 2003-04-04 Nippon Telegr & Teleph Corp <Ntt> Distributed server selecting system
JP2004110241A (en) * 2002-09-17 2004-04-08 Hitachi Kokusai Electric Inc Business supporting system
JP2004246778A (en) * 2003-02-17 2004-09-02 Nippon Telegr & Teleph Corp <Ntt> Method for load distribution of data base system, and load distribution controller, and control program for realizing this method
JP2004280528A (en) * 2003-03-17 2004-10-07 Hitachi Ltd Database system, server, inquiry inputting method, and data updating method
JP2007179300A (en) * 2005-12-28 2007-07-12 Nomura Research Institute Ltd Distribution system, distributed processing program and distributed processing method

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2011238072A (en) * 2010-05-11 2011-11-24 Nippon Telegr & Teleph Corp <Ntt> Database management device, database system, and method and program for database management
JP2012238155A (en) * 2011-05-11 2012-12-06 Chugoku Electric Power Co Inc:The Directory information providing device, information processing system, directory information providing method, and program
JP2013080294A (en) * 2011-09-30 2013-05-02 Fujitsu Ltd Control program, data access control device, and data control method
JP2013206145A (en) * 2012-03-28 2013-10-07 Hitachi Solutions Ltd Server device and data provision system
JP2015118645A (en) * 2013-12-20 2015-06-25 株式会社野村総合研究所 Data distribution management system

Also Published As

Publication number Publication date
JP5269394B2 (en) 2013-08-21

Similar Documents

Publication Publication Date Title
US6587970B1 (en) Method and apparatus for performing site failover
US8122055B2 (en) Hosted multi-tenant application with per-tenant unshared private databases
US8612408B2 (en) System and method for business service management
CN101883103B (en) Method and system for client-side scaling of Web server farm architecture in a cloud data center
US5877961A (en) Electronic support work station and method of operation
US6415284B1 (en) Intelligent forms for improved automated workflow processing
AU2012308929B2 (en) Coordination engine for cloud selection
ES2230116T3 (en) Internet server salvaguarda session device.
KR101292405B1 (en) Automatically determining file replication mechanisms
US7827138B2 (en) Method and system for synchronizing a server and an on-demand database service
TWI473029B (en) Extensible and programmable multi-tenant service architecture
US20030009705A1 (en) Monitoring and synchronization of power use of computers in a network
US20100057935A1 (en) Record medium with a load distribution program recorded thereon, load distribution method, and load distribution apparatus
US7877644B2 (en) Computer application performance optimization system
US9449102B2 (en) System, method and computer program product for enabling access to a resource utilizing a token
US20040243572A1 (en) System for searching for apparatus connected to network and apparatus employed by same system, and control method therefor
US20020059427A1 (en) Apparatus and method for dynamically allocating computer resources based on service contract with user
US6480861B1 (en) Distributed adaptive computing
EP1331788B1 (en) Contents delivery network service method and system
US20030149765A1 (en) Dynamic coordination and control of network connected devices for large-scale network site testing and associated architectures
US8566654B2 (en) Debugging site errors by an admin as a guest user in a multi-tenant database environment
US20020133814A1 (en) System and method to facilitate installation of components across one or more computers
US20110276946A1 (en) Visual user interface validator
US20080263082A1 (en) Recovery segment identification in a computing infrastructure
US20030191909A1 (en) Computer system, storage and storage utilization and monitoring method

Legal Events

Date Code Title Description
A621 Written request for application examination

Free format text: JAPANESE INTERMEDIATE CODE: A621

Effective date: 20100310

A977 Report on retrieval

Free format text: JAPANESE INTERMEDIATE CODE: A971007

Effective date: 20120511

A131 Notification of reasons for refusal

Free format text: JAPANESE INTERMEDIATE CODE: A131

Effective date: 20120515

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20120612

A02 Decision of refusal

Free format text: JAPANESE INTERMEDIATE CODE: A02

Effective date: 20130108

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20130326

A911 Transfer of reconsideration by examiner before appeal (zenchi)

Free format text: JAPANESE INTERMEDIATE CODE: A911

Effective date: 20130403

TRDD Decision of grant or rejection written
A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

Effective date: 20130423

A61 First payment of annual fees (during grant procedure)

Free format text: JAPANESE INTERMEDIATE CODE: A61

Effective date: 20130508

R150 Certificate of patent or registration of utility model

Free format text: JAPANESE INTERMEDIATE CODE: R150

R250 Receipt of annual fees

Free format text: JAPANESE INTERMEDIATE CODE: R250

R250 Receipt of annual fees

Free format text: JAPANESE INTERMEDIATE CODE: R250

LAPS Cancellation because of no payment of annual fees