MarkAutoDBAObjects 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
- Temporary tables and Error tables will automatically be skipped as per AUTODBA marking rules. For more information, refer to SQL Data Definition Language and the usage of the AUTODBA option within DDL statements.
- To mark a specific database, callers should specify a value for DatabaseName.
- To mark a specific table, callers should specify a value for both DatabaseName and TableName.
- DatabaseName and TableName should not contain wildcard characters (%, _).
- When the desired scope of the marking operation involves a list of objects that cannot be specified using parameters DatabaseName or TableName, callers can alternatively specify an ObjectListName that was previously created by APIs CreateObjectList and AddObjectListEntry. See ObjectList APIs.
- ObjectListName usage is mutually exclusive with DatabaseName and TableName. When a non-NULL value is specified for ObjectListName, DatabaseName and TableName must be NULL.
- DatabaseName,TableName, and ObjectListName cannot all be NULL. At least one object must be specified.
- A value for AutoDBA must be specified by the caller and cannot be left NULL.
- Join indexes cannot be explicitly marked and instead inherit the marking option of the base tables on which they are defined.