15.00 - Guideline for Refreshing Partition Statistics After An ALTER TABLE TO CURRENT Request - Teradata Database

Teradata Database SQL Data Definition Language Detailed Topics

prodname
Teradata Database
vrm_release
15.00
category
Programming Reference
featnum
B035-1184-015K

Guideline for Refreshing Partition Statistics After An ALTER TABLE TO CURRENT Request

You might need to refresh the partition statistics for a table or join index after you resolve its date or timestamp values because, depending on the options you specify for the request, those statistics can become stale after an ALTER TABLE TO CURRENT request completes.

The following table presents guidelines for refreshing statistics on the columns specified in the partitioning expression of a table or join index after an ALTER TABLE TO CURRENT request.

 

IF the ALTER TABLE TO CURRENT request …

THEN partition statistics …

specifies a null partition handler

are stale after the request completes.

You should refresh partition statistics for this case.

does not specify a null partition handler

are not stale after the request completes.

There is no need to refresh partition statistics for this case.

If an ALTER TABLE TO CURRENT request is submitted for a table or join index, the PARTITION statistics for the affected table or join index always become stale and you must refresh them after the request completes.