Native Object Store (NOS) allows external data to be accessed and integrated into Teradata Vantage. For this release, NOS has been enhanced with the WRITE_NOS feature.
WRITE_NOS is a table operator that allows you to write data from database tables to external object storage and store it in Parquet data format.
- Allows you to free up database space by offloading old or cold data to cheaper external object storage
- Offloading data to object storage may reduce the overall cost of storage
- Data written to object store using WRITE_NOS is optimized to be read back by foreign table
- Offloaded Parquet data can be queried (with foreign table). This enables you to meet compliance standards for retaining data
- Write data to various external sources, such as Amazon Web Services, Microsoft Azure (including Azure Data Lake Storage Gen2 in Blob Interop Mode), and Google Cloud Services.
- The maximum size of the output object is 16,776,192 bytes (including LOB and LOB-based UDT columns), which is the same as the read size of 16,776,192 bytes
- GZIP and SNAPPY are the supported compression algorithms for Parquet data
- Redshift is the supported format for the manifest files
- Parquet is the supported data format
- It is the responsibility of the user to clean up object store files on write failures interrupted write operations. Write operations can be interrupted on transaction aborts or system resets, among other reasons.
- Teradata recommends using WRITE_NOS to offload data during a batch window
- WRITE_NOS uses a large amount of memory.
- New WRITE_NOS table operator
For more information about creating foreign tables and accessing external data, see Native Object Store: Teradata Vantage™ Advanced SQL Engine, TDN0009800, Teradata Vantage™ - SQL Data Definition Language Syntax and Examples, B035-1144, Teradata Vantage™ - SQL Data Manipulation Language, B035-1146 and Teradata Vantage™ - Native Object Store Getting Started Guide, B035-1214.