Best Practices for Using Native Object Store | NOS | Teradata Vantage - Best Practices for Using NOS - Analytics Database - Teradata Vantage
Teradata Vantage™ - Native Object Store Getting Started Guide - 17.20
- Deployment
- VantageCloud
- VantageCore
- Edition
- Enterprise
- IntelliFlex
- VMware
- Product
- Analytics Database
- Teradata Vantage
- Release Number
- 17.20
- Published
- June 2022
- Language
- English (United States)
- Last Update
- 2024-10-04
- dita:mapPath
- tsq1628112323282.ditamap
- dita:ditavalPath
- qkf1628213546010.ditaval
- dita:id
- jjn1567647976698
- lifecycle
- latest
- Product Category
- Teradata Vantage
- To reduce the volume of data processed in the Analytics Database, either specify a more specific LOCATION string in the USING clause of the foreign table definition or use PATHPATTERN variables in the SQL statement.
- To ensure that path filtering is applied consistently, Teradata recommends that the database administrator capture path filtering (with appropriate casting of column data types) in a view of the foreign table and make the view available to end users.
- To improve performance of SQL statements with GROUP BY or ORDER BY clauses that include JSON files, cast values from their default VARCHAR data type to narrower data types.
- When joining a foreign table to either a relational table or another foreign table, collect statistics on the payload attribute that is used as a join constraint.
- If you generate spool tables, the spool is smaller if you cast values to narrower data types.