Avoiding backup and restore of selected tables

Deployment options: Netezza Performance Server for Cloud Pak for Data SystemNetezza Performance Server for Cloud Pak for DataNetezza Performance Server for Cloud Pak for Data as a Service

S

To avoid backing up and restoring a given table, you can use the BACKUP option on CREATE TABLE and ALTER TABLE:
  • CREATE TABLE ... [BACKUP [DATA] [ON | OFF]]
  • ALTER TABLE ... [BACKUP [DATA] [ON | OFF]]
By default (and on upgrade), a nontemporary user table is created with BACKUP ON, which matches the existing backup and restore behavior. BACKUP ON and BACKUP DATA ON are semantically equivalent. The other BACKUP choices are:
  • With BACKUP DATA OFF, the data for the specific table is not backed up and restored. This rule applies to both full and incremental backups. The table definition is backed up, and a restore creates a table with the specific definition but no data.
    Note: Queries against such a table in the target database cannot be expected to give meaningful results, since the data from the source table was not restored.
  • With BACKUP OFF, the table definition and the table data are not backed up.
    Note: nzrestore displays nonfatal errors when you are attempting to create dependent objects. For example, any views or synonyms dependent on a BACKUP OFF table are not be created. You can ignore these errors.