After a table-level recovery, the recovered schema information and its detailed explanation are as follows.
| Schema information | Restorable | Description |
|---|---|---|
| Database | No | When performing table-level restore, the corresponding database must exist in the target tenant; otherwise, the restore will fail. For example, if the backed-up table originally belonged to a database named INFO, and the REMAP TABLE command (which allows renaming the table to another database in the target tenant) is not used, the system will still restore the table into a database named INFO in the target tenant. |
| Tablespace | No | When performing table-level restore, the corresponding tablespace must exist in the target tenant; otherwise, the restore will fail. For example, if the backed-up table originally belonged to a tablespace named TS, and the REMAP TABLE command (which allows renaming the table to another tablespace in the target tenant) is not used, the system will still restore the table into a tablespace named TS in the target tenant. |
| Tablegroup (table group) | No | When you execute table-level recovery, the table group that corresponds to the table in the target tenant must exist. Otherwise, the recovery fails. For example, suppose that the backed up table belongs to the table group named TG in the source tenant. If you do not use the REMAP TABLE command (which allows you to rename the table to a different table group in the target tenant), the system will recover the table to the table group named TG in the target tenant. |
| Table | Yes | Only supports restoring user tables, including columnar and hybrid row-column storage formats. Does not support restoring system tables or temporary tables. |
| Partition | Yes | N/A |
| Tablet | Yes | N/A |
| Column | Yes | N/A |
| Constraint | Yes | Supported constraints for restore:
NoteIf the constraint name is user-defined and already exists in the target tenant, it will not be restored. |
| Foreign key | Yes | During foreign key restore, the system checks the integrity of the foreign key constraint. If a foreign key references a non-existent row, the foreign key restore will fail. |
| View | No | Views associated with the table are not restored. |
| Materialized view | No | Materialized views associated with the table are not supported for restore. |
| Materialized view log | No | Materialized view logs associated with the table are not supported for restore. |
| Local index | Yes | N/A |
| Global index | Yes | N/A |
| Full-text index | Yes | N/A |
| JSON multi-value index | Yes | N/A |
| Vector index | Yes | N/A |
| Spatial index | Yes | When performing table-level restore, coordinate systems are not restored. If the target tenant does not have a reference coordinate system, spatial indexes are not restored; if the target tenant has a coordinate system, spatial indexes are restored. |
| Auto-increment column | Yes | N/A |
| Table without primary key | Yes | N/A |
| Statistics | Yes | N/A |
| Trigger | Yes |
|
| Function, stored procedure, package | No | Functions, stored procedures, and packages associated with the table are not restored. |
| Synonym | No | Synonyms associated with the table are not restored. |
| LOB | Yes | N/A |
| SEQUENCE | No | Sequences that the table depends on are not restored. |