# CBO: about the statistical definition of “cardinality” (densities part I)

Let’s explore the concept of cardinality from the point of view of the statistician; this is both to get a clearer vision of the matter (i.e. for fun) and to path the way for understanding the rationale for the “density” statistics as calculated by dbms_stats (the topic of an upcoming post).

Let’s consider a statement with input parameters (bind variables), and consider the most fundamental of them all, the one with a filter predicate:

[sql]

select …

from t

where x = :x;

[/sql]

the cardinality “card” of the set of rows retrieved depends on the table possible values and the actual inputs provided by the client as bind variable values. What about the expected value E[card] ?

Let:

1) w(:x) (“w” stands for “workload”) the probability mass function of the random variable 😡 (that completely characterizes the workload);

2) E[count(:x)] the expected value of the cardinality of the rows retrieved for each value of :x.

We have, assuming that the two are independent:

[text]

E[card] = sum ( w(:x) * E[count(:x)] )

for all values of 😡

[/text]

To solve the formula we have to know (or assume) the client-dictated w(:x). The same goes for the table potential population (that -together with the statement of course- shapes E[count(:x)]); we must either have some statistical measurements about the table (for example, a frequency histogram on column X that we consider representative of the table population) or assume them (for example, assume a certain distribution for the column X values).

It is interesting to explore the most used scenario: a uniform (or assumed uniform) distribution for the column X values, of which we know the number of distinct values num_distinct(X) and the total number of values num_rows (let them be deterministically known for simplicity, and exclude null values). That means that E[count(:x)]) is equal to num_rows / num_distinct(X) *over a finite set that contains num_distinct(X) values* and is equal to zero over the remaining ones.

It is relatively easy to see that E[card] depends on how w(:x) and E[count(:x)]) overlap. At one end of the spectrum, if the client always submits values for 😡 that are not contained in the table, E[card] is zero – since the client choice matematically translates into E[count(:x)]) being zero over all values of 😡 for which w(:x) is non zero. At the other end of the spectrum, that is, under the non empty result set assumption, we have E[card] = sum ( w(:x) ) * num_rows / num_distinct(X) = num_rows / num_distinct(X), the usual formula used by the CBO in many (most) situations.

The “density” column statistic formula can be derived in a similar way, but using a different assumption about w(:x) – as we will see in a dedicated post.

Other posts belonging to this series:

densities part II

densities part III

densities part IV

## Leave a Reply to Blogroll Report 09/10/2009-16/10/2009 « Coskan’s Approach to Oracle Cancel reply