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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>SAS</strong>/<strong>ACCESS</strong> Interface to Teradata 4 The <strong>SAS</strong>/<strong>ACCESS</strong> Teradata Client 783When to Use <strong>SAS</strong>/<strong>ACCESS</strong> Locking Options 834Examples 835Setting the Isolation Level to <strong>ACCESS</strong> <strong>for</strong> Teradata Tables 835Setting Isolation Level to WRITE to Update a Teradata Table 836Preventing a Hung <strong>SAS</strong> Session When Reading and Inserting to the Same Table 836Naming Conventions <strong>for</strong> Teradata 837Teradata Conventions 837<strong>SAS</strong> Naming Conventions 837Naming Objects to Meet Teradata and <strong>SAS</strong> Conventions 837Accessing Teradata Objects That Do Not Meet <strong>SAS</strong> Naming Conventions 837Example 1: Unusual Teradata Table Name 838Example 2: Unusual Teradata Column Names 838Data Types <strong>for</strong> Teradata 838Overview 838Binary String Data 838Character String Data 839Date, Time, and Timestamp Data 839Numeric Data 840Teradata Null Values 840LIBNAME Statement Data Conversions 841Data Returned as <strong>SAS</strong> Binary Data with Default Format $HEX 842Introduction to <strong>SAS</strong>/<strong>ACCESS</strong> Interface to TeradataOverviewThis section describes <strong>SAS</strong>/<strong>ACCESS</strong> Interface to Teradata. For a list of <strong>SAS</strong>/<strong>ACCESS</strong>features that are available <strong>for</strong> this interface, see “<strong>SAS</strong>/<strong>ACCESS</strong> Interface to Teradata:Supported Features” on page 85.Note: <strong>SAS</strong>/<strong>ACCESS</strong> Interface to Teradata does not support the DBLOAD and<strong>ACCESS</strong> procedures. The LIBNAME engine technology enhances and replaces thefunctionality of these procedures. There<strong>for</strong>e, you must revise <strong>SAS</strong> jobs that werewritten <strong>for</strong> a different <strong>SAS</strong>/<strong>ACCESS</strong> interface and that include DBLOAD or <strong>ACCESS</strong>procedures be<strong>for</strong>e you can run them with <strong>SAS</strong>/<strong>ACCESS</strong> Interface to Teradata. 4The <strong>SAS</strong>/<strong>ACCESS</strong> Teradata ClientTeradata is a massively parallel (MPP) RDBMS. A high-end Teradata server supportsmany users. It simultaneously loads and extracts table data and processes complexqueries.Because Teradata customers run many processors at the same time <strong>for</strong> queries of thedatabase, users enjoy excellent DBMS server per<strong>for</strong>mance. The challenge to clientsoftware, such as <strong>SAS</strong>, is to leverage Teradata per<strong>for</strong>mance by rapidly extracting andloading table data. <strong>SAS</strong>/<strong>ACCESS</strong> Interface to Teradata meets this challenge by lettingyou optimize extracts and loads (reads and creates).In<strong>for</strong>mation throughout this document explains how you can use the <strong>SAS</strong>/<strong>ACCESS</strong>interface to optimize DBMS operations:3 It can create and update Teradata tables. It supports a FastLoad interface thatrapidly creates new table. It can also potentially optimize table reads by usingFastExport <strong>for</strong> the highest possible read per<strong>for</strong>mance.

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

Saved successfully!

Ooh no, something went wrong!