Search Images Maps Play YouTube News Gmail Drive More »
Sign in
Screen reader users: click this link for accessible mode. Accessible mode has the same essential features but works better with your reader.

Patents

  1. Advanced Patent Search
Publication numberUS20040260675 A1
Publication typeApplication
Application numberUS 10/465,148
Publication dateDec 23, 2004
Filing dateJun 19, 2003
Priority dateJun 19, 2003
Also published asUS7299226
Publication number10465148, 465148, US 2004/0260675 A1, US 2004/260675 A1, US 20040260675 A1, US 20040260675A1, US 2004260675 A1, US 2004260675A1, US-A1-20040260675, US-A1-2004260675, US2004/0260675A1, US2004/260675A1, US20040260675 A1, US20040260675A1, US2004260675 A1, US2004260675A1
InventorsNicolas Bruno, Murali Krishna, Ming-Chuan Wu, Surajit Chaudhuri
Original AssigneeMicrosoft Corporation
Export CitationBiBTeX, EndNote, RefMan
External Links: USPTO, USPTO Assignment, Espacenet
Cardinality estimation of joins
US 20040260675 A1
Abstract
A method of estimating cardinality of a join of tables using multi-column density values and additionally using coarser density values of a subset of the multi-column density attributes. In one embodiment, the subset of attributes for the coarser densities is a prefix of the set of multi-column density attributes. A number of tuples from each table that participate in the join may be estimated using densities of the subsets. The cardinality of the join can be estimated using the multi-column density for each table and the estimated number of tuples that participate in the join from each table.
Images(7)
Previous page
Next page
Claims(42)
1. A method of estimating cardinality of a join of tables using multi-column density values, comprising:
a) identifying a multi-column density over a set of attributes for each table;
b) identifying a density of a subset of said set of attributes for each table;
c) estimating a number of tuples from each table that participate in the join using densities of the subsets;
d) estimating the cardinality of the join using the multi-column density for each table and the estimated number of tuples that participate in the join from each table.
2. The method of claim 1 wherein estimating a number of tuples of one of the tables that participate in the join comprises estimating a number of distinct values of a subset of said set of attributes in a first table, estimating a number of distinct values of a subset of said set of attributes in a second table, and multiplying a density of the subset of attributes in each table by a minimum of the estimated numbers of distinct values.
3. The method of claim 2 wherein the number of distinct values of a subset of said set of attributes in a table is calculated by dividing the cardinality of the table by the density of the subset of attributes in the table.
4. The method of claim 1 wherein said estimating cardinality comprises selecting the minimum of an estimated number of tuples from a first table that participate in the join divided by a multi-column density over a set of attributes for the first table and an estimated number of tuples from a second table that participate in the join divided by a multi-column density over a set of attributes for the second table and multiplying said minimum, said multi-column density over a set of attributes for the first table, and said multi-column density over a set of attributes for the second table.
5. The method of claim 1 wherein said subset comprises prefixes of said set of attributes.
6. The method of claim 1 wherein densities of a plurality of subsets of the set of attributes are used to calculate a plurality of cardinality estimations and a minimum of the plurality of cardinality estimations is selected as the cardinality estimation for the join.
7. A method of estimating cardinality of a join of tables using multi-column density values, comprising:
a) identifying a multi-column density over a set of attributes for each table;
b) identifying a density of a subset of said set of attributes for each table;
c) identifying a cardinality of each table;
d) estimating the cardinality of the join using the multi-column density for each table, the density of said subset of said set of attributes for each table, and the cardinality of each table.
8. The method of claim 7 further comprising estimating a number of tuples from each table that participate in the join using densities of the subsets and cardinalities of the tables and wherein the cardinality of the join is estimated using the multi-column density for each table and the estimated number of tuples that participate in the join from each table.
9. The method of claim 8 wherein estimating a number of tuples of one of the tables that participate in the join comprises estimating a number of distinct values of a subset of said set of attributes in a first table, estimating a number of distinct values of a subset of said set of attributes in a second table, and multiplying a density of the subset of attributes in each table by a minimum of the estimated numbers of distinct values.
10. The method of claim 8 wherein the number of distinct values of a subset of said set of attributes in a table is calculated by dividing the cardinality of the table by the density of the subset of attributes in the table.
11. The method of claim 8 wherein said estimating cardinality comprises selecting a minimum of an estimated number of tuples from a first table that participate in the join divided by a multi-column density over a set of attributes for the first table and an estimated number of tuples from a second table that participate in the join divided by a multi-column density over a set of attributes for the second table and multiplying said minimum, said multi-column density over a set of attributes for the first table, and said multi-column density over a set of attributes for the second table.
12. The method of claim 7 wherein said subset comprises prefixes of said set of attributes.
13. The method of claim 7 wherein estimating the cardinality comprises identifying a first minimum of a cardinality of a first table divided by a density of a subset of said set of attributes for the first table and a cardinality of a second table divided by a density of a subset of said set of attributes for the second table, identifying a second minimum of said density of said subset of said set of attributes for the first table divided by a multi-column density over said set of attributes for the first table and said density of said subset of said set of attributes for the second table divided by a multi-column density over said set of attributes for the second table, and multiplying said first minimum, said second minimum, said multi-column density over said set of attributes for the first table, and said multi-column density over said set of attributes for the second table.
14. The method of claim 7 wherein densities of a plurality of subsets of the set of attributes are used to calculate a plurality of cardinality estimations and a minimum of the plurality of cardinality estimations is selected as the cardinality estimation for the join.
15. In a method of estimating cardinality of a join of tables using a multi-column density over a set of attributes is identified for each table and the cardinality of each table, the improvement comprising additionally using a density of a subset of said set of attributes for each table to estimate the cardinality of the join.
16. The method of claim 15 wherein densities of said subsets are used to estimate a number of tuples from each table that participate in the join and the cardinality of the join is estimated using the multi-column density for each table and the estimated number of tuples that participate in the join from each table.
17. The method of claim 16 wherein estimating a number of tuples of each of the tables that participate in the join comprises estimating a number of distinct values of a subset of said set of attributes in a first table, estimating a number of distinct values of a subset of said set of attributes in a second table, and multiplying a density of the subset of attributes in each table by a minimum of the estimated numbers of distinct values.
18. The method of claim 17 wherein the number of distinct values of a subset of said set of attributes in a table is calculated by dividing the cardinality of the table by the density of the subset of attributes in the table.
19. The method of claim 16 wherein said estimating cardinality comprises selecting the minimum of an estimated number of tuples from a first table that participate in the join divided by a multi-column density over a set of attributes for the first table and an estimated number of tuples from a second table that participate in the join divided by a multi-column density over a set of attributes for the second table and multiplying said minimum, said multi-column density over a set of attributes for the first table, and said multi-column density over a set of attributes for the second table.
20. The method of claim 15 wherein said subset comprises prefixes of said set of attributes.
21. A method of estimating cardinality of a join of tables using multi-column density values and histograms, comprising:
a) identifying a multi-column density over a set of attributes for each table;
b) identifying a histogram over an attribute from said set of attributes for each table;
c) aligning buckets of each histogram
d) estimating for each bucket in a pair of aligned buckets a number of tuples from each table that participate in the join using densities of the buckets; and
e) estimating the cardinality of the join of a pair of buckets using the multi-column density for each table and the estimated number of tuples that participate in the join from each bucket in the pair of aligned buckets.
22. The method of claim 21 wherein the cardinality is estimated for each pair of buckets and is summed to estimate the cardinality of the join of tables.
23. A method of estimating cardinality of a join of tables using multi-column density values, comprising:
a) identifying a multi-column density over a set of attributes for each table;
b) identifying a histogram over an attribute from said set of attributes for each table;
c) aligning buckets of each histogram;
d) identifying a number of tuples in each bucket of a pair of aligned buckets;
e) estimating the cardinality of the join of the pair of buckets using the multi-column density for each table, the density of each bucket of the pair of buckets, and the number of tuples in each bucket of the pair of buckets.
24. The method of claim 23 wherein the cardinality is estimated for each pair of buckets and is summed to estimate the cardinality of the join of tables.
25. A computer readable medium having computer executable instructions stored thereon for performing a method of estimating cardinality of a join of tables using multi-column density values, the method comprising:
a) identifying a multi-column density over a set of attributes for each table;
b) identifying a density of a subset of said set of attributes for each table;
c) estimating a number of tuples from each table that participate in the join using densities of the subsets;
d) estimating the cardinality of the join using the multi-column density for each table and the estimated number of tuples that participate in the join from each table.
26. The computer readable medium of claim 25 wherein estimating a number of tuples of one of the tables that participate in the join comprises estimating a number of distinct values of a subset of said set of attributes in a first table, estimating a number of distinct values of a subset of said set of attributes in a second table, and multiplying a density of the subset of attributes in each table by a minimum of the estimated numbers of distinct values.
27. The computer readable medium of claim 26 wherein the number of distinct values of a subset of said set of attributes in a table is calculated by dividing the cardinality of the table by the density of the subset of attributes in the table.
28. The computer readable medium of claim 25 wherein said estimating cardinality comprises selecting the minimum of an estimated number of tuples from a first table that participate in the join divided by a multi-column density over a set of attributes for the first table and an estimated number of tuples from a second table that participate in the join divided by a multi-column density over a set of attributes for the second table and multiplying said minimum, said multi-column density over a set of attributes for the first table, and said multi-column density over a set of attributes for the second table.
29. The computer readable medium of claim 25 wherein said subset comprises prefixes of said set of attributes.
30. The computer readable medium of claim 25 wherein densities of a plurality of subsets of the set of attributes are used to calculate a plurality of cardinality estimations and a minimum of the plurality of cardinality estimations is selected as the cardinality estimation for the join.
31. A computer readable medium having computer executable instructions stored thereon for performing a method of estimating cardinality of a join of tables using multi-column density values, the method comprising:
a) identifying a multi-column density over a set of attributes for each table;
b) identifying a density of a subset of said set of attributes for each table;
c) identifying a cardinality of each table;
d) estimating the cardinality of the join using the multi-column density for each table, the density of said subset of said set of attributes for each table, and the cardinality of each table.
32. The computer readable medium of claim 31 wherein the method further comprises estimating a number of tuples from each table that participate in the join using densities of the subsets and cardinalities of the tables and wherein the cardinality of the join is estimated using the multi-column density for each table and the estimated number of tuples that participate in the join from each table.
33. The computer readable medium of claim 32 wherein estimating a number of tuples of each of the tables that participate in the join comprises estimating a number of distinct values of a subset of said set of attributes in a first table, estimating a number of distinct values of a subset of said set of attributes in a second table, and multiplying a density of the subset of attributes in each table by a minimum of the estimated numbers of distinct values.
34. The computer readable medium of claim 32 wherein the number of distinct values of a subset of said set of attributes in a table is calculated by dividing the cardinality of the table by the density of the subset of attributes in the table.
35. The computer readable medium of claim 32 wherein said estimating cardinality comprises selecting a minimum of an estimated number of tuples from a first table that participate in the join divided by a multi-column density over a set of attributes for the first table and an estimated number of tuples from a second table that participate in the join divided by a multi-column density over a set of attributes for the second table and multiplying said minimum, said multi-column density over a set of attributes for the first table, and said multi-column density over a set of attributes for the second table.
36. The computer readable medium of claim 31 wherein said subset comprises prefixes of said set of attributes.
37. The computer readable medium of claim 31 wherein estimating the cardinality comprises identifying a first minimum of a cardinality of a first table divided by a density of a subset of said set of attributes for the first table and a cardinality of a second table divided by a density of a subset of said set of attributes for the second table, identifying a second minimum of said density of said subset of said set of attributes for the first table divided by a multi-column density over said set of attributes for the first table and said density of said subset of said set of attributes for the second table divided by a multi-column density over said set of attributes for the second table, and multiplying said first minimum, said second minimum, said multi-column density over said set of attributes for the first table, and said multi-column density over said set of attributes for the second table.
38. The computer readable medium of claim 31 wherein densities of a plurality of subsets of the set of attributes are used to calculate a plurality of cardinality estimations and a minimum of the plurality of cardinality estimations is selected as the cardinality estimation for the join.
39. A computer readable medium having computer executable instructions stored thereon for performing a method of estimating cardinality of a join of tables using multi-column density values histograms, the method comprising:
a) identifying a multi-column density over a set of attributes for each table;
b) identifying a histogram over an attribute from said set of attributes for each table;
c) aligning buckets of each histogram
d) estimating for each bucket in a pair of aligned buckets a number of tuples from each table that participate in the join using densities of the buckets; and
e) estimating the cardinality of the join of a pair of buckets using the multi-column density for each table and the estimated number of tuples that participate in the join from each bucket in the pair of aligned buckets.
40. The computer readable medium of claim 39 wherein the cardinality is estimated for each pair of buckets and is summed to estimate the cardinality of the join of tables.
41. A computer readable medium having computer executable instructions stored thereon for performing a method of estimating cardinality of a join of tables using multi-column density values histograms, the method comprising:
a) identifying a multi-column density over a set of attributes for each table;
b) identifying a histogram over an attribute from said set of attributes for each table;
c) aligning buckets of each histogram;
d) identifying a number of tuples in each bucket of a pair of aligned buckets;
e) estimating the cardinality of the join of the pair of buckets using the multi-column density for each table, the density of each bucket of the pair of buckets, and the number of tuples in each bucket of the pair of buckets.
42. The computer readable medium of claim 41 wherein the cardinality is estimated for each pair of buckets and is summed to estimate the cardinality of the join of tables.
Description
FIELD OF THE INVENTION

[0001] The present disclosure concerns a method of estimating cardinality of a join of tables using multi-column density values, and more particularly, the present disclosure relates to a method of estimating cardinality of a join of tables using multi-column density values and additionally using coarser density values of a subset of the multi-column density attributes.

BACKGROUND ART

[0002] Relational databases systems allow a database user to enter queries into the database and return the data that meets the conditions of the query. The data present within the database system is in one or more tables or relations. Each relation consists of a number of records or tuples containing specific information possibly grouped in some ordered sequence. Each tuple consists of one or more fields called attributes. In any single attribute of a tuple there can be only a single value. However, each tuple can have a different value for the same attribute.

[0003] Some characteristics of a database relation are typically maintained. For example, the database system may maintain the cardinality, the density and the number of distinct values of each relation. Cardinality is the number of tuples or records in a relation. The number of distinct values is the number of distinct values of a given attribute or set of attributes. The density is the average number of tuples per distinct value.

[0004] One operation performed by a database system is known as a join operation. A join operation is used to combine related tuples from two relations into single tuples. Typically, the join operation matches tuples from two relations on the values taken from each relation on a common attribute and creates a joined table or relation. If another relation needs to be joined with the result relation, the result relation may be referred to as an intermediate relation because it is created in the process of generating a result relation.

[0005] Another operation performed by a database system is the select operation. The select operation is used to select a subset of tuples from a relation that satisfy a selection condition. One can consider the select operation to be a filter that keeps only those tuples that satisfy a qualifying condition.

[0006] A query entered into a relational database system may result in multiple operations being performed. For example, selection operations on one or more relations can be used together with multiple join operations in the same query. In many cases, the operations of the query can be performed in several different orders without changing the result of the query. Each possible order of operations is referred to as a query execution plan. There may be several alternative query execution plans, each specifying a set of operations to be executed by the database system. Each different query execution plan will have a different “cost.” The costs may include the cost of accessing secondary storage, computation cost, memory usage cost, and communication cost.

[0007] Relational database systems typically include a component called a query optimizer. The query optimizer may identify several query execution plans, estimate the cost of each different query execution plan, and select the plan with the lowest estimated cost for execution. Query plans generated for a query will differ in their total cost of obtaining the desired data. The query optimizer evaluates these cost estimates for each query plan in order to determine which plan is likely to have the lowest execution cost.

[0008] The join operation can be quite expensive, since joining together two or more entire relations can result in a very large relation. When multiple joins are present in a query, the cost of a bad execution plan may increase dramatically. It is important for the query optimizer to identify a query execution plan that minimizes cost. The join ordering chosen by the query optimizer is often a key factor in the ultimate cost of the query execution plan.

[0009] In view of these considerations, query optimizers often use estimates of the cardinality of joins in attempting to select the most efficient query plan. It may be desirable to estimate the cardinality of the join of a table R with a table S where attribute a of table R is equal to attribute b of table S, denoted R

R.a=S.bS. One prior art method of estimating the cardinality of such a join relied on what is referred to as the “containment assumption.” According to the containment assumption, each group of distinct valued tuples belonging to the relation with the minimal number of distinct values joins with some group of distinct valued tuples in the other table. The containment assumption has been extended to estimate the cardinality of a multi-predicate join. One problem with an existing method of estimating the cardinality of a multi-predicate using the containment assumption join is that cardinality is often overestimated.

[0010] There is a need for a method of estimating cardinality using multi-column density values and additionally using coarser density values of a subset of the multi-column density attributes to reduce the overestimation problem.

SUMMARY

[0011] The present disclosure concerns a method of estimating cardinality of a join of tables using multi-column density values and additionally using coarser density values of a subset of the multi-column density attributes. In one embodiment, the sequence of attributes for the coarser densities is a prefix of the sequence of multi-column density attributes.

[0012] In one embodiment of the method, a multi-column density over a set of attributes is identified for each table. A density of a subset of the set of attributes is also identified for each table. In this embodiment, a number of tuples from each table that participate in the join is estimated using densities of the subsets. The cardinality of the join is estimated using the multi-column density for each table and the estimated number of tuples that participate in the join from each table.

[0013] In one embodiment of the method, a multi-column density over a set of attributes and a cardinality is identified for each table. A density of a subset of the set of attributes is also identified for each table. The cardinality of the join is estimated using the multi-column density for each table, the density of said subset of said set of attributes for each table, and the cardinality of each table.

[0014] In one embodiment, the method improves an existing method of estimating cardinality of a join of tables using a multi-column density over a set of attributes. The method improves the existing method by additionally using a density of a subset of the set of multi-column density attributes for each table to estimate the cardinality of the join.

[0015] The number of tuples from each table that participate in the join may be estimated by multiplying an estimated minimum number of distinct values for the subset of attributes and a density of the subset of attributes in the table. The number of distinct values of a subset of attributes can be calculated by dividing the cardinality of the table by the density of the subset of attributes in the table.

[0016] In one embodiment, the join cardinality estimation is calculated by selecting the minimum of an estimated number of tuples from a first table that participate in the join divided by a multi-column density over a set of attributes for the first table and an estimated number of tuples from a second table that participate in the join divided by a multi-column density over a set of attributes for the second table. This minimum, the multi-column density for the first table, and the multi-column density for the second table are multiplied to calculate the estimated cardinality of the join.

[0017] In one embodiment, the cardinality estimation is calculated by identifying a first minimum value of a cardinality of a first table divided by a density of a subset of the set of multi-column density attributes for the first table and a cardinality of a second table divided by a density of a subset of the set multi-column density attributes for the second table. The method also identifies a second minimum value of the density of the subset of the set of multi-column density attributes for the first table divided by a multi-column density over the set of multi-column density attributes for the first table and the density of the subset of the set of multi-column density attributes for the second table divided by a multi-column density over the set of attributes for the second table. The first minimum value, the second minimum value, the multi-column density over the set of attributes for the first table, and the multi-column density over the set of attributes for the second table are multiplied to calculate the estimated cardinality of the join.

[0018] These and other objects, advantages, and features of an exemplary embodiment are described in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

[0019]FIG. 1 is a schematic depiction of a computer system used in practicing an exemplary embodiment of the disclosed method;

[0020]FIG. 2 is illustrates a method of estimating the cardinality of a join of two relations using single column densities;

[0021]FIG. 3A illustrates a method of estimating the cardinality of a join of two relations using multi-column densities;

[0022]FIG. 3B illustrates a method of estimating the cardinality of a join of two relations using multi-column densities;

[0023]FIG. 4 is a flow chart that illustrates a method of estimating cardinality of a join of two relations using multi-column densities and densities of subsets of multi-column density attributes; and

[0024]FIG. 5 illustrates a method of estimating the cardinality of a join of two relations using histograms and multi-column densities.

DETAILED DESCRIPTION

[0025] Exemplary Operating Environment

[0026]FIG. 1 and the following discussion are intended to provide a brief, general description of a suitable computing environment in which the invention may be implemented. Although not required, the invention will be described in the general context of computer-executable instructions, such as program modules, being executed by a personal computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the invention may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

[0027] With reference to FIG. 1, an exemplary system for implementing the invention includes a general purpose computing device in the form of a conventional personal computer 20, including a processing unit 21, a system memory 22, and a system bus 24 that couples various system components including system memory 22 to processing unit 21. System bus 23 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. System memory 22 includes read only memory (ROM) 24 and random access memory (RAM) 25. A basic input/output system (BIOS) 26, containing the basic routines that help to transfer information between elements within personal computer 20, such as during start-up, is stored in ROM 24. Personal computer 20 further includes a hard disk drive 27 for reading from and writing to a hard disk, a magnetic disk drive 28 for reading from or writing to a removable magnetic disk 29 and an optical disk drive 30 for reading from or writing to a removable optical disk 31 such as a CD ROM or other optical media. Hard disk drive 27, magnetic disk drive 28, and optical disk drive 30 are connected to system bus 23 by a hard disk drive interface 32, a magnetic disk drive interface 33, and an optical drive interface 34, respectively. The drives and their associated computer-readable media provide nonvolatile storage of computer-readable instructions, data structures, program modules and other data for personal computer 20. Although the exemplary environment described herein employs a hard disk 27, a removable magnetic disk 29 and a removable optical disk 31, it should be appreciated by those skilled in the art that other types of computer-readable media which can store data that is accessible by computer, such as random access memories (RAMs), read only memories (ROMs), and the like may also be used in the exemplary operating environment.

[0028] A number of program modules may be stored on the hard disk 27, magnetic disk 29, optical disk 31, ROM 24 or RAM 25, including an operating system 35, one or more application programs 36, other program modules 37, and program data 38. A database system 55 may also be stored on the hard disk, magnetic disk 29, optical disk 31, ROM 24 or RAM 25. A user may enter commands and information into personal computer 20 through input devices such as a keyboard 40 and pointing device 42. Other input devices may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to processing unit 21 through a serial port interface 46 that is coupled to system bus 23, but may be connected by other interfaces, such as a parallel port, game port or a universal serial bus (USB). A monitor 47 or other type of display device is also connected to system bus 23 via an interface, such as a video adapter 48. In addition to the monitor, personal computers typically include other peripheral output devices such as speakers and printers.

[0029] Personal computer 20 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 49. Remote computer 49 may be another personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to personal computer 20, although only a memory storage device 50 has been illustrated in FIG. 1. The logical connections depicted in FIG. 1 include local area network (LAN) 51 and a widearea network (WAN) 52. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets, and the Internet.

[0030] When using a LAN networking environment, personal computer 20 is connected to local network 51 through a network interface or adapter 53. When used in a WAN networking environment, personal computer 20 typically includes a modem 54 or other means for establishing communication over wide area network 52, such as the Internet. Modem 54, which may be internal or external, is connected to system bus 23 via serial port interface 46. In a networked environment, program modules depicted relative to personal computer 20, or portions thereof, may be stored in remote memory storage, device 50. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.

[0031] Notation

[0032] In this disclosure, tables are represented by uppercase letters. For example, tables may be represented by uppercase letters R; S; T . . . Table attributes are represented by lowercase letters. For example, table attributes may be represented by lowercase letters a; b; c . . . The cardinality of a table R is denoted as cardR or |R|. For a given attribute a of table R, the density of attribute a in table R, denoted δR.a, is the average number of duplicates per distinct value of attribute a in R. The number of distinct values of attribute a in table R is denoted dvR.a. As a result, dvR.a=cardRR.a.

[0033] A multi-column density MCD for attributes a1, . . . ,an of table R is denoted as δR.a1, . . . ,an The multi-column density δR.a1, . . . ,an is the average number of duplicates per distinct combination of attributes a1, . . . ,an. In this disclosure, the number of distinct combinations of a1, . . . ,an in table R are denoted as dvR.a1, . . . ,an. As such, the number of distinct attribute combinations dvR.a1, . . . ,an=cardRR.a1, . . . ,an. It is assumed in this disclosure that whenever multi-column densities are available over attributes a1, . . . ,an the densities of prefix subsets of the original multi-column density are also available. For the multi-column density of a1, . . . ,an the densities of the prefixes: (a1), (a1, a2); (a1, a2, a3), . . . ,(a1,a2, . . . ,an−1) are also available.

[0034] Join Estimation Using Containment Assumptions

[0035] The cardinality of the join of table R with table S where attribute a of table R is equal to attribute b of table S is denoted R

R.a=S.bS. According to the containment assumption, each group of distinct valued tuples belonging to the relation with the minimal number of distinct values joins with some group of distinct valued tuples in the other table. This is illustrated by the example of FIG. 2. In the example of FIG. 2 table R has a cardinality cardR=100, there are twenty distinct values of attribute a dvR.a=20 and therefore, the density of attribute a is δR.a=5. Table S has a cardinality cardS=100, there are one hundred distinct values of attribute b dvS.b=100 (all values of b are different in the example), and therefore, the density of attribute b is δS.b=1. Applying the containment assumption to the example of FIG. 2, relation R has the fewest number groups with distinct values, i.e. 20 groups. The containment assumption assumes that each group of distinct valued tuples of table R join with a group of distinct valued tuples in table S, which in the example is a single tuple in S. The arrows 104 between table R and table S illustrate this. According to the containment assumption, a group 100 of tuples (five tuples in the example) with attribute a having a value vala1 will join with a group 102 of tuples (one tuple in the example) with attribute b having a value valb1 as indicated by arrow 104. Similarly the groups of tuples from relation R having values vala2, . . . ,vala20 will join with groups of tuples from relation S having values vala2, . . . ,vala20 respectively. Note in the example of FIG. 2 that groups (single tuples in the example) 21-100 of table S do not participate in the join.

[0036] Using the containment assumption, an estimated cardinality of the join is calculated as: card R R . a = S . b S = min ( card R δ R . a , card S δ S . b ) · δ R . a · δ S . b Equation 1

[0037] Applying Equation 1 to the example of FIG. 2, the estimated cardinality of the join R R . a = S . b S is : = min ( dv R . a = 20 , dv S . b = 100 ) ( δ R . a = 5 ) ( δ S . b = 1 ) = ( 20 ) ( 5 ) ( 1 ) = 100

[0038] Considering the multi-predicate join of table R with table S where attribute a of table R is equal to attribute b of table S and attribute c of table R is equal to attribute d of table S, denoted R

R.a=S.bR.c=S.dS. The estimation calculation of Equation 1 can be extended to this multi-predicate join to define the estimated cardinality of the multi-predicate join as: card R R . a = S . b R . c = S . d S = min ( card R δ R . a , c , card S δ S . b , d ) · δ R . a , c · δ S . b , d Equation 2

[0039] This estimation is correct under the containment assumption in absence of additional information, such as partial densities. If the densities of the prefixes of the multi-column densities (e.g., δR.aR.b) are also available, the estimation of Equation 2 could be an overestimate of the cardinality. The example illustrated by FIG. 3 shows how use of Equation 2 can overestimate cardinality.

[0040]FIGS. 3A and 3B illustrate the join predicate R

R.a=S.bR.c=S.dS. Suppose cardR=1000, cardS=1000 and that δR.a,c=10 and δR.b,d=1. Referring to FIG. 3A, there are 100 groups of tuples with distinct values dvR.a,c of the combination of attributes a and c and there are 1000 groups of tuples (1 tuple per group in the example) with distinct values dvS.b,d In FIG. 3A, according to Equation 2, a group 108 of ten tuples with attribute a having a value vala1 and attribute c having a value valc1 will join with a group 110 of tuples (one tuple in the example) with attribute b having a value valb1 and attribute d having a value vald1 as indicated by arrow 112 Similarly the ninety-nine remaining groups of ten tuples with the same value on attributes a and c from relation R will join with one tuple from relation S. Therefore, using the containment assumption the estimated cardinality according to Equation 2 is: min ( card R δ R . a , c ; card S δ S . b , d ) · δ R . a , c · δ S . b , d = min ( dv R . a , c = 1000 / 10 , dv S . b , c = 1000 / 1 ) ( δ R . a , c = 10 ) ( δ S . b , d = 1 ) min ( 100 , 1000 ) * 10 * 1 = 100 * 10 = 1000.

[0041] Using Coarser Densities to Reduce Overestimation

[0042] Using Equation 2 in the Example of FIGS. 3A and 3B assumes that all tuples from R join with some tuple in S, since dvR.a,c=100<1000=dvR.b,d. Suppose that in the example of FIGS. 3A and 3B, the following additional density information about a subset of the attributes of the multi-column density is also available: δR.a=100 and δS.b=500. These are the densities of the prefixes of the multi-column densities δR.a,c and δR.b,d. These densities of the prefixes allow the table R to be modeled as consisting of ten groups (dvR.a) of one-hundred tuples each (δR.a) where each item in a group has the same attribute value R.a. Referring to FIG. 3B, a first group 114 of one-hundred tuples is modeled as having value vala1 in the example. In FIG. 3B, the remaining nine groups of one-hundred tuples have values vala2, . . . ,vala10. The prefix densities allow table S to be modeled as consisting of two groups 116, 118 (dvS.b) of 500 tuples each (δS.b), where each member of a group has the same attribute value S.b. In FIG. 3B, the first group 116 of five-hundred tuples is illustrated as having value valb1 and the second group 118 of five-hundred tuples is illustrated as having value valb2. This information does not contradict the original multi-column densities. Rather, this information simply models a coarser distribution for table R (i.e. a GROUP BY R.a of the different combinations of R.a, R.c). In FIG. 3B, arrows 120, 122 illustrate that at most two out of the ten groups of table R (grouped by R.a alone) would match with tuples in table S, since there are only two groups with different values of attribute S.b. Therefore, the remaining 8 groups in table R (80% of the tuples in R) would not participate in a match, which is a great restriction over the first calculation that uses only the original multi-column densities.

[0043] In one embodiment, the multicolumn density δR.a,c, the multi-column density δR.b,d, and the density information δR.aR.b, about a prefix subset of the multi-column density attributes is also available. This density information can be used to estimate the cardinality of R

R.a=S.bR.c=S.dS by using a two-step approach. This two-step approach is illustrated by FIG. 4. In the exemplary embodiment, the method first estimates 130 how many tuples from R and S participate in the simpler join R R.a=S.bS using the containment assumption and the coarser subset density information δR.a and δS.b. The estimated number of tuples in table R that participate in the simpler join R R.a=S.bS is: min ( card R δ R . a , card S δ S . b ) · δ R . a . Equation 3

[0044] Analogously, the number of tuples in S that participate in this simpler join is: min ( card R δ R . a , card S δ S . b ) · δ S . b . Equation 4

[0045] In a second step, the cardinality of the original join R

R.a=S.bR.c=S.dS is estimated 132 using the estimated number tuples from R and S that participate in the simpler join R R.a=S.bS (using the Equations 3 and 4) instead of the cardinality of R cardR and the cardinality of S cardS. The observation is that any tuple from table R or table S that does not participate in the simpler join will not participate in the original join, since the latter contains an additional equality predicate. Therefore, in the exemplary embodiment the method replaces the actual cardinalities cardR and cardS in estimation Equation 2 with the estimated number of tuples from table R and table S that participate in the simpler join defined by Equations 3 and 4 respectively. In this way, the method removes from table R and table S tuples that are do not to participate in the join when the containment assumption is applied. This assumes that the values of densities δR.a,c and δS.b,d are unchanged after removing the tuples that do not participate in the join. The resulting estimation equation is: card R R . a = S . b R . c = S . d S = ( min ( card R δ R . a · card S δ S . b ) · δ R . a δ R . a , c , min ( card R δ R . a ; card S δ S . b ) · δ S . b δ S . b , d ) · δ R . a , c · δ S . b , d . Equation 5

[0046] By extracting the common factor min ( card R δ R . a , card S δ S . b )

[0047] Equation 5 reduces to: card R R . a = S . b R . c = S . d S = min ( card R δ R . a , card S δ S . b ) · min ( δ R . a δ R . a , c · δ S . b δ S . b , d ) · δ R . a , c · δ S . b , d . Equation 6

[0048] If the densities of the other prefixes are available from the construction of the original multi-column densities i.e., densities δR.c, δR.c,a. δ S.d, δS.d,b using the arguments applied above, the cardinality R

R.a=S.bR.c=S.dS can be estimated by Equation 7. card R R . a = S . b R . c = S . d S = min ( card R δ R . c , card S δ S . d ) · min ( δ R . c δ R . c , a , δ S . d δ S . d , b ) · δ R . c , a · δ S . d , b . Equation 7

[0049] The two estimations returned using Equations 6 and 7 can be different. In such a case, since all these estimations are estimated upper bounds for the join, the exemplary method takes the minimal one estimate.

[0050] In one embodiment, Equation 7 is generalized for any number n (greater than 2) of equalities in the join predicate, by recursively applying the method described above. In general, for a join with a number n predicates there can be n! (n factorial) different permutations of multi-column densities and subsets of prefixes. If all of the densities are available, the method selects the minimum estimation of the cardinality in one embodiment. However, in one embodiment only a selected number of the possible estimations are calculated. This may be done either to be efficient or because not all combinations of the multi-column densities are available. Regardless of how many of the possible estimations are calculated using the disclosed method, the disclosed estimation method guarantees that the minimal value among the estimations is at least as accurate as the estimation obtained if the single multi-column densities were just used by themselves in Equation 2.

[0051] Situations When Using Coarser Subset Densities Reduces Overestimation

[0052] Equation 6 has the following basic form:

min(a1/b1, a2/b2)*min(b1/c1, b2/c2)*c1*c2. where:

[0053] a1=cardR

[0054] a2=cardS

[0055] b1=δR.a

[0056] b2=δS.b

[0057] c1=δR.a,c

[0058] c2=δS.b,d

[0059] Original estimation equation 2, which does not consider the coarser densities has the following basic form:

min(a1/c1, a2/c2)*c1*c2.

[0060] If a1/b1<a2/b2 and b1/c1<b2/c2, i.e., both min operators of Equation 6 return the first parameter, then the min operator of Equation 2 also returns the first parameter, and the result of both equations is exactly the same. That is, Equation 6 reduces to Equation 2, since a 1 b 1 × b 1 c 1 = a 1 c 1 .

[0061] Analogously, if both min operators of Equation 6 return the second parameter, then the min operator of Equation 2 returns the second parameter, and the result of Equations 2 and 6 is the same. That is, Equation 6 reduces to Equation 2, since a 2 b2 × b 2 c 2 = a 2 c 2 .

[0062] However, if the first min operator of Equation 6 returns the first parameter, and the second min operator of Equation 6 returns the second parameter, both equations might return different values. That is, Equation 6 does not reduce to Equation 2, since, in general, a 1 b 1 × b 2 c 2

[0063] is different from either a 1 c 1 or a 2 c 2 .

[0064] Similarly, if the first min operator of Equation 6 returns the second parameter, and the second min operator of Equation 6 returns the first parameter, both equations might return different values. Again, Equation 6 doe not reduce to Equation 2, since a 2 b 2 × b 1 c 1

[0065] is in general different from either a 1 c 1 or a 2 c 2 .

[0066] In such cases, Equation 6 provides a tighter upper bound than Equation 2 and is thus more accurate. The following example query illustrates how this situation arises:

EXAMPLE

[0067] SELECT*FROM part, supplier, lineitem

[0068] WHERE

[0069] p_partkey=l_partkey AND

[0070] s_suppkey=l_suppkey AND

[0071] p_name like ‘% green’

[0072] OPTION (force order)

[0073] In the example, the database TPC-H is used. The following values are obtained from the TPC-H database where S=supplier, P=part, and L=lineitem.

[0074] cardS=1000, δS.suppkey=1

[0075] cardP=20000, δP.partkey=1

[0076] cardL=600000, δL.partkey,suppkey=7.5,δL.partkey=30, δL.suppkey=600

[0077] The filter σpname like ‘green’ returns the following information where σgreenP is denoted σP:

[0078] cardσP=200, δσP.partkey=1

[0079] After applying the Cartesian product, it can be estimated (denoting “S×σP” as x) that

[0080] cardx=1000*200=200000

[0081] δx.partkey,suppkey=1 (it is the product of the original densities).

[0082] δx.partkey=1000 (since each distinct partkey value was combined with all 1000 suppliers).

[0083] δx.suppkey=200 (since each distinct suppkey value was combined with all 200 green parts).

[0084] All the information in the above example can be derived from the Cartesian product alone, without considering key information. This information can be used to estimate the size of the join L

partkey=partkeysuppkey=suppkeyx. If the multi-column densities δL.partkey,suppkey and δx.partkey,suppkey are used with Equation 2, the estimated cardinality is calculated as follows: L partkey = partkey suppkey = suppkey x = min ( card L δ L . partkey . suppkey · card x δ x . partkey . suppkey ) · δ L . partkey . suppkey · · δ x . partkeys · uppkey = min ( 600000 / 7 * 5 , 200000 / 1 ) * 7.5 * 1 = 80000 * 7.5 = 600 , 000

[0085] By applying Equation 6 it will be shown that 600,000 is an overestimate of the cardinality. The estimated cardinality using equation 6 multi-column densities δL.partkey,suppkey and δx.partkey,suppkey, and the additional prefix density information δL.partkey and δx.partkey is calculated as follows: L partkey = partkey suppkey = suppkey x = min ( card L δ L . partkey · card x δ x . partkey ) min ( δ L . partkey δ L . partkey . suppkey · δ x . partkey δ x . partkey .. suppkey ) · δ L . partkey · · suppkey · · δ x . partkey · suppkey = min ( 600000 / 30 , 200000 / 1000 ) * min ( 30 / 7.5 , 1000 / 1 ) * 7.5 * 1 = min ( 20000 , 200 ) * min ( 4 , 1000 ) * 7.5 * 1 = 200 * 4 * 7.5 = 6000

[0086] Note that the results of the first min operation is the second parameter, while the result for the second min operation is the first parameter. Had the other possible multi-column densities, i.e., δL.suppkey,partkey and δx.suppkey,partkey, and the additional prefix density information δL.suppkey and δx.suppkey, the cardinality is calculated as follows: L partkey = partkey suppkey = suppkey x = min ( card L δ L . suppkey . · card x δ x . suppkey . ) · min ( δ L . suppkey δ L . suppkey · . partkey . · δ L . suppkey δ x . suppkey · . partkey ) · δ L .. suppkey · · partkey · δ x . suppkey · partkey = min ( 600000 / 600 , 200000 / 200 ) * min ( 600 / 7.5 , 200 / 1 ) * 7.5 * 1 = min ( 1000 , 1000 ) * min ( 80 , 200 ) * 7.5 * 1 = 1000 * 80 * 7.5 = 600 , 000

[0087] In the exemplary embodiment, the method takes the minimum over these two refined estimations (min (600000, 6000)=6000) to obtain the estimated cardinality estimation. The estimated cardinality returned in this example is an accurate estimation (the actual value obtained by running the query on TPC-H is 6629).

[0088] Extending the Method to Histograms

[0089] In one embodiment, the disclosed method of estimating cardinality using multi-column densities can be extended to histograms. Referring to FIG. 5, suppose a multi-column density over R.a, R.c is available, a multi-column density over S.b, S.d is available and histograms 150, 152 over R.a and S.b are also available. In one embodiment, the disclosed method can simply extend the information in each histogram bucket with the single value δR.a,c or δS.b,d coming from the multi-column densities. In this embodiment, each histogram bucket currently represents δR.a and δS.b duplicates for each distinct value of R.a and S.b respectively. In such a case, the method chooses to use an extended histogram as opposed to the multi-column density. The reasoning behind this decision is that more detailed information about one column (R.a) is available and no multi-column density information is lost, since the bucket information is extended with the multi-column density value.

[0090] Referring to FIG. 5, the buckets 154 of the histogram 150 for R.a are aligned with the buckets 156 of the histogram 152 for S.b. For each pair of buckets, the multi-column density values δR.a,c, δS.b,d and the information in the pair of buckets (number of tuples in each bucket, density of each bucket) can be used in Equation 7 to calculate the cardinality for the pair of buckets. The results for the pairs of buckets are added together to estimate the cardinality of the join.

[0091] While the present invention has been described with a degree of particularity, it is the intent that the invention include all modifications and alterations falling within the spirit or scope of the appended claims.

Referenced by
Citing PatentFiling datePublication dateApplicantTitle
US7249120 *Jun 27, 2003Jul 24, 2007Microsoft CorporationMethod and apparatus for selecting candidate statistics to estimate the selectivity value of the conditional selectivity expression in optimize queries based on a set of predicates that each reference a set of relational database tables
US7552119Dec 20, 2006Jun 23, 2009International Business Machines CorporationApparatus and method for skipping XML index scans with common ancestors of a previously failed predicate
US7630967Nov 22, 2005Dec 8, 2009At&T Intellectual Property Ii, L.P.Join paths across multiple databases
US7685098 *Dec 8, 2005Mar 23, 2010International Business Machines CorporationEstimating the size of a join by generating and combining partial join estimates
US7716210Dec 20, 2006May 11, 2010International Business Machines CorporationMethod and apparatus for XML query evaluation using early-outs and multiple passes
US7865502 *Apr 10, 2008Jan 4, 2011International Business Machines CorporationOptimization of extensible markup language path language (XPATH) expressions in a database management system configured to accept extensible markup language (XML) queries
US7945558 *Jan 9, 2008May 17, 2011Hewlett-Packard Development Company, L.P.Query optimizer with join cardinality estimation which mitigates the effects of skew
US8112459Dec 17, 2004Feb 7, 2012International Business Machines CorporationCreating a logical table from multiple differently formatted physical tables having different access methods
US8131744Dec 17, 2004Mar 6, 2012International Business Machines CorporationWell organized query result sets
US8214352Nov 24, 2009Jul 3, 2012Hewlett-Packard Development CompanyModular query optimizer
US8312027Jun 5, 2012Nov 13, 2012Hewlett-Packard Development Company, L.P.Modular query optimizer
US8392403 *Sep 18, 2009Mar 5, 2013Microsoft CorporationManagement of data and computation in data centers
US20110072006 *Sep 18, 2009Mar 24, 2011Microsoft CorporationManagement of data and computation in data centers
WO2010062994A2 *Nov 25, 2009Jun 3, 2010Vertica Systems, Inc.Modular query optimizer
Classifications
U.S. Classification1/1, 707/999.002
International ClassificationG06F17/30
Cooperative ClassificationY10S707/962, Y10S707/99937, Y10S707/99935, Y10S707/99936, G06F17/30333, G06F17/30469
European ClassificationG06F17/30S4P3T5S, G06F17/30S2P7
Legal Events
DateCodeEventDescription
Apr 20, 2011FPAYFee payment
Year of fee payment: 4
Mar 31, 2005ASAssignment
Owner name: MICROSOFT CORPORATION, WASHINGTON
Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNOR S NAME, PREVIOUSLY RECORDED ON REEL 014204 FRAME 0163;ASSIGNORS:BRUNO, NICOLAS;KRISHNA, MURALI;WU, MING-CHUAN;AND OTHERS;REEL/FRAME:015863/0202;SIGNING DATES FROM 20030613 TO 20030617
Jun 19, 2003ASAssignment
Owner name: MICROSOFT CORPORATION, WASHINGTON
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BRUNO, NICOLAS;KRISHNA, MURALI;WU, MING-CHUEN;AND OTHERS;REEL/FRAME:014204/0163;SIGNING DATES FROM 20030613 TO 20030617