WO2010123168A1 - 데이터베이스 관리 방법 및 시스템 - Google Patents
데이터베이스 관리 방법 및 시스템 Download PDFInfo
- Publication number
- WO2010123168A1 WO2010123168A1 PCT/KR2009/002254 KR2009002254W WO2010123168A1 WO 2010123168 A1 WO2010123168 A1 WO 2010123168A1 KR 2009002254 W KR2009002254 W KR 2009002254W WO 2010123168 A1 WO2010123168 A1 WO 2010123168A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- query
- execution plan
- string
- identifier
- client
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2453—Query optimisation
- G06F16/24534—Query rewriting; Transformation
- G06F16/24542—Plan optimisation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24553—Query execution of query operations
- G06F16/24561—Intermediate data storage techniques for performance improvement
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
- Y10S707/99933—Query processing, i.e. searching
- Y10S707/99934—Query formulation, input preparation, or translation
Definitions
- the present invention relates to a method for managing a database, and more particularly, to a method and system for managing a database that can improve data processing speed.
- Database Management System is a system for managing a database that stores a large amount of data. It is an indispensable part of the current era when a large amount of information is created constantly. It is recognized as an element.
- DBMS DBMS
- all data is stored in a database in the form of a table, where a table is a basic structure for storing data in a database, and one table is composed of one or more records.
- each record means one row of the table, and in another term, it is also called a tuple.
- each record consists of one or more columns, where a column refers to a domain with a name that represents the real-world table items that make up the table, in other words, an attribute or field. Also called (Field).
- the DBMS When a specific query is input from the outside, the DBMS performs a function of selecting, inserting, updating, and deleting data in the database according to the input query.
- the query means what kind of request for data stored in a table of a database, that is, what kind of manipulation of data is desired, and is a structured query language (SQL). It is expressed using a language such as
- the most representative query among these SQL statements is the SELECT statement.
- the data existing in the table can be browsed, the data can be analyzed to modify the contents of the data, or the desired data can be viewed by cross-referencing the data stored in several tables.
- the execution plan for the second query statement is different from the execution plan for the first query statement.
- the conventional DBMS regenerates the execution plan for the second query statement, which reduces the efficiency of system operation.
- the present invention has been made to solve the above-mentioned problem, and generates an execution plan for a printed string generated by printing an execution value list of a query statement, and generates an execution plan for the printed string and the corresponding printed string. It is a technical problem to provide a database management method and system capable of matching and storing identifiers.
- a method of managing a database comprising: receiving, from a client, a printed string generated from a specific query statement; Determining whether the printed string is stored in a memory; If the print string is stored in the memory, and transmits the execution plan identifier that is matched and stored in the memory to the client, if the print string is not stored in the memory Generating an execution plan identifier for the execution plan of the printed character string and transmitting the generated execution plan identifier to the client; Receiving a query request consisting of the execution plan identifier and a list of execution values included in the specific query statement from the client; And providing the client with the query result obtained using the query request.
- the execution plan identifier transmitting step may include: responding to the printed string by the client; Receiving an execution plan generated by the client from the client; And generating an execution plan identifier for the received execution plan and transmitting the generated execution plan identifier to the client.
- the method may further include storing the generated execution plan identifier in the memory by matching the printed character string.
- the method may further include determining whether a query result identifier matching the query request is stored in the memory before the query result providing step.
- the query result providing step the query request When a query result identifier matching the query result is stored, the query result corresponding to the query result identifier is obtained from the memory or the disk and provided to the client.
- the query result identifier matching the query request is not stored, The query result obtained by executing an execution plan corresponding to an execution plan identifier using the execution value list may be provided to the client.
- the execution plan corresponding to the execution plan identifier is obtained by directly obtaining from the memory or decoding the execution plan in the form of a stream stored in the disk. It is characterized by.
- the method may further include generating a query table in which the printed character string, the query request, and a query result identifier for identifying a query result for the query request are matched and recorded. According to such an embodiment, the method may further include updating the query table when a table corresponding to table information included in the printed character string is changed.
- the factored string is characterized in that the execution value list included in the query statement is a string converted to a predetermined factor.
- a method of managing a database including: generating a characterized string from a query received from a user; Transmitting the printed string to a server; Receiving an execution plan identifier for the printed string from the server; Transmitting a query request consisting of the execution plan identifier and the execution value list included in the query statement to the server; And receiving a query result for the query request from the server.
- Database management system for achieving the above object is an interface module for handling the interface with the client;
- a determination module for determining whether a parameterized string generated from a query statement is stored in a memory; If the print string is stored in the memory, and transmits the execution plan identifier that is matched and stored in the memory to the client, if the print string is not stored in the memory
- An execution plan identifier management module for generating an execution plan identifier for the execution plan of the printed string and transmitting the execution plan identifier to the client;
- a query result obtaining module for obtaining a query result for the query request and providing the query request to the client when the query request including the execution plan identifier and the execution value list included in the query is received from the client.
- a database management system including: a string generation module configured to generate a string printed from a query received from a user; A query request generation module for generating a query request including an execution plan identifier and a list of execution values included in the query when the execution plan identifier for the printed string is received from a server; And an interface module for transmitting the printed character string and the query request to the server and receiving the execution plan identifier and the query result for the query request from the server.
- an execution plan is generated for a printed string generated by printing the execution value list of each query statement, and the identifier of the execution plan for the printed string and the corresponding printed string is stored. Therefore, the memory resource can be efficiently used as compared to storing all of the query statements and the identifiers of the execution plans for the queries.
- the matching string is stored in the memory without having to generate a new execution plan for the query.
- the execution speed of the system can be improved because the result of the query can be obtained by executing the execution plan.
- the present invention when a factorized string generated from a specific query statement and the execution value of the query statement are stored in the memory, it is necessary to generate a new execution plan for the query statement or to execute the generated execution plan. It is possible to further improve the speed of the system because the result value stored in matching with the string and the execution value stored in the memory can be provided as a result value for the query statement.
- FIG. 1 is a view showing the configuration of a database management system according to an embodiment of the present invention.
- FIG. 2 is a block diagram showing a detailed configuration of the client shown in FIG.
- FIG. 3 is a block diagram showing a detailed configuration of the server shown in FIG.
- FIG. 4 is a flowchart showing a database management method according to an embodiment of the present invention.
- FIG. 1 is a view showing the configuration of a database management system according to an embodiment of the present invention.
- the database management system 100 may include a client 110 and a server 120, which may be connected to the database 140 to record data recorded in the database 140. It performs a function to integrally manage the database 140, such as updating or deleting or adding data to the database 140.
- the client 110 receives a query from a user, generates an execution plan for the corresponding query, and transmits the generated query to the server 120.
- the query analysis module 111 As illustrated in FIG. 2, the query analysis module 111, a string generation module 112, an execution plan generation module 114, a query request generation module 116, and a server interface module 118.
- the query analysis module 111 analyzes the query by receiving a query from a user, parsing the received query, and performing a semantic check.
- the query statement refers to a string in which a data retrieval request for retrieving data satisfying a specific condition is defined from a specific table stored in the database 140.
- such a query statement may be generated using Structured Query Language (SQL) syntax.
- SQL Structured Query Language
- a query statement in which a request for retrieving information of an employee corresponding to a specific employee number from the database 140 is defined in SQL syntax may be as follows.
- the string generation module 112 generates a characterized string from the query analyzed by the query analysis module 112.
- the string generation module 112 may express the execution value list (constant value list) such as constants or binding variables (Variables) in the query analyzed by the query analysis module 112. By printing a plurality of execution values) into a predetermined argument to generate a printed string.
- the reason why the string generation module 112 generates the string that is printed from the specific query statement is that a large amount of resource consumption may occur because the execution list is generated for each of the different query statements.
- an execution plan is generated for a generalized string in which the execution value list is converted to a specific argument, only the execution value list needs to generate one execution plan for each different query statement. This is because the resource consumption for generating the plan can be prevented.
- the string generation module 112 transmits the generated string to the server 120 through the interface module 118 to determine whether the server 120 is required to generate an execution plan for the string to be printed. To help.
- the execution plan generation module 114 when the response to the print string is received from the server 120 to be described later, the execution plan generation module 114 generates an execution plan for the print string.
- the execution plan refers to a data structure including a method of fetching a tuple corresponding to a specific condition from a specific table, a drawing order, and the like.
- the response to the printed string may be transmitted from the server 120 through the interface module 118 when it is determined that the printed string is not stored in the server 120.
- That is, that the printed string is stored in the server 120 means that an execution plan has already been generated for the printed string, and the printed string is not stored in the server 120. You need to create an action plan.
- the execution plan generation module 114 may determine to generate an execution plan for the corresponding characterized string when Null is received in response to the transmission of the characterized string from the server 120.
- the query request generation module 116 receives, via the interface module 118, the execution plan identifier for the string printed in response to the transmission of the string printed from the server 120 or in response to the execution plan transmission.
- the query request is generated using the execution plan identifier transmitted from the server 120 and the execution value list included in the query received through the query analysis module 111.
- the execution plan identifier for the printed string if the printed string is stored in the server 120, the execution plan identifier for the printed string is returned in response to the transmission of the printed string. If it is provided directly by 120, but the print string is not stored in the server 120, the execution plan generation module 114 generates an execution plan for the print string, and transmits it to the server 120. Only when the execution plan identifier for the corresponding execution plan can be generated and provided by the server 120.
- the query request generation module 116 may generate an execution plan identifier transmitted from the server 120 and a list of execution values included in the query in a pair format.
- the query request generation module 116 transmits a pair request form such as ⁇ P, 2106 ⁇ to the server 120.
- the query request generation module 116 can greatly reduce the amount of information included in the query request, compared to the existing method of transmitting the execution plan itself as a query request. Network load can be reduced.
- the interface module 118 is responsible for the interface with the server 120, and transmits the printed string generated by the string generation module 112 described above to the server 120, the server 120 Receive a response to a string transfer sent from.
- the response to the transmission of the printed string is an execution plan identifier for the printed string when the printed string is stored in the server 120 as described above, and the printed string is the server 120. If not stored in the response may be.
- the interface module 118 When the interface module 118 receives a response to the transmission of the printed string from the server 120, the interface module 118 transmits it to the execution plan generation module 114 described above, and when the execution plan identifier is transmitted, the query request generation module 116. Transmits the execution plan identifier.
- the interface module 118 converts the execution plan generated by the execution plan generation module 114 into a stream form and transmits it to the server 120, and generates the execution plan by the execution plan generation module 114 from the server 120.
- the execution plan identifier for the executed execution plan is received and transmitted to the query request generation module 116.
- the interface module 118 transmits the query request generated by the query request generation module 116 to the server 120, receives a query result corresponding to the query request from the server 120, and provides the query result to the user.
- the client 110 including each of the above-described modules may be programmed and installed on a user terminal (not shown). However, in a modified embodiment, the client 110 may be installed on the server 120. .
- the server 120 stores and executes the execution plan generated by the client 110 as described above, and provides the client 110 with query results obtained by executing the execution plan. Perform.
- the server 120 includes a determination module 122, an execution plan identifier management module 124, a query result obtaining module 126, a query table generating module 128, and an interface module 130. , Memory 132, and disk 134.
- the determination module 122 determines whether the printed string received from the client 110 described above is recorded in the management table of the memory 132 and transmits the result to the execution plan identifier management module 122 which will be described later. do. That is, the determination module 122 determines whether the printed string received from the client 110 is a string previously received.
- the determination module 122 may determine whether a character string generated in the query table generation module 128, which will be described later, exists in the query table stored in the memory 132.
- execution plan identifier management module 124 determines that the string printed by the determination module 122 is stored in the query table, the execution plan identifier which is matched with the printed string on the query table will be described later. It transmits to the client 110 through the interface module 130.
- the fact that the parameterized string is stored in the query table means that the execution string and the execution plan identifier for the parameterized string have already been generated because the characterization string is a previously received string.
- the execution plan identifier management module 124 provides the client 110 with an execution plan identifier which is matched with the corresponding string and stored.
- the execution plan identifier management module 124 transmits the response.
- the execution plan identifier management module 124 may send a null to the client 110 in response to the transmission of the printed string.
- the execution plan identifier management module 124 sends the execution plan in the form of a stream received from the client 110 to the disk 134 in the form of a file. Save and generate an identification plan identifier for the execution plan to transmit to the client (110).
- the execution plan identifier management module 124 may determine the identifier of the file in which the execution plan is stored as the identification plan identifier.
- the execution plan identifier management module 124 transmits the generated execution plan identifier to the query table management module 128, which will be described later, so that the execution plan identifier may be matched with the printed string and recorded on the query table.
- the query result obtaining module 126 obtains a query result for the query request transmitted from the client 110 and provides the query result to the client 110 through the client interface module 130.
- the query request means text in which the execution plan identifier for the corresponding parameterized string and the execution value list included in the query statement are defined in pair form as described above, and the query result is one tuple or a plurality of tuples. It can be a set.
- the query result obtaining module 126 determines whether a query result identifier matching the query request received from the client 110 is recorded in the query table stored in the memory 132, and is matched with the query request. When the query result identifier is recorded in the query table, the query result corresponding to the query result identifier is obtained from the memory 132 or the disk 134 and provided to the client 110.
- the fact that the query result identifier matching the query request is stored in the query table means that the query request is a previously entered query request.
- the query result for the query request is stored in the memory 132 or the disk 134. Because it is already stored in), it is not necessary to decode the execution plan stored in the disk 134 or to execute the decoded execution plan in order to obtain a query result for the query request.
- the present invention can improve the data search speed because the query result previously generated for the query request can be used.
- the query result obtaining module 26 determines whether an execution plan corresponding to the execution plan identifier included in the query request is stored in the memory 132. To judge.
- the query result obtaining module 126 reads the execution plan in the form of a stream corresponding to the execution plan identifier included in the query request from the disk 134. Decode and store in memory 132. Thereafter, the query result is obtained from the database 140 and stored in the disk 134 by executing the decoded execution plan by using the execution value list included in the query request.
- the query result from the database 140 is executed by executing the execution plan already stored on the memory 132 using the execution value list included in the query request. To obtain and store in the disk 134.
- the query result obtaining module 126 generates the query result identifier for the query result in storing the obtained query result on the disk 134. By providing the query result identifier on the query table.
- the query result identifier matching the query request is not stored in the query table, it means that the query request is the first input query request. Therefore, the query result for the query request is stored in the query request. It is obtained by using the execution plan corresponding to the execution plan identifier included and the execution value list included in the query request.
- the present invention does not generate a new execution plan to obtain a query result for a query request even if a query result identifier matching the query request is not recorded in the query table. Since the previous execution plan stored in) can be used as it is, the performance of the database management system 110 can be improved.
- the query table management module 128 includes the printed string transmitted from the client 110, the execution plan identifier generated by the execution plan identifier management module 124 for the corresponding printed string, and the query statement.
- the execution value list and the query result identifier for the query request are matched and recorded on the query table stored in the memory 132.
- the query table management module 128 may update the query table when a new printed string is received or when a new query result identifier is generated according to the reception of a new execution value list.
- the query table management module 128 may include ⁇ factored string, execution plan identifier, ⁇ 1 st execution value list, 1 st query result identifier ⁇ , ⁇ 2 nd execution value list, etc., for each characterized string.
- 2 nd query result identifier ⁇ ,. , ⁇ N st execution value list, N st query result identifier ⁇ can be written on the query table.
- the query table management module 128 matches and stores an execution plan identifier, an execution value list, and a query result identifier for each parameterized string generated by printing the execution value list of each query statement. Therefore, memory resources can be used efficiently.
- the interface module 130 is responsible for the interface function with the client 110, receives the characterized string from the client 110 and transmits to the determination module 122 and the query table management module 128, In response thereto, an execution plan identifier matching the printed string or an execution plan generation request for the printed string is received from the execution plan identifier generation module 124 and provided to the client 110.
- the interface module 130 receives the execution plan for the string string printed from the client 110 and transmits the execution plan to the execution plan identifier management module 124, and generates the execution plan generated by the execution plan identifier management module 124.
- the identifier is sent to the client 110.
- the interface module 130 receives a query request composed of an execution plan identifier and an execution value list from the client 110, transmits the query request to the query result obtaining module 126, and is obtained by the query result obtaining module 126.
- the query result is provided to the client 110.
- the query table generated by the query table generating module 128 described above is recorded, the execution plan decoded by the query result obtaining module 126 is stored, and the query result obtaining module 126 is decoded.
- the query result of executing the executed execution plan using the execution value list is stored.
- the memory 132 may store only N execution plans or query results that have been recently used among execution plans or query results.
- the disk 134 stores the execution plan transmitted from the client 110 and the query results for the query request.
- the database 110 stores various types of data in a table format.
- Each table may include one or more tuples, and each tuple may include one or more columns.
- a table means a set of information about employees
- a tuple means information corresponding to each employee
- a column indicates the employee's number
- It means the area where the name of the employee, the position of the employee, and the salary of the employee are stored.
- the determination module 122 determines whether the printed string is recorded on the query table of the memory 132. Assuming that the parameterized string is not recorded on the query table, the execution plan identifier management module 124 transmits the response to the execution plan generation module 114.
- the execution plan generation module 114 generates an execution plan for the corresponding characterized string and transmits the execution plan to the execution plan identifier management module 124
- the execution plan identifier management module 124 transmits the execution plan to the disk 134.
- the execution plan identifier management module 124 generates an execution plan identifier "P" in the execution plan and transmits it to the query request generation module 116.
- the query request generation module 116 uses the execution plan identifier "P" transmitted from the execution plan identifier management module 124 and the execution value list "2106" included in the query statement, such as ⁇ P, 2106 ⁇ .
- a pair type query request is generated and transmitted to the query result obtaining module 126.
- the query result obtaining module 126 determines whether there is a query result identifier matching the received query request in the query table.
- the query result for the query does not exist in the memory 132 or the disk 134, so that the query result obtaining module 126 may execute the execution plan identifier from the disk 134.
- Read the execution plan corresponding to "P” decode and store it in the memory 132, and then execute the decoded execution plan using the execution value list 2106 to obtain a query result and obtain the obtained query result from the client 110. To send).
- the query result obtaining module 126 assigns the query result identifier R1 to the obtained query result and stores the obtained query result in the disk 134.
- the query request generation module 116 generates a pair request form such as ⁇ P, 100 ⁇ using the execution plan identifier "P" and the execution value list "100" included in the query to obtain the query result. Send to module 126.
- the query result obtaining module 126 determines whether there is a query result identifier matching the received query request in the query table. As a result of the determination, there is no query result identifier matching the query request, but since the execution plan corresponding to the execution plan identifier "P" is already stored in the memory 132, the execution plan identifier "P" from the disk 134. There is no need to read the action plan.
- the query result obtaining module 126 executes the execution plan stored in the memory 132 using the execution value list 100 to obtain the query result and transmits the query result to the client 100.
- the query result obtaining module 126 assigns the query result identifier R2 to the obtained query result and then stores the obtained query result in the disk 134.
- the query request generation module 116 generates a pair request form such as ⁇ P, 1206 ⁇ by using the execution plan identifier "P" and the execution value list "2106" included in the query to obtain the query result. Send to module 126.
- the query result obtaining module 126 determines whether there is a query result identifier matching the received query request in the query table. As a result of the determination, since the query result identifier R1 matching the query request ⁇ P, 1206 ⁇ is recorded on the query table, the query result obtaining module 126 retrieves the query result corresponding to the query result identifier R1 from the disk 134. After reading and storing the result in the memory 132, the query result is provided to the client 110.
- the client receives a query from the user and analyzes (S400).
- the query statement may be written in SQL syntax, and the analysis of such query means parsing and semantic check of the query.
- the client generates a characterized string from the analyzed query (S402).
- the string generation module 112 may generate a string that is printed by converting a list of execution values, such as constants or binding variables, into predetermined arguments in the query analyzed by the query analysis module 112. Can be.
- the server determines whether the printed string is recorded on the query table (S406).
- the server may send a null in response to the string transfer sent to the client.
- the client generates an execution plan for the corresponding characterized string (S410), and transmits the generated execution plan to the server (S412).
- the client may convert the generated execution plan into a stream form and transmit it to the server.
- the server stores the received execution plan on the disk (S414), and generates an execution plan identifier for the stored execution plan (S415).
- the generated identifier may be matched with the corresponding factorized string and recorded in the query table.
- the server transmits the generated execution plan identifier to the client (S416).
- the execution plan identifier that matches the recorded string on the query table and is recorded is transmitted to the client (S416).
- the client when the execution plan identifier is transmitted from the server, the client generates a query request consisting of the execution plan identifier and the execution value list included in the query (S418), and transmits the generated query request to the server (S420). ).
- the client in generating the query request, the client may generate the execution plan identifier transmitted from the server and the execution value list included in the query in pair form.
- the amount of information included in the query request can be greatly reduced compared to the existing method of transmitting the execution plan itself as the query request, thereby reducing the network load generated when a large amount of data is inquired.
- the server determines whether a query result identifier matching the query request exists in the query table (S422). As a result of determination, when a query result identifier matching the query request exists, after obtaining a query result corresponding to the query result identifier on a memory or a disk (S424), the obtained query result is transmitted to the client (S426).
- the obtained query result when obtaining the query result from the disk, the obtained query result may be stored in the memory and then the obtained query result may be transmitted to the client.
- the execution plan corresponding to the execution plan identifier is not stored in the memory
- the execution plan corresponding to the execution plan identifier on the disk is read, decoded, and stored in the memory (S430). Thereafter, the execution plan stored in the memory is executed using the execution value list included in the query request to obtain the query result and then stored in the disk (S432).
- a query result identifier for identifying the query result may be generated, and the generated query result identifier may be matched with the query request on the query table and recorded. Thereafter, the obtained query result is transmitted to the client (S426).
- the execution plan corresponding to the execution plan identifier is stored in the memory as a result of the determination in S428, the execution result stored in the memory is executed by using the execution value list included in the query request. After the acquisition, the obtained query result is stored in the disk (S430).
- a query result identifier for identifying the query result may be generated, and the generated query result identifier may be matched with the query request on the query table and recorded. Thereafter, the obtained query result is transmitted to the client (S426).
- the above-described database management method can be implemented in the form of program instructions that can be executed by various computer means and recorded in a computer-readable recording medium.
- the computer-readable recording medium may include program instructions, data files, data structures, and the like, alone or in combination.
- the program instructions recorded on the recording medium may be those specially designed and configured for the present invention, or may be known and available to those skilled in computer software.
- Computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tape, optical media such as CD-ROMs, DVDs, and magnetic disks such as floppy disks. Magnetic-Optical Media, and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like.
- the recording medium may be a transmission medium such as an optical or metal wire, a waveguide, or the like including a carrier wave for transmitting a signal specifying a program command, a data structure, or the like.
- program instructions include not only machine code generated by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like.
- the hardware device described above may be configured to operate as one or more software modules to perform the operations of the present invention, and vice versa.
- the database management system is described as being configured as a client as a server, but in the modified embodiment, the client and the server are physically implemented as a server, or some components of the client are included in the server In addition, some components of the server may be implemented to be included in the client.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computational Linguistics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Operations Research (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
Claims (25)
- 특정 질의문으로부터 생성된 인자화된 문자열을 클라이언트로부터 수신하는 단계;상기 인자화된 문자열이 메모리에 저장되어 있는지 여부를 판단하는 단계;상기 인자화된 문자열이 상기 메모리에 저장되어 있으면 상기 메모리에 상기 인자화된 문자열과 매칭되어 저장되어 있는 실행계획 식별자를 상기 클라이언트로 전송하고, 상기 인자화된 문자열이 상기 메모리에 저장되어 있지 않으면 상기 인자화된 문자열의 실행계획에 대한 실행계획 식별자를 생성하여 상기 클라이언트로 전송하는 단계;상기 클라이언트로부터 상기 실행계획 식별자와 상기 특정 질의문에 포함된 실행 값 리스트로 구성되는 질의요청을 수신하는 단계; 및상기 질의요청을 이용하여 획득되는 질의결과를 상기 클라이언트로 제공하는 단계를 포함하는 것을 특징으로 하는 데이터베이스 관리 방법.
- 제1항에 있어서, 상기 인자화된 문자열이 상기 메모리에 저장되어 있지 않은 경우 상기 실행계획 식별자 전송단계는,상기 클라이언트에게 상기 인자화된 문자열에 대해 응답하는 단계;상기 클라이언트에 의해 생성된 실행계획을 상기 클라이언트로부터 수신하는 단계; 및상기 수신된 실행계획에 대한 실행계획 식별자를 생성하여 상기 클라이언트로 전송하는 단계를 포함하는 것을 특징으로 하는 데이터베이스 관리 방법.
- 제1항에 있어서,상기 생성된 실행계획 식별자를 상기 인자화된 문자열과 매칭시켜 상기 메모리에 저장하는 단계를 더 포함하는 것을 특징으로 하는 데이터베이스 관리 방법.
- 제1항에 있어서,상기 질의결과 제공 단계 이전에, 상기 메모리에 상기 질의요청과 매칭되는 질의결과 식별자가 저장되어 있는지 여부를 판단하는 단계를 더 포함하고,상기 질의결과 제공 단계에서, 상기 질의요청에 매칭되는 질의결과 식별자가 저장되어 있는 경우 상기 질의결과 식별자에 상응하는 질의결과를 상기 메모리 또는 디스크로부터 획득하여 상기 클라이언트로 제공하고,상기 질의요청에 매칭되는 질의결과 식별자가 저장되어 있지 않은 경우 상기 실행계획 식별자에 상응하는 실행계획을 상기 실행 값 리스트를 이용하여 실행함으로써 획득되는 질의결과를 상기 클라이언트로 제공하는 것을 특징으로 하는 데이터베이스 관리 방법.
- 제4항에 있어서,상기 질의요청에 매칭되는 질의결과 식별자가 저장되어 있지 않은 경우 상기 실행계획 식별자에 상응하는 실행계획은, 상기 메모리로부터 직접 획득하거나 상기 디스크에 저장되어 있는 스트림 형태의 실행계획을 디코딩 함으로써 획득되는 것을 특징으로 하는 데이터베이스 관리 방법.
- 제4항에 있어서,상기 실행계획을 실행함으로써 획득되는 질의결과를 식별하기 위한 질의결과 식별자를 생성하는 단계; 및상기 질의결과 식별자, 상기 질의요청, 및 상기 인자화된 문자열을 서로 매칭시켜 상기 메모리에 저장하는 단계를 더 포함하는 것을 특징으로 하는 데이터베이스 관리 방법.
- 제1항에 있어서,상기 인자화된 문자열, 상기 질의요청, 및 상기 질의요청에 대한 질의결과 식별을 위한 질의결과 식별자가 매칭되어 기록되는 질의 테이블을 생성하는 단계를 더 포함하는 것을 특징으로 하는 데이터베이스 관리 방법.
- 제7항에 있어서,상기 인자화된 문자열에 포함되어 있는 테이블 정보에 상응하는 테이블이 변경되면, 상기 질의 테이블을 갱신하는 단계를 더 포함하는 것을 특징으로 하는 데이터베이스 관리 방법.
- 제1항에 있어서,상기 인자화된 문자열은 상기 질의문에 포함된 실행 값 리스트가 미리 정해진 인자로 변환된 문자열인 것을 특징으로 하는 데이터베이스 관리 방법.
- 사용자로부터 수신되는 질의문으로부터 인자화된 문자열을 생성하는 단계;상기 인자화된 문자열을 서버로 전송하는 단계;상기 서버로부터 상기 인자화된 문자열에 대한 실행계획 식별자를 수신하는 단계;상기 실행계획 식별자와 상기 질의문에 포함된 실행 값 리스트로 구성되는 질의요청을 상기 서버로 전송하는 단계; 및상기 질의요청에 대한 질의결과를 상기 서버로부터 수신하는 단계를 포함하는 것을 특징으로 하는 데이터베이스 관리 방법.
- 제10항에 있어서,상기 인자화된 문자열은 상기 질의문에 포함된 실행 값 리스트를 미리 정해진 인자로 변환함으로써 생성하는 것을 특징으로 하는 데이터베이스 관리 방법.
- 제10항에 있어서, 상기 실행계획 식별자 수신 단계 이전에,상기 서버로부터 상기 인자화된 문자열에 대한 응답이 수신되면 상기 인자화된 문자열에 대한 실행계획을 생성하는 단계; 및상기 생성된 실행계획을 상기 서버로 전송하는 단계를 더 포함하는 것을 특징으로 하는 데이터베이스 관리 방법.
- 제12항에 있어서,상기 인자화된 문자열에 대한 응답은, 상기 서버에 상기 인자화된 문자열과 상기 인자화된 문자열에 대한 실행계획 식별자가 매칭되어 저장되어 있지 않은 경우 상기 서버로부터 수신되는 것을 특징으로 하는 데이터베이스 관리 방법.
- 제1항 내지 제13항 중 어느 하나의 항에 기재된 방법을 수행하기 위한 프로그램이 기록된 기록매체.
- 클라이언트와의 인터페이스를 담당하는 인터페이스 모듈;질의문으로부터 생성된 인자화된 문자열이 메모리에 저장되어 있는지 여부를 판단하는 판단 모듈;상기 인자화된 문자열이 상기 메모리에 저장되어 있으면 상기 메모리에 상기 인자화된 문자열과 매칭되어 저장되어 있는 실행계획 식별자를 상기 클라이언트로 전송하고, 상기 인자화된 문자열이 상기 메모리에 저장되어 있지 않으면 상기 인자화된 문자열의 실행계획에 대한 실행계획 식별자를 생성하여 상기 클라이언트로 전송하는 실행계획 식별자 관리 모듈; 및상기 실행계획 식별자와 상기 질의문에 포함된 실행 값 리스트로 구성되는 질의요청이 상기 클라이언트로부터 수신되면, 상기 질의요청에 대한 질의결과를 획득하여 상기 클라이언트로 제공하는 질의결과 획득모듈을 포함하는 것을 특징으로 하는 데이터베이스 관리 시스템.
- 제15항에 있어서, 상기 실행계획 식별자 관리 모듈은,상기 인자화된 문자열이 상기 메모리에 저장되어 있지 않은 경우 상기 클라이언트로 상기 인자화된 문자열에 대한 응답을 전송하고, 상기 클라이언트로부터 상기 실행계획이 수신되면, 상기 수신된 실행계획에 실행계획 식별자를 부여하여 상기 클라이언트로 전송하는 것을 특징으로 하는 데이터베이스 관리 시스템.
- 제15항에 있어서, 상기 질의결과 획득 모듈은,상기 메모리에 상기 질의요청과 매칭되는 질의결과 식별자가 저장되어 있는지 여부를 판단하고,상기 질의요청에 매칭되는 질의결과 식별자가 저장되어 있으면 상기 질의결과 식별자에 상응하는 질의결과를 상기 메모리 또는 디스크로부터 획득하여 상기 클라이언트로 제공하고,상기 질의요청에 매칭되는 질의결과 식별자가 저장되어 있지 않으면 상기 실행계획 식별자에 상응하는 실행계획을 상기 실행 값 리스트를 이용하여 실행함으로써 획득되는 질의결과를 상기 클라이언트로 제공하는 것을 특징으로 하는 데이터베이스 관리 시스템.
- 제17항에 있어서, 상기 질의결과 획득 모듈은,상기 질의요청에 매칭되는 질의결과 식별자가 저장되어 있지 않은 경우 상기 메모리로부터 상기 실행계획 식별자에 상응하는 실행계획을 직접 획득하거나, 상기 디스크에 저장되어 있는 스트림 형태의 실행계획을 디코딩 함으로써 상기 실행계획 식별자에 상응하는 실행계획을 획득하는 것을 특징으로 하는 데이터베이스 관리 시스템.
- 제17항에 있어서,상기 질의결과 획득 모듈은, 상기 실행계획을 실행함으로써 획득되는 질의결과를 식별하기 위한 질의결과 식별자를 생성하는 것을 특징으로 하는 데이터베이스 관리 시스템.
- 제15항에 있어서,상기 인자화된 문자열, 상기 질의요청, 및 상기 질의결과를 식별하기 위한 질의결과 식별자가 매칭되어 기록되는 질의 테이블을 생성하여 상기 메모리에 저장하는 질의 테이블 관리 모듈을 더 포함하는 것을 특징으로 하는 데이터베이스 관리 시스템.
- 제20항에 있어서,상기 질의 테이블 관리 모듈은, 상기 인자화된 문자열에 포함되어 있는 테이블 정보에 해당하는 테이블이 변경되면, 상기 질의 테이블을 갱신하는 것을 특징으로 하는 데이터베이스 관리 시스템.
- 사용자로부터 수신된 질의문으로부터 인자화된 문자열을 생성하는 문자열 생성 모듈;서버로부터 상기 인자화된 문자열에 대한 실행계획 식별자가 수신되면, 상기 실행계획 식별자와 상기 질의문에 포함된 실행 값 리스트로 구성되는 질의요청을 생성하는 질의요청 생성 모듈; 및상기 인자화된 문자열 및 상기 질의요청을 상기 서버로 전송하고, 상기 서버로부터 상기 실행계획 식별자 및 상기 질의요청에 대한 질의결과를 수신하는 인터페이스 모듈을 포함하는 것을 특징으로 하는 데이터베이스 관리 시스템.
- 제22항에 있어서,상기 문자열 생성 모듈은, 상기 질의문에 포함된 실행 값 리스트를 미리 정해진 인자로 변환함으로써 상기 인자화된 문자열을 생성하는 것을 특징으로 하는 데이터베이스 관리 시스템.
- 제22항에 있어서,상기 서버로부터 상기 인자화된 문자열에 대한 응답이 수신되면 상기 인자화된 문자열에 대한 실행계획을 생성하는 실행계획 생성 모듈을 더 포함하고,상기 인터페이스 모듈은, 상기 서버로부터 상기 인자화된 문자열에 대한 응답을 수신하고, 상기 생성된 실행계획을 상기 서버로 전송하는 것을 특징으로 하는 데이터베이스 관리 시스템.
- 제24항에 있어서,상기 인자화된 문자열에 대한 응답은, 상기 서버에 상기 인자화된 문자열과 상기 인자화된 문자열에 대한 실행계획 식별자가 매칭되어 저장되어 있지 않은 경우 상기 서버로부터 수신되는 것을 특징으로 하는 데이터베이스 관리 시스템.
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/265,984 US8661022B2 (en) | 2009-04-24 | 2009-04-29 | Database management method and system |
JP2012507131A JP5600736B2 (ja) | 2009-04-24 | 2009-04-29 | データベース管理方法およびシステム |
US14/162,353 US9753977B2 (en) | 2009-04-24 | 2014-01-23 | Method and system for managing database |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020090036163A KR101083563B1 (ko) | 2009-04-24 | 2009-04-24 | 데이터베이스 관리 방법 및 시스템 |
KR10-2009-0036163 | 2009-04-24 |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/265,984 A-371-Of-International US8661022B2 (en) | 2009-04-24 | 2009-04-29 | Database management method and system |
US14/162,353 Division US9753977B2 (en) | 2009-04-24 | 2014-01-23 | Method and system for managing database |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2010123168A1 true WO2010123168A1 (ko) | 2010-10-28 |
Family
ID=43011268
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2009/002254 WO2010123168A1 (ko) | 2009-04-24 | 2009-04-29 | 데이터베이스 관리 방법 및 시스템 |
Country Status (4)
Country | Link |
---|---|
US (2) | US8661022B2 (ko) |
JP (1) | JP5600736B2 (ko) |
KR (1) | KR101083563B1 (ko) |
WO (1) | WO2010123168A1 (ko) |
Families Citing this family (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9171039B2 (en) * | 2011-09-29 | 2015-10-27 | Sap Se | Query language based on business object model |
US9229983B2 (en) | 2012-11-30 | 2016-01-05 | Amazon Technologies, Inc. | System-wide query optimization |
KR101542299B1 (ko) * | 2013-02-18 | 2015-08-07 | 단국대학교 산학협력단 | 하둡 기반의 질의 처리 방법 및 장치 |
CN103577561B (zh) * | 2013-10-24 | 2017-12-01 | 华为技术有限公司 | 执行计划的存储方法、装置及系统 |
US10394808B2 (en) * | 2015-02-26 | 2019-08-27 | International Business Machines Corporation | Database query execution tracing and data generation for diagnosing execution issues |
EP3140753A4 (en) * | 2015-03-28 | 2017-06-07 | Huawei Technologies Co. Ltd. | A system and method to optimize queries on a view |
CN107180017B (zh) * | 2016-03-11 | 2021-05-28 | 阿里巴巴集团控股有限公司 | 一种样本序列化方法和装置 |
JP6669571B2 (ja) * | 2016-04-19 | 2020-03-18 | 株式会社シスバンク | リレーショナルデータベースのチューニング装置及び方法 |
US10417229B2 (en) * | 2017-06-27 | 2019-09-17 | Sap Se | Dynamic diagonal search in databases |
CN111949631A (zh) * | 2019-05-14 | 2020-11-17 | 华为技术有限公司 | 一种确定数据库的配置参数的方法及装置 |
CN110727835B (zh) * | 2019-10-17 | 2021-03-12 | 浙江中智达科技有限公司 | 数据查询方法、装置及系统 |
CN113872788A (zh) * | 2020-06-30 | 2021-12-31 | 中兴通讯股份有限公司 | 数据库配置参数调整方法、设备及存储介质 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6356887B1 (en) * | 1999-06-28 | 2002-03-12 | Microsoft Corporation | Auto-parameterization of database queries |
EP1585036A2 (en) * | 2004-04-08 | 2005-10-12 | International Business Machines Corporation | Management of parameterized database queries |
Family Cites Families (47)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH1049539A (ja) * | 1996-07-31 | 1998-02-20 | Matsushita Electric Ind Co Ltd | データベース管理システム |
US6115703A (en) * | 1998-05-11 | 2000-09-05 | International Business Machines Corporation | Two-level caching system for prepared SQL statements in a relational database management system |
US20010051956A1 (en) * | 1998-09-29 | 2001-12-13 | Paul Bird | Global caching and sharing of sql statements in a heterogeneous application environment |
US7080062B1 (en) * | 1999-05-18 | 2006-07-18 | International Business Machines Corporation | Optimizing database queries using query execution plans derived from automatic summary table determining cost based queries |
US6466931B1 (en) * | 1999-07-30 | 2002-10-15 | International Business Machines Corporation | Method and system for transparently caching and reusing query execution plans efficiently |
US6601064B1 (en) * | 1999-11-24 | 2003-07-29 | Ncr Corporation | Method and apparatus for fetching array based objects by direct delivery and batching |
US6526403B1 (en) * | 1999-12-17 | 2003-02-25 | International Business Machines Corporation | Method, computer program product, and system for rewriting database queries in a heterogenous environment |
US6721724B1 (en) * | 2000-03-31 | 2004-04-13 | Microsoft Corporation | Validating multiple execution plans for database queries |
US20020107835A1 (en) * | 2001-02-08 | 2002-08-08 | Coram Michael T. | System and method for adaptive result set caching |
IL141599A0 (en) * | 2001-02-22 | 2002-03-10 | Infocyclone Inc | Information retrieval system |
US6925457B2 (en) * | 2001-07-27 | 2005-08-02 | Metatomix, Inc. | Methods and apparatus for querying a relational data store using schema-less queries |
JP4162184B2 (ja) * | 2001-11-14 | 2008-10-08 | 株式会社日立製作所 | データベース管理システムの実行情報を取得する手段を有する記憶装置 |
US6985904B1 (en) * | 2002-02-28 | 2006-01-10 | Oracle International Corporation | Systems and methods for sharing of execution plans for similar database statements |
CA2382714A1 (en) * | 2002-04-19 | 2003-10-19 | Ibm Canada Limited-Ibm Canada Limitee | Substituting parameter markers for literals in a database query language statement to promote reuse of previously generated access plans |
US6999958B2 (en) * | 2002-06-07 | 2006-02-14 | International Business Machines Corporation | Runtime query optimization for dynamically selecting from multiple plans in a query based upon runtime-evaluated performance criterion |
JP4116413B2 (ja) * | 2002-12-11 | 2008-07-09 | 株式会社日立製作所 | プリフェッチアプライアンスサーバ |
US7243098B2 (en) * | 2002-12-19 | 2007-07-10 | International Business Machines Corporation | Method, system, and program for optimizing aggregate processing |
US20040162822A1 (en) * | 2003-02-13 | 2004-08-19 | Khachatur Papanyan | Method and apparatus for converting in-line database queries to stored procedures |
US7895191B2 (en) * | 2003-04-09 | 2011-02-22 | International Business Machines Corporation | Improving performance of database queries |
US20040236726A1 (en) * | 2003-05-19 | 2004-11-25 | Teracruz, Inc. | System and method for query result caching |
US7146363B2 (en) * | 2003-05-20 | 2006-12-05 | Microsoft Corporation | System and method for cardinality estimation based on query execution feedback |
WO2005028627A2 (en) * | 2003-09-19 | 2005-03-31 | Netezza Corporation | Performing sequence analysis as a relational join |
US7539660B2 (en) * | 2003-10-23 | 2009-05-26 | International Business Machines Corporation | Method and system for generating SQL joins to optimize performance |
US20050216451A1 (en) * | 2004-02-19 | 2005-09-29 | Urs Enzler | Generation of database queries from predefined query strings |
US7310637B2 (en) * | 2004-05-05 | 2007-12-18 | International Business Machines Corporation | Dynamic database access via standard query language and abstraction technology |
US7328207B2 (en) * | 2004-08-20 | 2008-02-05 | Microsoft Corporation | Extensions for query persistence across requests with dynamic update for writeback |
US20060074872A1 (en) * | 2004-09-30 | 2006-04-06 | International Business Machines Corporation | Adaptive database buffer memory management using dynamic SQL statement cache statistics |
US8290977B2 (en) * | 2004-10-21 | 2012-10-16 | Sybase Inc. | Database system providing methodology for execution of functions in XML queries |
US7337170B2 (en) * | 2005-01-18 | 2008-02-26 | International Business Machines Corporation | System and method for planning and generating queries for multi-dimensional analysis using domain models and data federation |
US7640230B2 (en) * | 2005-04-05 | 2009-12-29 | Microsoft Corporation | Query plan selection control using run-time association mechanism |
US20060294088A1 (en) * | 2005-06-27 | 2006-12-28 | International Business Machines Corporation | Method, system, and computer program product for caching dynamically generated queries |
US20070214104A1 (en) * | 2006-03-07 | 2007-09-13 | Bingjie Miao | Method and system for locking execution plan during database migration |
US8032522B2 (en) * | 2006-08-25 | 2011-10-04 | Microsoft Corporation | Optimizing parameterized queries in a relational database management system |
US7865515B2 (en) * | 2006-08-28 | 2011-01-04 | Microsoft Corporation | Server side bucketization of parameterized queries |
US8527502B2 (en) * | 2006-09-08 | 2013-09-03 | Blade Makai Doyle | Method, system and computer-readable media for software object relationship traversal for object-relational query binding |
US7898817B2 (en) * | 2006-10-17 | 2011-03-01 | Hewlett-Packard Development Company, L.P. | Circuit board assembly |
US7640238B2 (en) * | 2007-01-19 | 2009-12-29 | International Business Machines Corporation | Query planning for execution using conditional operators |
US20080195578A1 (en) * | 2007-02-09 | 2008-08-14 | Fabian Hueske | Automatically determining optimization frequencies of queries with parameter markers |
US20080201295A1 (en) * | 2007-02-21 | 2008-08-21 | Mylavarapu Praveena | Caching plans with using data values |
US20080319958A1 (en) * | 2007-06-22 | 2008-12-25 | Sutirtha Bhattacharya | Dynamic Metadata based Query Formulation for Multiple Heterogeneous Database Systems |
US8086597B2 (en) * | 2007-06-28 | 2011-12-27 | International Business Machines Corporation | Between matching |
US7877376B2 (en) * | 2007-07-18 | 2011-01-25 | Oracle International Corporation | Supporting aggregate expressions in query rewrite |
US20100005077A1 (en) * | 2008-07-07 | 2010-01-07 | Kickfire, Inc. | Methods and systems for generating query plans that are compatible for execution in hardware |
US20090171895A1 (en) * | 2007-12-28 | 2009-07-02 | Herbert Hackmann | Method and system for generating dynamic associations to data objects |
US7937385B2 (en) * | 2008-05-05 | 2011-05-03 | International Business Machines Corporation | Obtaining a plan for executing a query in a relational database |
US8060495B2 (en) * | 2008-10-21 | 2011-11-15 | International Business Machines Corporation | Query execution plan efficiency in a database management system |
US8666966B2 (en) * | 2009-01-30 | 2014-03-04 | Hewlett-Packard Development Company, L.P. | Providing parallel result streams for database queries |
-
2009
- 2009-04-24 KR KR1020090036163A patent/KR101083563B1/ko active IP Right Grant
- 2009-04-29 JP JP2012507131A patent/JP5600736B2/ja active Active
- 2009-04-29 US US13/265,984 patent/US8661022B2/en active Active
- 2009-04-29 WO PCT/KR2009/002254 patent/WO2010123168A1/ko active Application Filing
-
2014
- 2014-01-23 US US14/162,353 patent/US9753977B2/en active Active
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6356887B1 (en) * | 1999-06-28 | 2002-03-12 | Microsoft Corporation | Auto-parameterization of database queries |
EP1585036A2 (en) * | 2004-04-08 | 2005-10-12 | International Business Machines Corporation | Management of parameterized database queries |
Also Published As
Publication number | Publication date |
---|---|
KR101083563B1 (ko) | 2011-11-14 |
US20140136515A1 (en) | 2014-05-15 |
KR20100117415A (ko) | 2010-11-03 |
US9753977B2 (en) | 2017-09-05 |
JP5600736B2 (ja) | 2014-10-01 |
US20120143847A1 (en) | 2012-06-07 |
JP2012524930A (ja) | 2012-10-18 |
US8661022B2 (en) | 2014-02-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2010123168A1 (ko) | 데이터베이스 관리 방법 및 시스템 | |
WO2020015067A1 (zh) | 数据采集方法、装置、设备及存储介质 | |
WO2014189190A1 (ko) | 데이터 부재 태깅 기반의 정보 검색 시스템 및 방법 | |
WO2018058959A1 (zh) | Sql审核方法、装置、服务器及存储设备 | |
WO2016047866A1 (ko) | 데이터베이스 마이그레이션 방법 및 그 장치 | |
WO2021040166A1 (ko) | 소프트웨어 업데이트를 위한 신구 데이터간의 차분 생성 방법 및 그 장치 | |
WO2015144012A1 (zh) | 一种软件开发事务的实现方法及电子设备 | |
WO2010137814A2 (en) | Method of providing by-viewpoint patent map and system thereof | |
WO2011162446A1 (ko) | 온톨로지 스키마와 결합된 개체명 사전 및 마이닝 규칙을 이용한 용어의 개체명 결정모듈 및 방법 | |
WO2012060669A1 (ko) | Sms를 통해 원격 디바이스를 제어하는 방법 및 이를 위한 장치 | |
WO2011162444A1 (ko) | 온톨로지 스키마와 결합된 개체명 사전 및 마이닝 규칙을 이용한 개체명 사전 또는 마이닝 규칙 데이터베이스 갱신 장치 및 방법 | |
WO2010050786A2 (en) | Conditional processing method and apparatus | |
WO2022108318A1 (ko) | 스마트 컨트랙트 코드 취약점 분석 장치 및 방법 | |
WO2024090932A1 (ko) | 수집 데이터 자동 처리를 위한 데이터 적재 프로파일링 장치 및 방법 | |
WO2021141292A1 (ko) | 하이브리드 클라우드 기반의 실시간 데이터 아카이빙 방법 및 시스템 | |
WO2013008978A1 (ko) | 개체 식별 결과 검색 시스템 및 방법 | |
WO2024075927A1 (en) | Meta-searching method and apparatus | |
WO2018086371A1 (zh) | 笔记本、智能终端及笔记本内容索引创建方法 | |
WO2012169708A1 (ko) | 메타 데이터 변환 방법 및 이에 적합한 장치 | |
WO2020215680A1 (zh) | 自动生成pojo类的方法、装置及存储介质、计算机设备 | |
WO2022145503A1 (ko) | 시맨틱 레스트 에이피아이 제공 방법 | |
WO2020242086A1 (ko) | 다중 지식의 비교 우위를 추론하는 서버, 방법 및 컴퓨터 프로그램 | |
WO2015163697A1 (ko) | Db2 데이터베이스에서 데이터를 복원하는 방법 및 장치 | |
WO2015163696A1 (ko) | 마이크로소프트 sql 서버 데이터베이스에서 데이터를 복원하는 방법 및 장치 | |
WO2015178554A1 (ko) | 압축 방식을 이용한 데이터 소스 관리 장치 및 방법 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 09843696 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2012507131 Country of ref document: JP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13265984 Country of ref document: US |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 09843696 Country of ref document: EP Kind code of ref document: A1 |