13.07.2015 Views

SAS/ACCESS 9.2 for Relational Databases: Reference, Fourth Edition

SAS/ACCESS 9.2 for Relational Databases: Reference, Fourth Edition

SAS/ACCESS 9.2 for Relational Databases: Reference, Fourth Edition

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

784 LIBNAME Statement Specifics <strong>for</strong> Teradata 4 Chapter 283 It supports MultiLoad, which loads both empty and existing Teradata tables andgreatly accelerates the speed of insertion into Teradata tables.3 It supports the Teradata Parallel Transporter (TPT) API on Windows and UNIX.This API uses the Teradata load, update, and stream driver to load data and theexport driver to read data.LIBNAME Statement Specifics <strong>for</strong> TeradataOverviewThis section describes the LIBNAME statement that <strong>SAS</strong>/<strong>ACCESS</strong> Interface toTeradata supports and includes examples. For a complete description of this feature,see “Overview of the LIBNAME Statement <strong>for</strong> <strong>Relational</strong> <strong>Databases</strong>” on page 87.Here is the LIBNAME statement syntax <strong>for</strong> accessing Teradata.LIBNAME libref teradata ;Argumentslibrefspecifies any <strong>SAS</strong> name that serves as an alias to associate <strong>SAS</strong> with a database,schema, server, or group of tables and views.teradataspecifies the <strong>SAS</strong>/<strong>ACCESS</strong> engine name <strong>for</strong> the Teradata interface.connection-optionsprovide connection in<strong>for</strong>mation and control how <strong>SAS</strong> manages the timing andconcurrence of the connection to the DBMS. Here are the connection options <strong>for</strong>the Teradata interface.USER=Teradata-user-name | |specifies a required connection option that specifies a Teradata user name. Ifthe name contains blanks or national characters, enclose it in quotationmarks. For LDAP authentication with either a NULL or single realm,append only the @LDAP token to the Teradata user name. In this case, norealm name is needed. If you append a realm name, the LDAPauthentication server ignores it and authentication proceeds. However, ifmultiple realms exist, you must append the realm name to the @LDAP token.In this case, an LDAP server must already be configured to acceptauthentication requests from the Teradata server.PASSWORD=Teradata-passwordspecifies a required connection option that specifies a Teradata password. Thepassword that you specify must be correct <strong>for</strong> your USER= value. If you donot want to enter your Teradata password in clear text on this statement, seePROC PWENCODE in the Base <strong>SAS</strong> Procedures Guide <strong>for</strong> a method <strong>for</strong>encoding it. For LDAP authentication, you use this password option tospecify the authentication string or password. If the authentication string orpassword includes an embedded @ symbol, then a backslash (\) is requiredand it must precede the @ symbol. See “Teradata LIBNAME StatementExamples” on page 787.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!