PreserveAfterRecreate Usage Notes - Teradata VantageCloud Lake
Lake - Monitor Resources and Performance
- Deployment
- VantageCloud
- Edition
- Lake
- Product
- Teradata VantageCloud Lake
- Release Number
- Published
- February 2025
- ft:locale
- en-US
- ft:lastEdition
- 2025-11-21
- dita:mapPath
- wyu1683671641248.ditamap
- dita:ditavalPath
- pny1626732985837.ditaval
- dita:id
- wyu1683671641248
- The use of this API should be limited to those tables that after being temporarily dropped are subsequently recreated with the exact same name, column definitions, and statistics definitions.
- To reverse the changes made by a call to PreserveAfterRecreate, a call can be made to related API DoNotPreserveAfterRecreate whose JSON keys are the same as above.
- In addition to objects marked semi-autonomous with the AUTODBA WITH CHECK syntax option, this API can also be used in conjunction with objects marked fully autonomous via the AUTODBA option (no WITH CHECK).