The LIBNAME Statement for Relational Databases |
Default value: | NO |
Valid in: | SAS/ACCESS LIBNAME statement |
DBMS support: | Teradata |
Syntax | |
Syntax Description | |
Details | |
Example | |
See Also |
Syntax |
FASTEXPORT=YES | NO |
specifies that the SAS/ACCESS engine uses the Teradata Parallel Transporter (TPT) API to read data from a Teradata table.
specifies that the SAS/ACCESS engine does not use the TPT API to read data from a Teradata table.
Details |
By using the TPT API, you can read data from a Teradata table without working directly with the stand-alone Teradata FastExport utility. When FASTEXPORT=YES, SAS uses the TPT API export driver for bulk reads. If SAS cannot use the TPT API due to an error or because it is not installed on the system, it still tries to read the data but does not produce an error. To check 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 set 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 setting OPTIONS SASTRACE=",,,d" in your program.
Example |
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=testuser pw=testpw FASTEXPORT=YES; /* Create data */ Data tera.testdata; Do i=1 to 100; Output; End; Run; /* Read using FastExport TPT. This note appears in the SAS log if SAS uses TPT. NOTE: Teradata connection: TPT FastExport has read n row(s).*/ Data work.testdata; Set tera.testdata; Run;
See Also |
Maximizing Teradata Load Performance
Copyright © 2010 by SAS Institute Inc., Cary, NC, USA. All rights reserved.