Best Practices for Using Native Object Store | VantageCloud Lake - Best Practices for Using NOS

Best Practices for Using Native Object Store | VantageCloud Lake - Best Practices for Using NOS - Teradata Vantage

Teradata® VantageCloud Lake

Deployment

VantageCloud

Edition

Lake

Product

Teradata Vantage

Published

January 2023

Language

English (United States)

Last Update

2024-04-03

dita:mapPath

phg1621910019905.ditamap

dita:ditavalPath

pny1626732985837.ditaval

dita:id

phg1621910019905

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 make sure 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.