The following table compares ALTER TABLE TO CURRENT and ALTER TABLE … REVALIDATE. See General Rules and Restrictions for the REVALIDATE Option.
ALTER TABLE TO CURRENT | ALTER TABLE ... REVALIDATE |
---|---|
Periodically modify the partitioning. |
|
Resolves the DATE, CURRENT_DATE, and CURRENT_TIMESTAMP to their current values. | Uses the most recently resolved DATE, CURRENT_DATE, and CURRENT_TIMESTAMP values. |
Updates the partitioning information in the table header. | Updates the partitioning information in the table header. |
When reconciling the rows of the specified table or join index, Vantage skips any partition when it can determine that all of the rows in the partition would remain in that partition after reconciliation. This assumes that the rows of the table or join index are properly partitioned prior to submitting the ALTER TABLE TO CURRENT request. |
When reconciling the rows of the specified table, Vantage scans all of its partitions if you specify a null partition handler. This assumes that the rows of the table might not be properly partitioned before you submitted the current ALTER TABLE … REVALIDATE PRIMARY INDEX request. You cannot specify this option for join indexes. |
Reconciles all of the rows of the specified table or join index.
|
Only reconciles the rows of the specified table or join index if the request specifies a null partition handler. If you specify a WITH INSERT null partition handler for a table, Vantage deletes any rows that cannot be reconciled after saving them in a save table if the request specifies a WITH INSERT INTO save_table null partition handler. You cannot specify this option for join indexes. |