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 Accessing Teradata Objects That Do Not Meet <strong>SAS</strong> Naming Conventions 8373 Per<strong>for</strong>ms the insert operation without hanging (suspending) your <strong>SAS</strong> session.Naming Conventions <strong>for</strong> TeradataTeradata ConventionsFor general in<strong>for</strong>mation about this feature, see Chapter 2, “<strong>SAS</strong> Names and Support<strong>for</strong> DBMS Names,” on page 11.You can use these conventions to name such Teradata objects as include tables,views, columns, indexes, and macros.3 A name must be from 1 to 30 characters long.3 A name must begin with a letter unless you enclose it in double quotation marks.3 A name can contain letters (A to Z), numbers from 0 to 9, underscore (_), dollarsign ($), and the number or pound sign (#). A name in double quotation marks cancontain any characters except double quotation marks.3 A name, even when enclosed in double quotation marks, is not case sensitive. Forexample, CUSTOMER and Customer are the same.3 A name cannot be a Teradata reserved word.3 The name must be unique between objects, so a view and table in the samedatabase cannot have an identical name.<strong>SAS</strong> Naming ConventionsUse these conventions when naming a <strong>SAS</strong> object:3 A name must be from 1 to 32 characters long.3 A name must begin with a letter (A to Z) or an underscore (_).3 A name can contain letters (A to Z), numbers from 0 to 9, and an underscore (_).3 Names are not case sensitive. For example, CUSTOMER and Customer are the same.3 A name cannot be enclosed in double quotation marks.3 A name need not be unique between object types.Naming Objects to Meet Teradata and <strong>SAS</strong> ConventionsTo easily share objects between <strong>SAS</strong> and the DBMS, create names that meet both<strong>SAS</strong> and Teradata naming conventions:3 Start with a letter.3 Include only letters, digits, and underscores.3 Use a length of 1 to 30 characters.Accessing Teradata Objects That Do Not Meet <strong>SAS</strong> NamingConventionsThe following <strong>SAS</strong>/<strong>ACCESS</strong> code examples can help you access Teradata objects(existing Teradata DBMS tables and columns) that have names that do not follow <strong>SAS</strong>naming conventions.

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

Saved successfully!

Ooh no, something went wrong!