Selective Backup and Restore Rules | Teradata DSA - Selective Backup and Restore Rules - BAR - Data Stream Architecture

Teradata® DSA User Guide
Product
BAR
Data Stream Architecture
Release Number
17.00
Published
August 2020
Language
English (United States)
Last Update
2020-08-31
dita:mapPath
mas1575933453856.ditamap
dita:ditavalPath
vwp1576617377804.ditaval
dita:id
B035-3150
lifecycle
previous
Product Category
Software
Teradata Tools and Utilities
The table below lists individual object types, whether they can be restored or copied, and under what conditions. When performing a selective backup and restore on a table or database, observe the following rules.
  • Methods and UDTs are stored in SYSUDTLIB; SYSUDTLIB is only backed up or restored as part of a DBC backup.
  • Although an operation might be allowed, there is no guarantee the object will function as desired after the operation is complete.
Object Type Restore to Same DBS 1 Copy to Same DBS Copy and Rename to Same DBS Copy to Different DBS Copy and Rename to Different DBS
DB Level Object Level DB Level Object Level DB Level Object Level DB Level Object Level DB Level Object Level
Aggregate Function Yes Yes Yes Yes Yes No Yes Yes Yes No
JAR Yes Yes Yes Yes Yes No Yes Yes Yes No
External Stored Procedures Yes Yes Yes Yes Yes No Yes Yes Yes No
Standard Function Yes Yes Yes Yes Yes No Yes Yes Yes No
Function Alias

New with Advanced SQL Engine 16.20 Feature Update 1

 Yes Yes Yes Yes Yes No Yes Yes Yes No
Trigger Yes Yes No No No No No No No No
Instant or Constructor Method N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A
Join Index Yes Yes Yes Yes No No Yes Yes No No
Macro Yes Yes Yes Yes Yes No Yes Yes Yes No
Hash Index Yes Yes Yes Yes No No Yes Yes No No
Stored Procedure Yes Yes Yes Yes Yes No Yes Yes Yes No
Queue Table Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Table Function Yes Yes Yes Yes Yes No Yes   Yes No
Table Function (Operator) Yes Yes Yes Yes Yes No Yes Yes Yes No
Table Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
PPI Table Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
NOPI Table Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
User-Defined Data Type (UDT) N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A
View Yes Yes Yes Yes Yes No Yes Yes Yes No
Authorization Yes Yes Yes Yes Yes No Yes Yes Yes No
Parser Contract Function Yes Yes Yes Yes Yes No Yes Yes Yes No
System Join Index 2 Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
SQL-H 3,4 Yes Yes Yes Yes No No Yes Yes 4 No No
User Installed File (UIF) Yes Yes Yes Yes Yes No Yes Yes Yes No

1 DBS indicates an Advanced SQL Engine / Teradata Database system.

2 System Join Indexes (SJIs) can be copied to a different database and the database name can be changed but the object name cannot be changed.

3 All dependent objects used by the SQL-H object must exist prior to the copy.

4 To restore a backup job that contains a SQL-H object to a different database, the backup job source database must be the TD_SERVER_DB database.
Column Legend
Restore to Same DBS
Restore back to the same database name, same object name, and same Teradata system.
Copy to Same DBS
Copy back to the same database name, same object name, and same Teradata system.
Copy and Rename to Same DBS
Map to the same Teradata system and change either the database name, object name, or both.
Copy to Different DBS
Copy back to the same database name and same object name in a different Teradata system.
Copy and Rename to Different DBS
Map to a different Teradata system and change either the database name, object name, or both.