CN116628023A - Waiting event type query method and device, storage medium and electronic equipment - Google Patents

Waiting event type query method and device, storage medium and electronic equipment Download PDF

Info

Publication number
CN116628023A
CN116628023A CN202310526457.5A CN202310526457A CN116628023A CN 116628023 A CN116628023 A CN 116628023A CN 202310526457 A CN202310526457 A CN 202310526457A CN 116628023 A CN116628023 A CN 116628023A
Authority
CN
China
Prior art keywords
target
type
event
waiting
resource information
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
CN202310526457.5A
Other languages
Chinese (zh)
Other versions
CN116628023B (en
Inventor
易金东
熊军
冉崇杰
杨廷琨
崔虎龙
闵建兵
高云龙
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Yunhe Enmo Beijing Information Technology Co ltd
Original Assignee
Yunhe Enmo Beijing Information Technology Co 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 Yunhe Enmo Beijing Information Technology Co ltd filed Critical Yunhe Enmo Beijing Information Technology Co ltd
Priority to CN202310526457.5A priority Critical patent/CN116628023B/en
Publication of CN116628023A publication Critical patent/CN116628023A/en
Application granted granted Critical
Publication of CN116628023B publication Critical patent/CN116628023B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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/2455—Query execution
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3466—Performance evaluation by tracing or monitoring
    • 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/21—Design, administration or maintenance of databases
    • 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/28—Databases characterised by their database models, e.g. relational or object models
    • G06F16/284—Relational databases
    • G06F16/285—Clustering or classification
    • 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
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

The application discloses a waiting event type query method, a waiting event type query device, a storage medium and electronic equipment. Wherein the method comprises the following steps: determining a target query statement corresponding to the target waiting event in response to a type query instruction of the target waiting event; obtaining target query information of a target query statement, wherein the target query information at least comprises one of the following: application type information of the target query statement and target resource information when the target query statement is executed; matching the target query information with a preset classification rule to obtain an event type of a target waiting event, and feeding back the event type, wherein the event type comprises: the type of management caused by database management commands or the type of traffic caused by database development commands. The method and the device solve the technical problem that business personnel without DBA skills cannot accurately judge the event type of the waiting event of the database because the related technology does not classify various waiting events of the database.

Description

Waiting event type query method and device, storage medium and electronic equipment
Technical Field
The present application relates to the field of database management technologies, and in particular, to a method and apparatus for querying a waiting event type, a storage medium, and an electronic device.
Background
At present, domestic libraries and open source libraries are numerous, so that it is important to develop related operation and maintenance work on various types of databases to ensure that the databases maintain good stability in the execution process.
In general, database management personnel generally take steps of inquiring about the type of waiting event, inquiring about the detailed information of the waiting event, tracking the corresponding session detailed information, and taking corresponding measures according to the inquiry analysis result of the waiting event, so as to solve the database performance problem caused by the waiting event. However, the method can be performed only on the basis that the database manager grasps and accurately identifies the information of waiting events, session states, lock types and the like of various types of databases, so that the business personnel who do not know the related information of the databases cannot judge what type of waiting events of the databases have performance problems.
In view of the above problems, no effective solution has been proposed at present.
Disclosure of Invention
The embodiment of the application provides a waiting event type query method, a device, a storage medium and electronic equipment, which at least solve the technical problem that service personnel without DBA skills cannot accurately judge the event type of a waiting event of a database because the related technology does not classify various waiting events of the database.
According to an aspect of an embodiment of the present application, there is provided a waiting event type query method, including: determining a target query statement corresponding to the target waiting event in response to a type query instruction of the target waiting event; obtaining target query information of a target query statement, wherein the target query information at least comprises one of the following: application type information of the target query statement and target resource information when the target query statement is executed; matching the target query information with a preset classification rule to obtain an event type of a target waiting event, and feeding back the event type, wherein the event type comprises: the management type caused by the database management command or the service type caused by the database development command.
Optionally, matching the target query information with a preset classification rule to obtain an event type of the target waiting event, including: determining the application type of the target query statement according to the application type information, wherein when the application type of the target query statement is a maintenance type, determining the event type of the target waiting event as a management type; when the application type of the target query statement is a service type, determining that the event type of the target waiting event is the service type, wherein the waiting event of the service type comprises: and waiting for events of multiple classes determined based on the target resource information when executing the target query statement.
Optionally, when the application type of the target query statement is a service type, determining that the event type of the target waiting event is a service type includes: determining a target database for operating the target query statement; acquiring configuration resource information of a target database, and determining the event type of a target waiting event as a configuration type according to the configuration resource information, wherein the configuration resource information comprises at least one of the following: the size of the shared pool, the size of the redo log file; acquiring system resource information when a target database executes a target query statement, and determining the event type of a target waiting event as a system type according to the system resource information, wherein the system resource information comprises at least one of the following: disk resource information, memory latch resource information, network resource information, CPU resource information, cluster resource information and waiting queue information.
Optionally, acquiring system resource information when the target database executes the target query statement, and determining the event type of the target waiting event as the system type according to the system resource information, including: acquiring first CPU resource information of a target database when analyzing a target query statement, and determining the event type of a target waiting event as the CPU resource type according to the first CPU resource information; acquiring first disk resource information of a target database when analyzing a target query statement, and determining an event type of a target waiting event as an I/O type according to the first disk resource information; acquiring first memory latch resource information of a target database when analyzing a target query statement, and determining an event type of a target waiting event as a concurrency type according to the first memory latch resource information; and acquiring first cluster resource information of the target database when analyzing the target query statement, and determining the event type of the target waiting event as the cluster type according to the first cluster resource information.
Optionally, the target query statement includes: the system comprises a data manipulation language, a data definition language and a transaction control instruction, wherein the system resource information is acquired when a target database executes a target query statement, the event type of a target waiting event is determined to be the system type according to the system resource information, and the system comprises: acquiring the operation resource information of a target database when executing a target query statement, and determining the event type of a target waiting event as the CPU resource type according to the operation resource information; acquiring second disk resource information of a target database when executing a target query statement, and determining the event type of a target waiting event as an I/O type according to the second disk resource information; acquiring second cluster resource information of the target database when executing the target query statement, and determining the event type of the target waiting event as a cluster type according to the second cluster resource information; acquiring application program information of a target database when executing a data manipulation language, and determining an event type of a target waiting event as an application program type according to the application program information; obtaining waiting queue information of a target database when executing a data manipulation language or a data definition language, and determining an event type of a target waiting event as a waiting queue lock type according to the waiting queue information; and acquiring the rewriting log confirmation information of the target database when executing the transaction control instruction, and determining the event type of the target waiting event as the transaction commit type according to the rewriting log confirmation information.
Optionally, acquiring system resource information when the target database executes the target query statement, and determining an event type of the target waiting event as a system type according to the system resource information, and further including: acquiring second memory latch resource information of the target database when a query result of the target query statement is returned, and determining an event type of a target waiting event as a concurrency type according to the second memory latch resource information; acquiring network resource information of the target database when a query result of the target query statement is returned, and determining the event type of the target waiting event as the network type according to the network resource information.
Optionally, the method further comprises: and when the target database does not execute the target query statement, determining the event type of the target waiting event as an idle type.
According to another aspect of the embodiment of the present application, there is also provided a waiting event type query device, including: the determining module is used for determining a target query statement corresponding to the target waiting event in response to a type query instruction of the target waiting event; the acquisition module is used for acquiring target query information of the target query statement, wherein the target query information at least comprises one of the following components: application type information of the target query statement and target resource information when the target query statement is executed; the query module is used for matching the target query information with a preset classification rule to obtain an event type of a target waiting event and feeding back the event type, wherein the event type comprises: the management type caused by the database management command or the service type caused by the database development command.
According to another aspect of the embodiment of the present application, there is further provided a nonvolatile storage medium, where the nonvolatile storage medium includes a stored program, and a device where the nonvolatile storage medium is located executes the above-mentioned waiting event type query method by running the program.
According to another aspect of the embodiment of the present application, there is also provided an electronic device including: the system comprises a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the waiting event type query method through the computer program.
In the embodiment of the application, a target query statement corresponding to a target waiting event is determined in response to a type query instruction of the target waiting event; obtaining target query information of a target query statement, wherein the target query information at least comprises one of the following: application type information of the target query statement and target resource information when the target query statement is executed; matching the target query information with a preset classification rule to obtain an event type of a target waiting event, and feeding back the event type, wherein the event type comprises: the management type caused by the database management command or the service type caused by the database development command.
In the process, by accurately classifying various waiting events, the threshold for analyzing the performance of the database is greatly reduced, so that business personnel without DBA skills can quickly find out the problem types of the database to analyze the performance of the database, and further the technical problem that the business personnel without DBA skills cannot accurately judge the event types of the waiting events of the database because the related technologies do not classify various waiting events of the database is solved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application. In the drawings:
FIG. 1 is a flow chart of an alternative database performance analysis of the related art;
FIG. 2 is a flow chart of an alternative wait for event type query method according to an embodiment of the application;
FIG. 3 is a schematic diagram of an alternative wait event categorization in accordance with an embodiment of the application;
FIG. 4 is a schematic diagram of an alternative PostgreSQL database waiting event classification in accordance with an embodiment of the application;
FIG. 5 is a schematic diagram of an alternative DM database waiting for event classification in accordance with an embodiment of the application;
fig. 6 is a schematic structural diagram of an alternative waiting event type query device according to an embodiment of the present application.
Detailed Description
In order that those skilled in the art will better understand the present application, a technical solution in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present application without making any inventive effort, shall fall within the scope of the present application.
It should be noted that the terms "first," "second," and the like in the description and the claims and drawings of the present application are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the application described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
In addition, the related information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for presentation, analyzed data, etc.) related to the present application are information and data authorized by the user or sufficiently authorized by each party. For example, an interface is provided between the system and the relevant user or institution, before acquiring the relevant information, the system needs to send an acquisition request to the user or institution through the interface, and acquire the relevant information after receiving the consent information fed back by the user or institution.
Example 1
FIG. 1 is a schematic flow chart of the prior art analysis of database performance, which is mainly analyzed according to the following concept: classification of query waiting events (i.e., what waiting events currently exist in the query database); waiting for an event based on the categorized lower drill body analysis, comprising: inquiring the detailed information of the waiting event (namely, carrying out specific analysis on the waiting event); querying the corresponding session details (i.e., looking at which session the user waits for a lock to be held); judging whether the cause of the session is definitely waited, if yes, taking corresponding measures, otherwise, continuing to carry out further drill-down analysis on the session or SQL. However, the method can only be analyzed by database management personnel who are skilled in mastering and accurately identifying information such as waiting events, session states, lock types and the like of various databases, and for business personnel without DBA skills, the waiting event types of the databases cannot be accurately determined, so that the performance problems of the databases cannot be analyzed.
In order to solve the technical problems, the embodiment of the application provides a waiting event type query method to solve the technical problem that a business person without DBA skills cannot accurately judge the event type of a waiting event of a database because related technologies do not classify various waiting events of the database. The method of querying the type of the waiting event will be described in detail.
It should be noted that the steps illustrated in the flowcharts of the figures may be performed in a computer system such as a set of computer executable instructions, and that although a logical order is illustrated in the flowcharts, in some cases the steps illustrated or described may be performed in an order other than that illustrated herein.
Fig. 2 is a flow chart of an alternative waiting event type query method according to an embodiment of the present application, as shown in fig. 2, the method at least includes steps S202-S206, wherein:
step S202, in response to the type query instruction of the target waiting event, determining a target query statement corresponding to the target waiting event.
In the technical solution provided in step S202, the above-mentioned type query instruction for the target waiting event may be understood that the relevant service personnel queries the target waiting event that occurs when the target database executes the target query statement, so as to determine the event type thereof, thereby effectively exploring the relevant clues that can help to identify the performance bottleneck and tune the database. Where a wait event refers to an event that may occur during database operations when a request needs to be processed. For example, when a request is sent to read/write to an Oracle database, the request invokes multiple processes that may experience hardware, software, operating system, or configuration problems that terminate or delay processing, all known as wait events. It should be noted that to be executed efficiently in a database, waiting events must be kept as few as possible. In addition, all waiting events occurring during one operation are analyzed, and repair of the waiting events is required if the waiting period is too long, but all waiting events cannot be completely eliminated.
Step S204, obtaining target query information of a target query statement, wherein the target query information at least comprises one of the following: application type information of the target query statement and target resource information when the target query statement is executed.
In the technical solution provided in step S204, the relevant service personnel can accurately determine the event type of the target waiting event according to the target query information related to the target query statement, for example, whether the target query statement is a maintenance type or a service type, or according to the resource information when the target query statement is executed.
Step S206, matching the target query information with a preset classification rule to obtain an event type of the target waiting event, and feeding back the event type, wherein the event type comprises: the management type caused by the database management command or the service type caused by the database development command.
In the technical scheme provided in step S206, the related service personnel can match the obtained target query information with the preset classification rule, so as to quickly and accurately determine the event type of the target waiting event, feed back the event type to the service personnel, take corresponding measures on the waiting event in time, and analyze the database performance problem in time.
Based on the schemes defined in the above steps S202 to S206, it may be known that, in an embodiment, in response to a type query instruction for a target waiting event, a target query statement corresponding to the target waiting event is determined; obtaining target query information of a target query statement, wherein the target query information at least comprises one of the following: application type information of the target query statement and target resource information when the target query statement is executed; matching the target query information with a preset classification rule to obtain an event type of a target waiting event, and feeding back the event type, wherein the event type comprises: the management type caused by the database management command or the service type caused by the database development command.
Therefore, through the technical scheme of the embodiment of the application, the threshold for reducing the performance analysis of the database is achieved by accurately classifying various waiting events, so that business personnel without DBA skills can quickly find out the problem types of the database to analyze the performance of the database, and further the technical problem that the business personnel without DBA skills cannot accurately judge the event types of the waiting events of the database because the related technologies do not classify various waiting events of the database is solved.
The above-described method of this embodiment is further described below.
As an optional implementation manner, in the technical solution provided in step S206, the method may include: determining the application type of the target query statement according to the application type information, wherein when the application type of the target query statement is a maintenance type, determining the event type of the target waiting event as a management type; when the application type of the target query statement is a service type, determining that the event type of the target waiting event is the service type, wherein the waiting event of the service type comprises: and waiting for events of multiple classes determined based on the target resource information when executing the target query statement.
In this embodiment, because the attention points of different people are different, the operation and maintenance DBA will pay close attention to the execution condition of the maintenance class SQL, and the business personnel will pay close attention to the execution efficiency of the business SQL, so that the target query statement can be divided into a maintenance type and a business type according to the application type, and the event type of the corresponding target waiting event can be determined according to the application type of the target query statement.
Specifically, when the application type of the target query statement is a maintenance type, determining the event type of the target waiting event as a management type, wherein the DBA is generally professional, and the database performance can be completely analyzed according to the specific waiting event, so that the target waiting event of the management type does not need to be further divided into waiting classifications; when the application type of the target query statement is a service type, determining that the event type of the target waiting event is the service type, wherein the waiting event of the service type is further summarized and classified because the service personnel generally has shallow knowledge on the database and cannot accurately classify the waiting event, thereby facilitating the service personnel to quickly get on hand and achieving the effect of reducing the threshold, and therefore, the waiting event of the service type comprises: and waiting for events of multiple classes determined based on the target resource information when executing the target query statement.
In addition, for the target query statement of the service type, since the configuration of the database must be ensured to be reasonable when the DBA delivers the database to service personnel, the waiting event of the service type can be further classified according to SQL execution waiting caused by configuration type reasons or SQL waiting caused by other system reasons.
Optionally, a target database for operating the target query statement is first determined; then obtaining configuration resource information of a target database, and determining the event type of a target waiting event as a configuration type according to the configuration resource information, wherein the configuration resource information comprises at least one of the following: the size of the shared pool, the size of the redo log file; finally, system resource information when the target database executes the target query statement is obtained, and the event type of the target waiting event is determined to be the system type according to the system resource information, wherein the system resource information comprises at least one of the following: disk resource information, memory latch resource information, network resource information, CPU resource information, cluster resource information and waiting queue information.
In particular, the above configuration type of waiting event may be understood as a problem of database performance caused by too small allocated resources or unreasonable parameter configuration, and it is suggested to repair the problem by configuration or capacity expansion for this type of waiting event. The waiting event of the system type can be further divided according to the process of executing the query statement by the database, wherein the operation steps of the query statement can be summarized as follows by summarizing and summarizing the SQL (Structure Query Language, structured query language) execution process of more than ten databases of various domestic, open-source, business and the like: the analysis stage, the execution stage and the return result stage, so that the event type of the waiting event can be determined by acquiring different system resource information for each operation step.
Optionally, in the parsing query statement stage, the event type of the target waiting event may be determined according to the following rule:
acquiring first CPU resource information of a target database when analyzing a target query statement, and determining the event type of a target waiting event as the CPU resource type according to the first CPU resource information; acquiring first disk resource information of a target database when analyzing a target query statement, and determining an event type of a target waiting event as an I/O type according to the first disk resource information; acquiring first memory latch resource information of a target database when analyzing a target query statement, and determining an event type of a target waiting event as a concurrency type according to the first memory latch resource information; and acquiring first cluster resource information of the target database when analyzing the target query statement, and determining the event type of the target waiting event as the cluster type according to the first cluster resource information.
Specifically, in the parsing query statement stage, the system resources that relevant business personnel can acquire include: in order to prevent the analysis SQL related object from being changed, various latches of the analysis object and the sub-object can be obtained; in order to ensure the consistency of the shared memory, the parsed SQL and the execution plan can be placed into the shared cache after the parsing is completed, and the memory latch resource information needs to be acquired; some Share Every Thing high availability databases need to acquire cluster object locks during analysis, so that other clusters can not modify the objects, and therefore, first cluster resource information needs to be acquired; in the analysis process, metadata and statistical information of various objects are loaded, and Cache or IO access is needed at the moment to acquire CPU resource information and disk resource information. When the waiting event occurs in the database, determining the event type of the target waiting event according to the system resource information of the analysis query statement.
Optionally, in the stage of executing the query statement, the event type of the target waiting event may be determined according to the following rule:
acquiring the operation resource information of a target database when executing a target query statement, and determining the event type of a target waiting event as the CPU resource type according to the operation resource information; acquiring second disk resource information of a target database when executing a target query statement, and determining the event type of a target waiting event as an I/O type according to the second disk resource information; acquiring second cluster resource information of the target database when executing the target query statement, and determining the event type of the target waiting event as a cluster type according to the second cluster resource information; acquiring application program information of a target database when executing a data manipulation language, and determining an event type of a target waiting event as an application program type according to the application program information; obtaining waiting queue information of a target database when executing a data manipulation language or a data definition language, and determining an event type of a target waiting event as a waiting queue lock type according to the waiting queue information; and acquiring the rewriting log confirmation information of the target database when executing the transaction control instruction, and determining the event type of the target waiting event as the transaction commit type according to the rewriting log confirmation information.
The SQL comprises the following steps: data definition language (Data Definition Language, DDL): for creating, modifying and deleting database objects, such as tables, views, indexes, stored procedures, etc.; data manipulation language (Data Manipulation Language, DML): for querying and manipulating data, such as SELECT, INSERT, UPDATE, DELETE, etc.; data control language (Data Control Language, DCL): the security control method is used for managing the authority of the user to access the database and implementing the security control strategy. Such as GRANT, REVOKE, etc.; transaction control commands (Transaction Control Commands), including COMMIT and ROLLBACK commands and SAVEPOINT, always take an atomic approach after data insertion or modification.
Specifically, in the stage of executing the query statement, the system resources that can be acquired by the relevant service personnel include: when the query statement is executed, a large amount of operations such as sorting, GROUPBY, association and the like are generated, and at this time, the operation resource information needs to be acquired; when executing the query statement, the disk resource may be accessed, so that the second disk resource information needs to be acquired; reading data on other clusters is possible when the query statement is executed, so that second cluster resource information is required to be acquired; application information may also be obtained while executing the data manipulation language; the waiting queue information of the table or the row is also required to be acquired when the data manipulation language or the data definition language is executed; upon execution of the transaction control instruction, the overwrite log confirm information may be acquired. Thus, when the waiting event occurs in the database, the event type of the target waiting event is determined according to the system resource information of the executing query statement.
Optionally, in the query result stage of returning the query statement, the event type of the target waiting event may be determined according to the following rule:
acquiring second memory latch resource information of the target database when a query result of the target query statement is returned, and determining an event type of a target waiting event as a concurrency type according to the second memory latch resource information; acquiring network resource information of the target database when a query result of the target query statement is returned, and determining the event type of the target waiting event as the network type according to the network resource information.
Specifically, in the query result stage of returning the query statement, the system resources that the relevant service personnel can acquire include: because all the returned results of the relational databases are one cursor, the memory latch resource information related to the cursor can be obtained; in addition, a network is needed to transmit the query result of the target query statement, so that network resource information is also needed to be acquired. Thus, when the waiting event occurs in the database, the event type of the target waiting event is determined according to the system resource information in the query result stage of the returned query statement.
In addition, when the target database does not execute the target query statement, if the target database generates a waiting event, it may be determined that the event type of the target waiting event is an idle type at this time.
It should be noted that, in order to determine a waiting event classification library applicable to each database, the common waiting event types may be summarized and sorted, and some abnormal and unusual waiting event types may not be specifically classified.
As an alternative implementation, fig. 3 is a schematic diagram of an alternative waiting event categorization according to an embodiment of the application, as shown in fig. 3. Firstly, classifying according to the executed query statement into a service class SQL and a maintenance class SQL, and determining that a corresponding waiting event is an administ transaction (i.e. management type) for the maintenance class SQL; for business class SQL, it can be divided into Configuration (i.e. Configuration type) and other types, wherein the execution process according to SQL can be further divided into other types: ON CPU (i.e., CPU type), disk IO (i.e., I/O type), queue Lock (i.e., wait queue Lock type), cluster (i.e., cluster type), network (i.e., network type), concurrency (i.e., concurrency class), it should be noted that Concurrency may be further subdivided into commit (i.e., transaction commit type) caused by requesting memory latches when executing transaction control instructions and wait memory latches in other scenarios, and in addition, queue Lock may be further subdivided into TX Lock (i.e., application type) executing DML statements and other types of locks (i.e., wait queue Lock type). In addition, when the session is suspended and waiting is to enter a pending state, the waiting event type of the database is Idle (i.e., idle type).
Therefore, through the division of the waiting event types shown in fig. 3, the definition of waiting event classification can be defined in detail for each database, so that for the uniformly classified database waiting events, service personnel without DBA skills can conveniently and quickly find out the problem types of the databases, and therefore optimization suggestions for adjusting the performance of the databases are timely given.
Furthermore, in order to facilitate the service personnel without DBA skills to quickly find out the problem types of the databases when the performance problems occur in the databases, the classification standard definition can be defined in detail for each database to obtain the waiting event classification standard corresponding to each database, so that the service personnel can conveniently determine the specific reasons of waiting for each session by inquiring the waiting event classification standard of the database. Wherein the waiting events of each class of database are different, and therefore, the defined waiting event classification standards are also different. The waiting event defined by the present application will be specifically described below by taking the waiting event classification of two relational databases as an example.
Specifically, fig. 4 is a schematic diagram of an alternative PostgreSQL database waiting event classification according to an embodiment of the present application, and as shown in fig. 4, the original waiting events are reclassified according to multiple classes of waiting events defined in the present application, so as to obtain a more detailed waiting event classification standard, thereby facilitating a business person without DBA skills to quickly find out a problem type of the database when a performance problem occurs in the database.
In addition, fig. 5 is a schematic diagram of an alternative classification of waiting events in a DM database according to an embodiment of the present application, as shown in fig. 5, the original waiting events are reclassified according to multiple classes of waiting events defined in the present application, so as to obtain a more detailed waiting event classification standard, thereby facilitating a business person without DBA skills to quickly find out a problem type of the database when a performance problem occurs in the database.
Example 2
Based on embodiment 1 of the present application, there is also provided an embodiment of a waiting event type query device, which executes the waiting event type query method of the above embodiment when running. Fig. 6 is an optional waiting event type query device according to an embodiment of the present application, where the waiting event type query device, as shown in fig. 6, at least includes a determining module 61, an obtaining module 63 and a query module 65, where:
the determining module 61 is configured to determine a target query statement corresponding to the target waiting event in response to a type query instruction for the target waiting event.
Specifically, the determining module 61 queries the target database for the target waiting event occurring when executing the target query statement to determine the event type thereof, so that relevant clues which can help to identify performance bottlenecks and tune the database can be effectively explored. Where a wait event refers to an event that may occur during database operations when a request needs to be processed. For example, when a request is sent to read/write to an Oracle database, the request invokes multiple processes that may experience hardware, software, operating system, or configuration problems that terminate or delay processing, all known as wait events. It should be noted that to be executed efficiently in a database, waiting events must be kept as few as possible. In addition, all waiting events occurring during one operation are analyzed, and repair of the waiting events is required if the waiting period is too long, but all waiting events cannot be completely eliminated.
An obtaining module 63, configured to obtain target query information of a target query statement, where the target query information at least includes one of the following: application type information of the target query statement and target resource information when the target query statement is executed.
Specifically, the obtaining module 63 may accurately determine the event type of the target waiting event according to the target query information related to the target query statement, for example, whether the target query statement is a maintenance type or a service type, or according to the resource information when the target query statement is executed.
The query module 65 is configured to match the target query information with a preset classification rule, obtain an event type of the target waiting event, and feed back the event type, where the event type includes: the management type caused by the database management command or the service type caused by the database development command.
Specifically, the query module 65 may match the obtained target query information with a preset classification rule, so as to quickly and accurately determine an event type of the target waiting event, feed back the event type to the service personnel, take corresponding measures on the waiting event in time, and analyze the database performance problem in time.
As an alternative embodiment, the event type of the target wait event may be determined as follows: determining the application type of the target query statement according to the application type information, wherein when the application type of the target query statement is a maintenance type, determining the event type of the target waiting event as a management type; when the application type of the target query statement is a service type, determining that the event type of the target waiting event is the service type, wherein the waiting event of the service type comprises: and waiting for events of multiple classes determined based on the target resource information when executing the target query statement.
In this embodiment, because the attention points of different people are different, the operation and maintenance DBA will pay close attention to the execution condition of the maintenance class SQL, and the business personnel will pay close attention to the execution efficiency of the business SQL, so that the target query statement can be divided into a maintenance type and a business type according to the application type, and the event type of the corresponding target waiting event can be determined according to the application type of the target query statement.
Specifically, when the application type of the target query statement is a maintenance type, determining the event type of the target waiting event as a management type, wherein the DBA is generally professional, and the database performance can be completely analyzed according to the specific waiting event, so that the target waiting event of the management type does not need to be further divided into waiting classifications; when the application type of the target query statement is a service type, determining that the event type of the target waiting event is the service type, wherein the waiting event of the service type is further summarized and classified because the service personnel generally has shallow knowledge on the database and cannot accurately classify the waiting event, thereby facilitating the service personnel to quickly get on hand and achieving the effect of reducing the threshold, and therefore, the waiting event of the service type comprises: and waiting for events of multiple classes determined based on the target resource information when executing the target query statement.
In addition, for the target query statement of the service type, since the configuration of the database must be ensured to be reasonable when the DBA delivers the database to service personnel, the waiting event of the service type can be further classified according to SQL execution waiting caused by configuration type reasons or SQL waiting caused by other system reasons.
Optionally, a target database for operating the target query statement is first determined; then obtaining configuration resource information of a target database, and determining the event type of a target waiting event as a configuration type according to the configuration resource information, wherein the configuration resource information comprises at least one of the following: the size of the shared pool, the size of the redo log file; finally, system resource information when the target database executes the target query statement is obtained, and the event type of the target waiting event is determined to be the system type according to the system resource information, wherein the system resource information comprises at least one of the following: disk resource information, memory latch resource information, network resource information, CPU resource information, cluster resource information and waiting queue information.
In particular, the above configuration type of waiting event may be understood as a problem of database performance caused by too small allocated resources or unreasonable parameter configuration, and it is suggested to repair the problem by configuration or capacity expansion for this type of waiting event. The waiting event of the system type can be further divided according to the process of executing the query statement by the database, wherein the operation steps of the query statement can be summarized as follows by summarizing and summarizing SQL executing processes of more than ten databases of domestic, open source, business and the like: the analysis stage, the execution stage and the return result stage, so that the event type of the waiting event can be determined by acquiring different system resource information for each operation step.
Optionally, in the parsing query statement stage, the event type of the target waiting event may be determined according to the following rule:
acquiring first CPU resource information of a target database when analyzing a target query statement, and determining the event type of a target waiting event as the CPU resource type according to the first CPU resource information; acquiring first disk resource information of a target database when analyzing a target query statement, and determining an event type of a target waiting event as an I/O type according to the first disk resource information; acquiring first memory latch resource information of a target database when analyzing a target query statement, and determining an event type of a target waiting event as a concurrency type according to the first memory latch resource information; and acquiring first cluster resource information of the target database when analyzing the target query statement, and determining the event type of the target waiting event as the cluster type according to the first cluster resource information.
Specifically, in the parsing query statement stage, the system resources that relevant business personnel can acquire include: in order to prevent the analysis SQL related object from being changed, various latches of the analysis object and the sub-object can be obtained; in order to ensure the consistency of the shared memory, the parsed SQL and the execution plan can be placed into the shared cache after the parsing is completed, and the memory latch resource information needs to be acquired; some Share Every Thing high availability databases need to acquire cluster object locks during analysis, so that other clusters can not modify the objects, and therefore, first cluster resource information needs to be acquired; in the analysis process, metadata and statistical information of various objects are loaded, and Cache or IO access is needed at the moment to acquire CPU resource information and disk resource information. When the waiting event occurs in the database, determining the event type of the target waiting event according to the system resource information of the analysis query statement.
Optionally, in the stage of executing the query statement, the event type of the target waiting event may be determined according to the following rule:
acquiring the operation resource information of a target database when executing a target query statement, and determining the event type of a target waiting event as the CPU resource type according to the operation resource information; acquiring second disk resource information of a target database when executing a target query statement, and determining the event type of a target waiting event as an I/O type according to the second disk resource information; acquiring second cluster resource information of the target database when executing the target query statement, and determining the event type of the target waiting event as a cluster type according to the second cluster resource information; acquiring application program information of a target database when executing a data manipulation language, and determining an event type of a target waiting event as an application program type according to the application program information; obtaining waiting queue information of a target database when executing a data manipulation language or a data definition language, and determining an event type of a target waiting event as a waiting queue lock type according to the waiting queue information; and acquiring the rewriting log confirmation information of the target database when executing the transaction control instruction, and determining the event type of the target waiting event as the transaction commit type according to the rewriting log confirmation information.
The SQL comprises the following steps: data definition language: for creating, modifying and deleting database objects, such as tables, views, indexes, stored procedures, etc.; data manipulation language: for querying and manipulating data, such as SELECT, INSERT, UPDATE, DELETE, etc.; data control language: the security control method is used for managing the authority of the user to access the database and implementing the security control strategy. Such as GRANT, REVOKE, etc.; transaction control commands, including COMMIT and ROLLBACK commands and SAVEPOINT, always take an atomic approach after data insertion or modification.
Specifically, in the stage of executing the query statement, the system resources that can be acquired by the relevant service personnel include: when the query statement is executed, a large amount of operations such as sorting, GROUPBY, association and the like are generated, and at this time, the operation resource information needs to be acquired; when executing the query statement, the disk resource may be accessed, so that the second disk resource information needs to be acquired; reading data on other clusters is possible when the query statement is executed, so that second cluster resource information is required to be acquired; application information may also be obtained while executing the data manipulation language; the waiting queue information of the table or the row is also required to be acquired when the data manipulation language or the data definition language is executed; upon execution of the transaction control instruction, the overwrite log confirm information may be acquired. Thus, when the waiting event occurs in the database, the event type of the target waiting event is determined according to the system resource information of the executing query statement.
Optionally, in the query result stage of returning the query statement, the event type of the target waiting event may be determined according to the following rule:
acquiring second memory latch resource information of the target database when a query result of the target query statement is returned, and determining an event type of a target waiting event as a concurrency type according to the second memory latch resource information; acquiring network resource information of the target database when a query result of the target query statement is returned, and determining the event type of the target waiting event as the network type according to the network resource information.
Specifically, in the query result stage of returning the query statement, the system resources that the relevant service personnel can acquire include: because all the returned results of the relational databases are one cursor, the memory latch resource information related to the cursor can be obtained; in addition, a network is needed to transmit the query result of the target query statement, so that network resource information is also needed to be acquired. Thus, when the waiting event occurs in the database, the event type of the target waiting event is determined according to the system resource information in the query result stage of the returned query statement.
In addition, when the target database does not execute the target query statement, if the target database generates a waiting event, it may be determined that the event type of the target waiting event is an idle type at this time.
Therefore, through the technical scheme of the embodiment of the application, the threshold for reducing the performance analysis of the database is achieved by accurately classifying various waiting events, so that business personnel without DBA skills can quickly find out the problem types of the database to analyze the performance of the database, and further the technical problem that the business personnel without DBA skills cannot accurately judge the event types of the waiting events of the database because the related technologies do not classify various waiting events of the database is solved.
It should be noted that, each module in the waiting event type query device in the embodiment of the present application corresponds to each implementation step of the waiting event type query method in embodiment 1 one by one, and since detailed description has been made in embodiment 1, details not shown in part in this embodiment may refer to embodiment 1, and will not be repeated here.
Example 3
According to an embodiment of the present application, there is also provided a nonvolatile storage medium including a stored program, where a device in which the nonvolatile storage medium is located executes the waiting event type query method in embodiment 1 by running the program.
Specifically, the device where the nonvolatile storage medium is located executes the following steps by running the program:
step S202, in response to a type query instruction for a target waiting event, determining a target query statement corresponding to the target waiting event;
step S204, obtaining target query information of a target query statement, wherein the target query information at least comprises one of the following: application type information of the target query statement and target resource information when the target query statement is executed;
step S206, matching the target query information with a preset classification rule to obtain an event type of the target waiting event, and feeding back the event type, wherein the event type comprises: the management type caused by the database management command or the service type caused by the database development command.
According to an embodiment of the present application, there is further provided a processor for running a program, wherein the program executes the waiting event type query method in embodiment 1.
Specifically, the program execution realizes the following steps:
step S202, in response to a type query instruction for a target waiting event, determining a target query statement corresponding to the target waiting event;
Step S204, obtaining target query information of a target query statement, wherein the target query information at least comprises one of the following: application type information of the target query statement and target resource information when the target query statement is executed;
step S206, matching the target query information with a preset classification rule to obtain an event type of the target waiting event, and feeding back the event type, wherein the event type comprises: the management type caused by the database management command or the service type caused by the database development command.
According to an embodiment of the present application, there is also provided an electronic device including: a memory and a processor, wherein the memory stores a computer program, the processor is configured to execute the waiting event type query method in embodiment 1 by the computer program.
In particular, the processor is configured to implement the following steps by computer program execution:
step S202, in response to a type query instruction for a target waiting event, determining a target query statement corresponding to the target waiting event;
step S204, obtaining target query information of a target query statement, wherein the target query information at least comprises one of the following: application type information of the target query statement and target resource information when the target query statement is executed;
Step S206, matching the target query information with a preset classification rule to obtain an event type of the target waiting event, and feeding back the event type, wherein the event type comprises: the management type caused by the database management command or the service type caused by the database development command.
The foregoing embodiment numbers of the present application are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
In the foregoing embodiments of the present application, the descriptions of the embodiments are emphasized, and for a portion of this disclosure that is not described in detail in this embodiment, reference is made to the related descriptions of other embodiments.
In the several embodiments provided in the present application, it should be understood that the disclosed technology may be implemented in other manners. The above-described embodiments of the apparatus are merely exemplary, and the division of units may be a logic function division, and there may be another division manner in actual implementation, for example, multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interfaces, units or modules, or may be in electrical or other forms.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method of the various embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing is merely a preferred embodiment of the present application and it should be noted that modifications and adaptations to those skilled in the art may be made without departing from the principles of the present application, which are intended to be comprehended within the scope of the present application.

Claims (10)

1. A method for awaiting an event type query, comprising:
responding to a type query instruction of a target waiting event, and determining a target query statement corresponding to the target waiting event;
obtaining target query information of the target query statement, wherein the target query information at least comprises one of the following: application type information of the target query statement and target resource information when the target query statement is executed;
matching the target query information with a preset classification rule to obtain an event type of the target waiting event, and feeding back the event type, wherein the event type comprises: the management type caused by the database management command or the service type caused by the database development command.
2. The method of claim 1, wherein matching the target query information with a preset classification rule to obtain an event type of the target waiting event comprises:
Determining the application type of the target query statement according to the application type information, wherein,
when the application type of the target query statement is a maintenance type, determining that the event type of the target waiting event is a management type;
when the application type of the target query statement is a service type, determining that the event type of the target waiting event is the service type, wherein the waiting event of the service type comprises: and waiting for events of multiple classes determined based on the target resource information when the target query statement is executed.
3. The method of claim 2, wherein when the application type of the target query statement is a service type, determining that the event type of the target wait event is a service type comprises:
determining a target database for operating the target query statement;
acquiring configuration resource information of the target database, and determining the event type of the target waiting event as a configuration type according to the configuration resource information, wherein the configuration resource information comprises at least one of the following: the size of the shared pool, the size of the redo log file;
acquiring system resource information when the target database executes the target query statement, and determining the event type of the target waiting event as a system type according to the system resource information, wherein the system resource information comprises at least one of the following: disk resource information, memory latch resource information, network resource information, CPU resource information, cluster resource information and waiting queue information.
4. The method of claim 3, wherein obtaining the system resource information of the target database when executing the target query statement, and determining the event type of the target wait event as a system type based on the system resource information, comprises:
acquiring first CPU resource information of the target database when analyzing the target query statement, and determining the event type of the target waiting event as the CPU resource type according to the first CPU resource information;
acquiring first disk resource information of the target database when analyzing the target query statement, and determining that the event type of the target waiting event is an I/O type according to the first disk resource information;
acquiring first memory latch resource information of the target database when analyzing the target query statement, and determining that the event type of the target waiting event is a concurrency type according to the first memory latch resource information;
and acquiring first cluster resource information of the target database when analyzing the target query statement, and determining the event type of the target waiting event as a cluster type according to the first cluster resource information.
5. The method of claim 3, wherein the target query statement comprises: the system comprises a data manipulation language, a data definition language and a transaction control instruction, wherein the system resource information when the target database executes the target query statement is acquired, the event type of the target waiting event is determined to be the system type according to the system resource information, and the system comprises the following components:
acquiring the operation resource information of the target database when executing the target query statement, and determining the event type of the target waiting event as the CPU resource type according to the operation resource information;
acquiring second disk resource information of the target database when executing the target query statement, and determining that the event type of the target waiting event is an I/O type according to the second disk resource information;
acquiring second cluster resource information of the target database when executing the target query statement, and determining the event type of the target waiting event as a cluster resource type according to the second cluster resource information;
acquiring application program information of the target database when the data manipulation language is executed, and determining the event type of the target waiting event as an application program type according to the application program information;
Acquiring the waiting queue information of the target database when the data manipulation language or the data definition language is executed, and determining that the event type of the target waiting event is a waiting queue lock type according to the waiting queue information;
and acquiring the rewriting log confirmation information of the target database when executing the transaction control instruction, and determining the event type of the target waiting event as the transaction commit type according to the rewriting log confirmation information.
6. The method of claim 3, wherein obtaining the system resource information of the target database when executing the target query statement, and determining the event type of the target wait event as a system type according to the system resource information, further comprises:
acquiring second memory latch resource information of the target database when a query result of the target query statement is returned, and determining that the event type of the target waiting event is a concurrency type according to the second memory latch resource information;
acquiring the network resource information of the target database when the query result of the target query statement is returned, and determining that the event type of the target waiting event is a network type according to the network resource information.
7. A method according to claim 3, characterized in that the method further comprises:
and when the target database does not execute the target query statement, determining that the event type of the target waiting event is an idle type.
8. A wait for event type query device, comprising:
the determining module is used for responding to the type query instruction of the target waiting event and determining a target query statement corresponding to the target waiting event;
the acquisition module is used for acquiring target query information of the target query statement, wherein the target query information at least comprises one of the following steps: application type information of the target query statement and target resource information when the target query statement is executed;
the query module is used for matching the target query information with a preset classification rule to obtain an event type of the target waiting event and feeding back the event type, wherein the event type comprises: the management type caused by the database management command or the service type caused by the database development command.
9. A nonvolatile storage medium, characterized in that the nonvolatile storage medium includes a stored program, wherein a device in which the nonvolatile storage medium is located executes the waiting event type inquiry method according to any one of claims 1 to 7 by running the program.
10. An electronic device, comprising: a memory and a processor, wherein the memory has stored therein a computer program, the processor being configured to execute the waiting event type query method of any of claims 1 to 7 by the computer program.
CN202310526457.5A 2023-05-10 2023-05-10 Waiting event type query method and device, storage medium and electronic equipment Active CN116628023B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310526457.5A CN116628023B (en) 2023-05-10 2023-05-10 Waiting event type query method and device, storage medium and electronic equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310526457.5A CN116628023B (en) 2023-05-10 2023-05-10 Waiting event type query method and device, storage medium and electronic equipment

Publications (2)

Publication Number Publication Date
CN116628023A true CN116628023A (en) 2023-08-22
CN116628023B CN116628023B (en) 2024-04-09

Family

ID=87637436

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310526457.5A Active CN116628023B (en) 2023-05-10 2023-05-10 Waiting event type query method and device, storage medium and electronic equipment

Country Status (1)

Country Link
CN (1) CN116628023B (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117667223A (en) * 2024-02-01 2024-03-08 上海登临科技有限公司 Data adventure solving method, computing engine, processor and electronic equipment

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160179884A1 (en) * 2014-12-22 2016-06-23 Zbigniew Jerzak Integrated event processing and database management
US20190102411A1 (en) * 2017-09-29 2019-04-04 Oracle International Corporation Rule-based autonomous database cloud service framework
CN112084161A (en) * 2020-09-16 2020-12-15 腾讯科技（深圳）有限公司 Database-based data processing method and device and readable storage medium
CN113868252A (en) * 2021-09-27 2021-12-31 中国人民银行清算总中心 Database mode matching method and device and SQL query statement generation method
CN115357663A (en) * 2022-08-26 2022-11-18 建信金融科技有限责任公司 Data synchronization method, system and device based on incremental data synchronization component

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160179884A1 (en) * 2014-12-22 2016-06-23 Zbigniew Jerzak Integrated event processing and database management
US20190102411A1 (en) * 2017-09-29 2019-04-04 Oracle International Corporation Rule-based autonomous database cloud service framework
CN112084161A (en) * 2020-09-16 2020-12-15 腾讯科技（深圳）有限公司 Database-based data processing method and device and readable storage medium
CN113868252A (en) * 2021-09-27 2021-12-31 中国人民银行清算总中心 Database mode matching method and device and SQL query statement generation method
CN115357663A (en) * 2022-08-26 2022-11-18 建信金融科技有限责任公司 Data synchronization method, system and device based on incremental data synchronization component

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
王照文;: "基于事件ID的Windows日志集中审计", 中国金融电脑, no. 04 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117667223A (en) * 2024-02-01 2024-03-08 上海登临科技有限公司 Data adventure solving method, computing engine, processor and electronic equipment
CN117667223B (en) * 2024-02-01 2024-04-12 上海登临科技有限公司 Data adventure solving method, computing engine, processor and electronic equipment

Also Published As

Publication number Publication date
CN116628023B (en) 2024-04-09

Similar Documents

Publication Publication Date Title
US9996558B2 (en) Method and system for accessing a set of data tables in a source database
US6801903B2 (en) Collecting statistics in a database system
US11899666B2 (en) System and method for dynamic database split generation in a massively parallel or distributed database environment
US7069264B2 (en) Stratified sampling of data in a database system
US11544268B2 (en) System and method for generating size-based splits in a massively parallel or distributed database environment
US7130838B2 (en) Query optimization via a partitioned environment
US20150142733A1 (en) System and method for efficient management of big data in a database using streaming tables
US10216782B2 (en) Processing of updates in a database system using different scenarios
US8224807B2 (en) Enhanced utilization of query optimization
US7743052B2 (en) Method and apparatus for projecting the effect of maintaining an auxiliary database structure for use in executing database queries
US20070174290A1 (en) System and architecture for enterprise-scale, parallel data mining
US10089357B2 (en) System and method for generating partition-based splits in a massively parallel or distributed database environment
US20160092524A1 (en) System and method for data transfer from jdbc to a data warehouse layer in a massively parallel or distributed database environment
US10078684B2 (en) System and method for query processing with table-level predicate pushdown in a massively parallel or distributed database environment
US20070156736A1 (en) Method and apparatus for automatically detecting a latent referential integrity relationship between different tables of a database
US20070294218A1 (en) Method and System for Reducing Host Variable Impact on Access Path Selection
US20110202497A1 (en) Systems and Methods for Performing Direct Reporting Access to Transaction Databases
US7761445B2 (en) Automated system for identifying and dropping marginal database indexes
CN116628023B (en) Waiting event type query method and device, storage medium and electronic equipment
US20020049747A1 (en) Method for integrating and accessing of heterogeneous data sources
US11354313B2 (en) Transforming a user-defined table function to a derived table in a database management system
US20090171921A1 (en) Accelerating Queries Based on Exact Knowledge of Specific Rows Satisfying Local Conditions
CN112199401B (en) Data request processing method, device, server, system and storage medium
Peng et al. Event detection over live and archived streams
CN113886205A (en) Database performance bottleneck positioning analysis method, device and system and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant