ASSOCIATE STATISTICS

Purpose

Use the ASSOCIATE STATISTICS statement to associate a statistics type (or default statistics) containing functions relevant to statistics collection, selectivity, or cost with one or more columns, standalone functions, packages, types, domain indexes, or indextypes.

For a listing of all current statistics type associations, query the USER_ASSOCIATIONS data dictionary view. If you analyze the object with which you are associating statistics, then you can also query the associations in the USER_USTATS view.

Prerequisites

To issue this statement, you must have the appropriate privileges to alter the base object (table, function, package, type, domain index, or indextype). In addition, unless you are associating only default statistics, you must have execute privilege on the statistics type. The statistics type must already have been defined.

Syntax

associate_statistics::=

Description of the illustration associate_statistics.gif


column_association::=

Description of the illustration column_association.gif


function_association::=

Description of the illustration function_association.gif


using_statistics_type::=

Description of the illustration using_statistics_type.gif


default_cost_clause::=

Description of the illustration default_cost_clause.gif


default_selectivity_clause::=

Description of the illustration default_selectivity_clause.gif

Semantics

column_association

Specify one or more table columns. If you do not specify schema, then Oracle Database assumes the table is in your own schema.

function_association

Specify one or more standalone functions, packages, user-defined datatypes, domain indexes, or indextypes. If you do not specify schema, then Oracle Database assumes the object is in your own schema.

• FUNCTIONS refers only to standalone functions, not to method types or to built-in functions.

• TYPES refers only to user-defined types, not to built-in SQL datatypes.

Restriction on function_association

You cannot specify an object for which you have already defined an association. You must first disassociate the statistics from this object.

using_statistics_type

Specify the statistics type (or a synonym for the type) being associated with column, function, package, type, domain index, or indextype. The statistics_type must already have been created.

The NULL keyword is valid only when you are associating statistics with a column or an index. When you associate a statistics type with an object type, columns of that object type inherit the statistics type. Likewise, when you associate a statistics type with an indextype, index instances of the indextype inherit the statistics type.You can override this inheritance by associating a different statistics type for the column or index. Alternatively, if you do not want to associate any statistics type for the column or index, then you can specify NULL in the using_statistics_type clause.

Restriction on Specifying Statistics Type

You cannot specify NULL for functions, packages, types, or indextypes.

default_cost_clause

Specify default costs for standalone functions, packages, types, domain indexes, or indextypes. If you specify this clause, then you must include one number each for CPU cost, I/O cost, and network cost, in that order. Each cost is for a single execution of the function or method or for a single domain index access. Accepted values are integers of zero or greater.

default_selectivity_clause

Specify as a percent the default selectivity for predicates with standalone functions, types, packages, or user-defined operators. The default_selectivity must be a number between 0 and 100. Values outside this range are ignored.

Restriction on the default_selectivity_clause

You cannot specify DEFAULT SELECTIVITY for domain indexes or indextypes.

Examples

Associating Statistics: Example

This statement creates an association for the standalone package emp_mgmt (created in "Creating a Package: Example"):

ASSOCIATE STATISTICS WITH PACKAGES emp_mgmt DEFAULT SELECTIVITY 10;

Specifying Default Cost: Example

This statement specifies that using the domain index t_a to implement a given predicate always has a CPU cost of 100, I/O cost of 5, and network cost of 0.

ASSOCIATE STATISTICS WITH INDEXES t_a DEFAULT COST (100,5,0);

The optimizer will use these default costs instead of calling a cost function.