SetObjectOption 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
- To set an option at the system level, omit ObjectListName, DatabaseName and TableName.
- To set an option for all tables and their statistics within a given database, callers should specify a value for DatabaseName only.
- To set an option for all statistics in a given table, callers should specify a value for both DatabaseName and TableName.
- A table option set via this API supersedes any associated values specified in calls to APIs that perform tuning analysis or statistics collections.
- If the table option is already set for a table, the current option will be overwritten by the value specified in any subsequent call to the API.
- When the desired scope of the operation involves a list of objects that cannot be specified via parameters DatabaseName or TableName, callers can alternatively specify an ObjectListName that was previously created by APIs CreateObjectList and AddObjectListEntry.
- ObjectListName usage is mutually exclusive with DatabaseName and TableName. When a non-NULL value is specified for ObjectListName, DatabaseName and TableName must not be specified.
- 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).