After table-level recovery is performed, the schema information and its details are as follows:
| Schema information | Can be recovered? | Description |
|---|---|---|
| Database | No | During table-level recovery, the corresponding database in the target tenant must exist; otherwise, the recovery 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 place the table under the INFO database in the target tenant. |
| Tablespace | No | During table-level recovery, the corresponding tablespace in the target tenant must exist; otherwise, the recovery 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 place the table under the TS tablespace in the target tenant. |
| Table group | No | During table-level recovery, the corresponding table group in the target tenant must exist; otherwise, the recovery will fail. For example, if the backed-up table originally belonged to a table group named TG, and the REMAP TABLE command (which allows renaming the table to another table group in the target tenant) is not used, the system will place the table under the TG table group in the target tenant. |
| Table | Yes |
|
| Partition | Yes | N/A |
| Tablet | Yes | N/A |
| Column | Yes | N/A |
| Constraint | Yes | The following constraints can be recovered:
NoteIf the constraint name is user-defined and already exists in the target tenant, it will not be recovered. |
| Foreign key | Yes | During foreign key recovery, the system checks the integrity of the foreign key constraints. If a foreign key references a non-existent row, the foreign key recovery will fail. |
| View | No | Views associated with the table will not be recovered during table recovery. |
| Materialized view | No | Materialized views associated with the table cannot be recovered. |
| Materialized view log | No | Materialized view logs associated with the table cannot be recovered. |
| Local index | Yes | N/A |
| Global index | Yes | N/A |
| Full-text index | Yes | For V4.3.5, full-text indexes can be recovered starting from V4.3.5 BP4. |
| JSON multi-value index | Yes | For V4.3.5, JSON multi-value indexes can be recovered starting from V4.3.5 BP4. |
| Vector index | No | Vector indexes on the table will not be recovered during table recovery. |
| Spatial index | Yes | During table-level recovery, coordinate systems will not be recovered. If the target tenant does not have a reference coordinate system, spatial indexes will not be recovered; if the target tenant has a coordinate system, spatial indexes will be recovered. |
| Auto-increment column | Yes | N/A |
| Table without a primary key | Yes | N/A |
| Statistics | Yes | N/A |
| Trigger | Yes |
|
| Function, stored procedure, and package | No | Functions, stored procedures, and packages associated with the table will not be recovered during table recovery. |
| Synonym | No | Synonyms associated with the table will not be recovered during table recovery. |
| LOB | Yes | N/A |
| SEQUENCE | No | Sequences that the table depends on will not be recovered during table recovery. |