Specifies whether the SAS/ACCESS engine uses the TPT API to read data.
Table of Contents
specifies that data is loaded from Teradata into SAS using the TPT Export driver.
specifies that the TPT Export driver is not to be used.
By using the TPT API, you can read data from a Teradata table without working directly with the standalone Teradata FastExport utility. When FASTEXPORT=YES, SAS uses the TPT API export driver for bulk reads. If SAS cannot use the TPT API—because of an error or because it is not installed on the system—SAS still tries to read the data. However, no error is produced. To see whether SAS used the TPT API to read data, look for this message in the SAS log:
NOTE: Teradata connection: TPT FastExport has read n row(s).
When you specify a query band on this option, you must specify the DBSLICEPARM= LIBNAME option. The query band is passed as a SESSION query band to the FastExport utility.
To see whether threaded Reads are actually generated,
turn on SAS tracing by specifying OPTIONS SASTRACE=",,,d"; in
your program.
Teradata on AIX: Beginning with the August 2024 update for SAS/ACCESS on SAS 9.4M8 and with the October 2024 update for SAS/ACCESS on SAS 9.4M7, setting FASTEXPORT=NO is ignored. SAS uses the Teradata Parallel Transporter API to load data to Teradata. For more information, see SAS Note 70928 - SAS/ACCESS Interface to Teradata support for Teradata Tools and Utilities (TTU) 17.xx and later in AIX environments.
In this example, the TPT API reads SAS data from a Teradata table. SAS still tries to read data even if it cannot use the TPT API.
Libname tera Teradata user=myusr1 pw=mypwd1 FASTEXPORT=YES;
/* Create data */
Data tera.testdata;
Do i=1 to 100;
Output;
End;
Run;
/* Read using TPT FastExport. */
Data work.testdata;
Set tera.testdata;
Run;
This note appears in the SAS log if SAS uses TPT.
NOTE: Teradata connection: TPT FastExport has read n row(s).