US008346761B2

(12) United States Patent

Muras et al.

(10) Patent N0.: (45) Date of Patent:

(56)

US 8,346,761 B2
Jan. 1, 2013

(54) (75)

METHOD AND SYSTEM FOR DATA MINING

References Cited
U.S. PATENT DOCUMENTS

FOR AUTOMATIC QUERY OPTIMIZATION

Inventors: Brian Robert Muras, Rochester, MN

6,360,214 B1 *

3/2002

Ellis et a1. ....................... .. 707/2

(US); John Matthew Santosuosso,

Rochester, MN (U S)

2005/0177557 2005/0065928 2002/0198867 A1 *

12/2002 3/2005 8/2005 Ziauddin Mortensen Lohman et etet a1. a1. al................. .. 707/3

(73) Assignee: International Business Machines

Corporation, Armonk, NY (US)
Notice: Subject to any disclaimer, the term of this patent is extended or adjusted under 35

* cited by examiner
Primary Examiner * Jean M Corrielus
Assistant Examiner * Alex Gofman

(74) Attorney, Agent, or Firm *Wood, Herron & Evans,

LLP

U.S.C. 154(b) by 2291 days.

(21) Appl. N0.: 10/911,849 (22) Filed: (65) (51) (52) (58)
Int. Cl.

(57)

ABSTRACT

Aug. 5, 2004
Prior Publication Data

US 2006/0031189 A1

Feb. 9, 2006

G06F 15/16 G06F 1 7/20

(2006.01) (2006.01)

US. Cl. ...................................... .. 707/721; 707/718

Field of Classi?cation Search ...................... .. None

A database monitor tracks performance statistics and infor mation about the execution of different SQL statements. A query optimizer bene?ts from these statistics When generat ing an access plan. In particular, the query optimizer, upon receiving an SQL statement, searches the records of the data base monitor for similar SQL statements that have previously been executed. As part of determining the best access plan for the current SQL statement, the query optimizer considers the information retrieved from the database monitor. In this Way, the access plan that is generated can automatically be tuned based on empirical performance evidence.

See application ?le for complete search history.

4 Claims, 5 Drawing Sheets

32.

4s
PARSED STATEMENT
46 40

50
EXECUTION PLAN
44

/QUERY ZV

DATABASE

PARSER
42

SQL

OPTIMIZER
DATA 34 BASE

DATABASE

ENGINE

RESULT

SET /

DATABASE
MONITOR

US. Patent

Jan. 1, 2013

Sheet 2 of5

US 8,346,761 B2
3 02

DATABASE ENGINE EXECUTES SQL STATEMENTS AND TRACKS PERFORMANCE STATISTICS

3 04
NEW SQL STATEMENT
RECEIVED

306
QUERY OPTHVIIZER STARTS TO GENERATE ACCESS PLAN

3 08
SEARCH PERFORMANCE STATISTICS FOR

SIMILAR SQL STATMENTS

310
USE STATISTICS FROM SIMILAR STATEMENT(S)
WHEN GENERATING THE ACCESS PLAN

FIG. 3

US. Patent

Jan. 1, 2013

Sheet 3 of5

US 8,346,761 B2

4 02
OPTIMIZER

RECEIVES sQL

QUERY

NO

IS ACCESS PLAN ALREADY

YES

AVAILABLE?

AR

SEARCH DATABASE
FOR SIMILAR SQL

404

QUERY

408

EXECUTION

I
RETRIEvE

406
410

PERFORMANCE
STATISTICS AND

INFORMATION

I
VERIFY EXECUTION PERFORMANCE WAS ACCEPTABLE

412

l
GENERATE CURRENT ACcEss PLAN USING PERFORMANCE

INFORMATION

414

i
EXECUTE ACCESS PLAN

416

FIG. 4

US. Patent

Jan. 1, 2013

Sheet 4 of5

US 8,346,761 B2

502
QUERY OPTIMIZER RECEIVES SQL
STATEMENT

l
IDENTIFY PREVIOUSLY DEVELOPED ACCESS PLAN(S) FOR THIS STATEMENT

504

I
IDENTIFY RECORD(S) WITHIN THE DATABASE THAT RELATE TO THESE ACCESS PLAN(S)

S06

i
DETERMINE FROM THE RECORD(S) WHETHER EXECUTION
PERFORMANCE WAS ACCEPTABLE

508
YES

N0

5l0
FORCE

512

RE-OPTIMIZATION TO
GENERATE NEW ACCESS
PLAN

USEgIEEIIQCICCHESST-IPELAN
QUERY

514
ADJUST ESTIMATED RUN TIME FOR ORIGINAL ACCESS PLAN

FIG. 5

US. Patent

Jan. 1, 2013

Sheet 5 of5

US 8,346,761 B2

602
IDENTIFY FROM DATABASE HOST VARIABLES

USED IN QUERIES WITH POOR PERFORMANCE

l
QUERY OPTIMIZER
RECEIVES AN SQL STATEMENT

604

I
START TO GENERATE ACCESS PLAN

606

I
ARE CURRENT HOST VARIABLES IN THE LIST OF IDENTIFIED HOST VARIABLES?

608
NO

FORCE RE-OPTIMIZATION TO ENSURE A NEW ACCESS PLAN IS GENERATED

CONTINUE GENERATING ACCESS PLAN IN THE NORMAL MANNER

610

612

FIG. 6

US 8,346,761 B2
1
METHOD AND SYSTEM FOR DATA MINING

2
each optimizer/DBMS) loW-level information telling the database engine that ultimately handles a query precisely
What steps to take (and in What order) to execute the query.

FOR AUTOMATIC QUERY OPTIMIZATION

FIELD OF THE INVENTION

Also typically associated With each generated plan is an opti

miZer s estimate of hoW long it Will take to run the query using

The invention relates to database management systems, and in particular, to query optimizers.
BACKGROUND OF THE INVENTION
Databases are used to store information for an innumerable

that plan.
An optimiZers job is often necessary and dif?cult because of the enormous number (i.e., countably in?nite number) of
possible query forms that can be generated in a database management system, e.g., due to factors such as the use of

number of applications, including various commercial, industrial, technical, scienti?c and educational applications.
As the reliance on information increases, both the volume of information stored in most databases, as Well as the number of users Wishing to access that information, likeWise increases. Moreover, as the volume of information in a database, and the number of users Wishing to access the database, increases, the amount of computing resources required to manage such a
database increases as Well.
20

SQL queries With any number of relational tables made up of countless data columns of various types, the theoretically in?nite number of methods of accessing the actual data records from each table referenced (e.g., using an index, a hash table, etc.), the possible combinations of those methods
of access among all the tables referenced, etc. An optimiZer is

often permitted to reWrite a query (or portion of it) into any equivalent form, and since for any given query there are typically many equivalent forms, an optimiZer has a count

ably in?nite universe of extremely diverse possible solutions

(plans) to consider. On the other hand, an optimiZer is often required to use minimal system resources given the desirabil

Database management systems (DBMSs), Which are the

computer programs that are used to access the information

stored in databases, therefore often require tremendous

resources to handle the heavy Workloads placed on such systems. As such, signi?cant resources have been devoted to
25

ity for high throughput. As such, an optimiZer often has only

a limited amount of time to pare the search space of possible

execution plans doWn to an optimal plan for a particular

query. Another automated tool that is a part of many database management systems is a database monitor. It is used to

increasing the performance of database management systems

With respect to processing searches, or queries, to databases. Improvements to both computer hardWare and softWare have improved the capacities of conventional database man

agement systems. For example, in the hardWare realm, increases in microprocessor performance, coupled With

30

improved memory management systems, have improved the

number of queries that a particular microprocessor can per form in a given unit of time. Furthermore, the use of multiple

gather performance statistics related to SQL queries run Within the database management system. The data collected by the database monitor is typically collected in a database ?le itself Where it can be queried by a trained user to help identify and tune performance problem areas. A database
monitor typically tracks the name of a query, the name of the

microprocessors and/or multiple netWorked computers has

further increased the capacities of many database manage ment systems. From a softWare standpoint, the use of relational databases, Which organiZe information into formally-de?ned tables con sisting of roWs and columns, and Which are typically accessed using a standardiZed language such as Structured Query Lan

35

tables accessed by the query, the indices used by the query (if any), the join parameters of the query, and other pertinent
information such as the duration of time the query took to

40

complete. The performance statistics collected by a database monitor are typically large in volume and require a knoWl edgeable SQL administrator to interpret and use.

Typical query optimiZers store information about previ

ously encountered queries and the access plans that Were created for such queries. When a previous query is once again encountered, these optimiZers use previous access plans to avoid the time and cost of re-creating an access plan regard less of hoW the earlier access plan performed. Thus, the cur rent determination and analysis by the optimiZer to re-use a plan simply considers Whether a similar access plan is avail able for use and does not consider the past performance
statistics of that plan such as those that are collected by a

guage (SQL), has substantially improved processing e?i

ciency, as Well as substantially simpli?ed the creation, orga
niZation, and extension of information Within a database.

Furthermore, signi?cant development efforts have been

directed toWard query optimization, Whereby the execution of particular searches, or queries, is optimiZed in an auto
mated manner to minimiZe the amount of resources required to execute each query.

45

Through the incorporation of various hardWare and soft Ware improvements, many high performance database man
agement systems are able to handle hundreds or even thou

50

database monitor. Thus, there remains the need in prior data base environments for a system that permits selecting or
modifying a query access plan based on empirical evidence

sands of queries each second, even on databases containing millions or billions of records. HoWever, further increases in information volume and Workload are inevitable, so contin ued advancements in database management systems are still

about the performance statistics of previously executed

55

access plans that Were collected by a database monitor.

required.
One area that has been a fertile area for academic and

SUMMARY OF THE INVENTION Embodiments of the present invention relate to a database

60

corporate research is that of improving the designs of the query optimiZers utiliZed in many conventional database management systems. The primary task of a query optimiZer
is to choose the most ef?cient Way to execute each database

query, or request, passed to the database management system by a user. The output of an optimiZation process is typically
referred to as an execution plan, access plan, or just
65

monitor that tracks performance statistics and information about the execution of different database queries and a query optimiZer that bene?ts from these statistics When generating an access plan. In particular, the query optimiZer, upon receiv
ing a database query, searches a database of performance

plan and is frequently depicted as a tree graph. Such a plan

typically incorporates (often in a proprietary form unique to

statistics for similar database queries that have previously been executed. As part of determining the best access plan for the current database query, the query optimiZer considers the

US 8,346,761 B2
3
information retrieved from the statistics database. In this way, the access plan that is generated can automatically be tuned

4
support selecting an access plan based on previously col lected performance statistics of similar access plans that have

based on empirical evidence of past performance.

One aspect of the present invention relates to a method for generating an access plan. In accordance with this method, a

previously executed. Instead of merely relying on estimated costs for the different access plan strategies, the query opti
miZer uses the empirical evidence from previous query execu tions when determining how to generate the access plan. A

particular set of past performance statistics is identi?ed that

relates to a database query. When the query optimiZer gener ates an access plan for the current database query, its genera tion is based at least in part on the particular set of past

speci?c implementation of such a database engine and opti miZer framework capable of supporting this functionality in a
manner consistent with the invention will be discussed in greater detail below. However, prior to a discussion of such a

performance statistics.
Another aspect of the present invention relates to another method for generating an access plan in which a respective set of past performance statistics is maintained for each of a

plurality of previously executed database queries. From these statistics, a particular set of past performance statistics is
identi?ed corresponding to a previously executed database
query similar to a current database query and the performance of an access plan identi?ed within the particular set of past

speci?c implementation, a brief discussion will be provided regarding an exemplary hardware and software environment within which such an optimiZer framework may reside. Turning now to the Drawings, wherein like numbers denote like parts throughout the several views, FIG. 1 illus
trates an exemplary hardware and software environment for an apparatus 10 suitable for implementing a database man

performance statistics is analyZed. The query optimiZer gen

erates a current access plan for the current database query

agement system that considers previous performance statis

20

based at least in part on the access plan that was analyZed. Yet another aspect of the present invention relates to another method for generating an access plan that also

tics when selecting access plans consistent with the invention. For the purposes of the invention, apparatus 10 may represent practically any type of computer, computer system or other

programmable electronic device, including a client computer,

a server computer, a portable computer, a handheld computer,

includes a respective set of past performance statistics being maintained for each of a plurality of previously executed
database queries. A current access plan for a current database
25

an embedded controller, etc. Moreover, apparatus 10 may be

implemented using one or more networked computers, e. g.,

query is identi?ed and then, from the statistics, a particular set of past performance statistics is identi?ed corresponding to a previously executed database query that used the current

in a cluster or other distributed computing system. Apparatus

10 will hereinafter also be referred to as a computer,

access plan. The performance of the previously executed

database query is analyZed and used to determine whether to
re-use the current access plan.
30

although it should be appreciated the term apparatus may also include other suitable programmable electronic devices
consistent with the invention. Computer 10 typically includes at least one processor 12 coupled to a memory 14. Processor 12 may represent one or more processors (e. g., microprocessors), and memory 14 may represent the random access memory (RAM) devices com prising the main storage of computer 10, as well as any supplemental levels of memory, e.g., cache memories, non volatile or backup memories (e.g., programmable or ?ash

Still another aspect of the present invention relates to a method for generating an access plan that includes maintain

ing in non-volatile memory a respective set of past perfor

mance statistics for each of a plurality of previously executed database queries. A set of host variables references is identi
35

?ed within those respective sets of past performance statistics that relate to data skew performance degradation. The query
optimiZer forces re-optimiZation to generate a new access plan for the current database query if the current database
query includes one or more host variables within the identi
40

memories), read-only memories, etc. In addition, memory 14

may be considered to include memory storage physically located elsewhere in computer 10, e.g., any cache memory in
a processor 12, as well as any storage capacity used as a
virtual memory, e.g., as stored on a mass storage device 16 or

?ed set of host variables.

BRIEF DESCRIPTION OF THE DRAWINGS

on another computer coupled to computer 10 via network 18

45

FIG. 1 is a block diagram of a networked computer system

incorporating a database management system consistent with the invention. FIG. 2 is a block diagram illustrating the principal compo nents and ?ow of information therebetween in the database management system of FIG. 1.
FIG. 3 illustrates a ?owchart of an exemplary method for a

(e.g., a client computer 20). Computer 10 also typically receives a number of inputs and outputs for communicating information externally. For inter
face with a user or operator, computer 10 typically includes
one or more user input devices 22 (e.g., a keyboard, a mouse,

a trackball, a joystick, a touchpad, and/ or a microphone,

50

among others) and a display 24 (e.g., a CRT monitor, an LCD

display panel, and/or a speaker, among others). Otherwise,

user input may be received via another computer (e.g., a computer 20) interfaced with computer 10 over network 18,
or via a dedicated workstation interface or the like.
55

query optimiZer to use past performance statistics when gen erating an access plan.
FIG. 4 illustrates a ?owchart of an exemplary method of locating a similar SQL statement in a database monitors records to use when generating an access plan. FIG. 5 illustrates a ?owchart of an exemplary method for determining how to generate an access plan based on how well a similar access plan performed in the past. FIG. 6 illustrates a ?owchart of an exemplary method for determining how to generate an access plan based on past

For additional storage, computer 10 may also include one

or more mass storage devices 16, e.g., a ?oppy or other

removable disk drive, a hard disk drive, a direct access storage device (DASD), an optical drive (e.g., a CD drive, a DVD

drive, etc.), and/or a tape drive, among others. Furthermore,

60 computer 10 may include an interface with one or more

networks 18 (e.g., a LAN, a WAN, a wireless network, and/or

statistics regarding data skew.

DETAILED DESCRIPTION
65

As mentioned above, the embodiments discussed herein after utiliZe a database engine and optimiZer framework that

the Internet, among others) to permit the communication of information with other computers coupled to the network. It should be appreciated that computer 10 typically includes suitable analog and/or digital interfaces between processor 12 and each of components 14, 16, 18, 22 and 24 as is well
known in the art.

US 8,346,761 B2
5
Computer 10 operates under the control of an operating
system 30, and executes or otherwise relies upon various

6
In addition, various program code described hereinafter may be identi?ed based upon the application within which it is implemented in a speci?c embodiment of the invention.

computer software applications, components, programs, objects, modules, data structures, etc. (e.g., database manage ment system 32 and database 34, among others). Moreover, various applications, components, programs, objects, mod
ules, etc. may also execute on one or more processors in

However, it should be appreciated that any particular program nomenclature that follows is used merely for convenience,
and thus the invention should not be limited to use solely in

any speci?c application identi?ed and/or implied by such

nomenclature. Furthermore, given the typically endless num
ber of manners in which computer programs may be orga

another computer coupled to computer 10 via a network 18, e.g., in a distributed or client-server computing environment,

whereby the processing required to implement the functions

of a computer program may be allocated to multiple comput
ers over a network.

niZed into routines, procedures, methods, modules, objects,

and the like, as well as the various manners in which program

Turning brie?y to FIG. 2, an exemplary implementation of database management system 32 is shown. The principal
components of database management system 32 that are rel evant to query optimiZation are an SQL parser 40, cost-based

functionality may be allocated among various software layers that are resident within a typical computer (e.g., operating

systems, libraries,APIs, applications, applets, etc.), it should

be appreciated that the invention is not limited to the speci?c

organization and allocation of program functionality

described herein. Those skilled in the art will recogniZe that the exemplary environment illustrated in FIGS. 1 and 2 is not intended to limit the present invention. Indeed, those skilled in the art will recogniZe that other alternative hardware and/ or software environments may be used without departing from the scope of the invention.

optimiZer 42 and database engine 44. SQL parser 40 receives

from a user a database query 46, which in the illustrated

embodiment, is provided in the form of an SQL statement. SQL parser 40 then generates a parsed statement 48 there

20

from, which is passed to optimiZer 42 for query optimiZation.

As a result of query optimiZation, an execution or access plan

50 is generated, oftenusing data such as platform capabilities,

query content information, etc., that is stored in database 34. Once generated, the execution plan is forwarded to database engine 44 for execution of the database query on the infor mation in database 34. The result of the execution of the database query is typically stored in a result set, as repre
sented at block 52. While the database engine 44 executes the query 46, a
25

Query optimiZers have added great bene?ts to automatic

operation of database management systems. These optimiZ

ers have allowed different access plan strategies to be quickly explored so that an optimal strategy can be identi?ed and selected to perform an SQL statement. In addition, there are a number of database monitoring tools available to collect sta

30

database monitor 60 tracks performance of the execution and collects statistics and other information about how the plan 50 is performing. The statistics and information for each query
46 are stored in a monitor database 62. The database monitor

tistics about queries as they execute. However, these statistics have typically been useful only to skilled administrators who
can interpret the statistics and use them to help tune a data

62 is advantageously a relational database that permits easy searching and retrieval of data. Other components may be incorporated into system 32, as may other suitable database management architectures. Other database programming and organizational architectures may also be used consistent with the invention. Therefore, the invention is not limited to the particular implementation dis
cussed herein. In general, the routines executed to implement the embodi ments of the invention, whether implemented as part of an

35

40

base. Embodiments of the present invention contemplate using the data collected by database monitoring tools to auto matically allow a database to tune itself by permitting the query optimiZer to utiliZe the performance statistics collected when generating a query access plan. Typical query optimiZ ers have relatively robust performance and successfully choose an optimal access plan the majority of the time; how ever, in certain instances, the query optimiZer may have dif ?culty in selecting the best access plan. For example, the
more complex the WHERE clause that ?lters the selection of rows of a table, the more dif?culty the query optimiZer has in

selecting the best access plan. Also, when multiple ?les (or
45

operating system or a speci?c application, component, pro

gram, object, module or sequence of instructions, or even a

tables) are involved in a query, an optimiZer may have di?i

culty in selecting an e?icient access plan. By using past

performance statistics about how a similar access plan actu

subset thereof, will be referred to herein as computer pro

gram code, or simply program code. Program code typi

cally comprises one or more instructions that are resident at

ally performed, the query optimiZer may be prevented from

50

various times in various memory and storage devices in a computer, and that, when read and executed by one or more processors in a computer, cause that computer to perform the steps necessary to execute steps or elements embodying the

selecting a poor performing access plan that otherwise appears to be the optimal plan.
The type of data that can be collected by a database monitor

is large and varied. The exemplary embodiments described

herein provide speci?c examples of performance statistics

that may be used to affect which access plan an optimiZer
55

various aspects of the invention. Moreover, while the inven

tion has and hereinafter will be described in the context of

fully functioning computers and computer systems, those

skilled in the art will appreciate that the various embodiments
of the invention are capable of being distributed as a program

selects. However, the present invention also contemplates using other speci?c performance statistics to assist the query optimiZer. Commonly used performance statistics include ?le siZe, memory siZe, processor speed, number of processors

product in a variety of forms, and that the invention applies

available, the SQL statement (with parameters replaced), type

60

equally regardless of the particular type of signal bearing

media used to actually carry out the distribution. Examples of signal bearing media include but are not limited to recordable type media such as volatile and non-volatile memory devices,

of SQL operation, number of row updated, inserted, or deleted, number of rows fetched, elapsed time for this opera tion, access plan rebuild code, table name, join ?elds, esti

mated completion time, estimate I/O operations, number of

rows in the table, index name, hash used, host variables, join
65

?oppy and other removable disks, hard disk drives, magnetic

tape, optical disks (e.g., CD-ROMs, DVDs, etc.), among

others, and transmission type media such as digital and ana

position, join method, join type, etc.

In general, FIG. 3 illustrates a ?owchart of an exemplary

log communication links.

embodiment of the present invention. In step 302, SQL state

US 8,346,761 B2
7
ments are executed and during execution, performance sta tistics relating to each SQL statement are tracked and
recorded. The performance statistics are maintained in a man

8
With the principles of the present invention. In step 502, the query optimiZer receives an SQL statement and identi?es, in
step 504, an access plan that had previously been used to

ner that is accessible by the query optimizer. When a neW SQL

implement this SQL statement. In step 506, the query opti

miZer can then search for a record in the database monitor of

statement is received in step 304, the query optimiZer begins

to generate an access plan, in step 306. As part of developing the access plan, the query optimiZer searches the performance statistics, in step 308, to locate at least one similar SQL statement that Was performed in the past. In step 310, the
performance statistics of this statement, or more than one

a previous SQL statement that also used this access plan. From this record, a determination is made, in step 508, about hoW Well the access plan performed the SQL statement. For

statement, are then used by the query optimiZer When devel oping the access plan. The optimiZer may use this information
to force certain restrictions When developing an access plan or may use this information to select betWeen different access

example, the estimated I/O operations can be compared against the actual I/O operations or the estimated completion
time can be compared to the actual completion time. In addi tion, other performance characteristics can be compared to
one another to determine if the access plan performed as

plans that are available for the particular SQL statement.

FIG. 4 illustrates one exemplary use of certain perfor mance statistics of the database monitor to assist the query

intended. If the performance of the access plan Was beloW

acceptable levels, then the query optimiZer forces re-optimi

Zation of the access plan for this SQL statement, in step 510. If the access plan did perform adequately, then the query optimiZer may implement the query plan as it stands, in step
20

optimiZer in selecting an access plan. A query optimiZer

typically maintains a list of access plans that have been pre viously executed. Thus, When an SQL statement is encoun

512.

tered, the query optimiZer searches its cache of plans to deter

mine if it needs to build an access plan from scratch or Whether it can re-use an access plan it has previously built.

HoWever, an access plan for a particular SQL statement may

not be found in the cache if the cache acts as a FIFO buffer With limited siZe or if the cache is in volatile memory that
25

exists only during the current session of the query optimiZer.

Similarly, during dynamic SQL operation, the query access

plans are not saved as they are executed. HoWever, the data base monitor stores a non-volatile record of previously
30

If re-optimiZation is selected, then the estimated run time for the original access plan may be increased, in step 514, to re?ect the discovery that the previous estimated run time proved to be too short. In this Way, the original access plan becomes less attractive to the query optimiZer When the query optimiZer is selecting from among different access plans for a particular query in the future. Even if the original access plan is selected, the query optimiZer may utiliZe the historical
records of the database monitor to learn the closest estimated run time for a particular access plan and adjust them accord

executed access plans and, therefore, provides an additional source of information for the query optimizer. In step 402, the query optimiZer identi?es the SQL state ment and determines, in step 404, Whether an existing access

ingly.
Another area Where empirical performance statistics can be used by a query optimiZer to improve generation of an access plan is related to data skeW. The physical arrangement of data on different devices affects the performance of data base operations. For example, if a particular query results in accessing data that is randomly scattered over a variety of different devices, then a large portion of the I/O operations
may occur in parallel. If the data to be accessed is concen trated on one or just a feW devices, then I/ O operations occur

plan, currently maintained by the query optimiZer, is available

for the query. If so, then that access plan is used, in step 406, to perform the query. If the query optimiZer can not locate a previously imple mented query access plan, then it searches, in step 408, the
records of the database monitor for a similar query or SQL

35

40

statement. One of ordinary skill Will recogniZe that there are a variety of Ways to measure similarity betWeen queries. The

mainly serially and performance is degraded. Other data skeW

situations may exist Where one particular device is especially
sloW such that any query plan that access that device runs
45

queries may be compared on their SQL syntax, their JOIN variables, their WHERE clauses, their host variables, and
other characteristics. If the present SQL query is similar to a

stored query, then the query optimiZer retrieves other perfor

mance statistics about the stored query from the database

much sloWer (e.g., 25 to 100 times) sloWer than average query plans. In large data Warehouses, a device may be a physical device or a logical partition. For example, a device may be

monitor records, in step 410. In step 412, the performance statistics of the stored query
are optionally checked to verify that it performed the query as estimated or With the estimated number of I/O operations. Alternatively, the performance statistics can be used to deter
mine the number of roWs fetched as compared to the number of roWs updated. This statistic may be used to determine if the
50

partition that is striped across multiple physical drives. Data skeW refers to the general condition in Which the physical
manner in Which the data is stored adversely affects the per

formance of performing certain I/ O operations.

The ?owchart of FIG. 6 illustrates one exemplary method for a query optimiZer to consider data skeW When selecting an

access plan for implementing an SQL statement. In step 602, the database monitor is queried to identify Which host vari
55

SELECT clause is su?iciently ?ltering records acted on by

the WHERE clause. The purpose of the determination in step 412 is to identify Whether the access plan tracked Within the database monitor is one that performed suf?ciently Well so as to recommend it to the query optimiZer. From the information in the database monitor records, the query optimiZer can be forced, in step 414, to use certain

ables are involved in query plans that executed x times sloWer than its estimated run time (Where x may be a variety of

numbers such as, but not limited to, betWeen 25-100). These
host variables are identi?ed as host variable that involve data
60

implementations to generate an access plan (e. g., join orders, indexes, etc.) instead of generating the entire access plan from scratch. In step 416, then, this access plan is executed to implement the query.
FIG. 5 illustrates a ?owchart of another exemplary use of

skeW. In step 604, the query optimiZer receives an SQL state ment and begins generation of an access plan in step 606. As part of the generation of the access plan, the query optimiZer determines, in step 608, if the current SQL statement includes
one or more host variables that have been identi?ed as involv

ing data skeW. If so, then the query optimiZer can force a
65

re-optimiZation in step 610 to ensure a neW access plan is generated from scratch. OtherWise, a current access plan can

performance statistics by a query optimiZer in accordance

be executed, in step 612, Without re-optimiZation, if available.

US 8,346,761 B2
10
The method described With relation to FIG. 6 is particularly

useful When the database management system is operating in

a mode known as reusable open data path (ODP) mode. The
ODP is a data structure Within an access plan that de?nes an

performance statistics When selecting an access plan for an SQL statement. Various modi?cations may be made to the

illustrated embodiments Without departing from the spirit and

scope of the invention. Therefore, the invention lies in the

active path through Which data is read. In reusable ODP mode, the ODP is kept open even When the SQL query that requested the path is closed. This speeds up data access the next time the path is needed. Reusable ODP mode improves

claims hereinafter appended.

What is claimed is: 1. A method for generating an access plan, the method

comprising the steps of:

maintaining in non-volatile memory a respective set of past performance statistics for each of a plurality of previ

performance but is particularly susceptible to performance

degradation due to data skeW. Thus, if a query in reusable ODP mode references a set of host variables that have been

ously executed database queries;

identifying a set of host variables referenced Within those

identi?ed as involving data skeW, it is particularly advanta

geous to exit the reusable ODP mode and force a re-optimi Zation of the query. If this attempt at re-optimiZation does not result in any improvements, then this set of host variables can be marked as especially harmful so that in the future no time or effort is Wasted to force re-optimiZation of queries that reference this set of host variables.

respective sets of past performance statistics that relate to data skeW performance degradation; and
forcing re-optimiZation to generate and store a neW access plan for a current SQL statement if the current database
query includes one or more host variables Within the

identi?ed set of host variables.

Anotherperformance statistic that is peripherally related to

data skeW involves information about When a table or ?le Was

2. The method of claim 1, further comprising the step of:

20

re-organiZed. Re-organiZation of a ?le changes its physical

layout on the different storage devices on Which a database is

determining if a current database query includes one or more of the identi?ed set of host variables.

implemented and implicates What index may improve ?le

access performance. Thus, query access plans that executed
before a ?le Was re-organiZed may, or may not, be the best
25

3. The method of claim 1, Wherein the step of identifying further includes the step of:
identifying a set of host variables references Within those

respective sets of past performance statistics that

executed sloWer than estimated.

access plan to implement an SQL statement. Thus, the query

optimiZer, When estimating l/O operations or When evaluat

ing estimated run times, in order to select an access plan, may also consider Whether a table or ?le has been re-organiZed
30

When determining hoW much Weight to assign the different

4. The method of claim 3, Wherein the step of identifying further includes the step of: identifying the set of host variables references Within those respective sets of past performance statistics that
executed betWeen 25 and 100 times sloWer than esti mated.

performance statistics.
Accordingly, a system and method has been described that

permits a query optimiZer to automatically consider empirical