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.

306 DBLABEL= Data Set Option 4 Chapter 11run;To use more than one value <strong>for</strong> DBKEY=, you must include the second value as a joinon the WHERE clause. In the next example PROC SQL brings the entire DBMS tableinto <strong>SAS</strong> and then proceeds with processing:options sastrace=’,,,d’ sastraceloc=saslog nostsuffix;proc sql;create table work.barbkey asselect keyvalues.empid, employees.hiredate, employees.jobcodefrom mydblib.employees(dbkey=(empid jobcode))inner join work.keyvalues on employees.empid = keyvalues.empid;quit;See Also“DBINDEX= Data Set Option” on page 303DBLABEL= Data Set OptionSpecifies whether to use <strong>SAS</strong> variable labels or <strong>SAS</strong> variable names as the DBMS column namesduring output processing.Default value: NOValid in: DATA and PROC steps (when accessing DBMS data using <strong>SAS</strong>/<strong>ACCESS</strong>software)DBMS support: Aster nCluster, DB2 under UNIX and PC Hosts, DB2 under z/OS,Greenplum, HP Neoview, In<strong>for</strong>mix, Microsoft SQL Server, MySQL, Netezza, ODBC,OLE DB, Oracle, Sybase, Sybase IQ, TeradataSyntaxDBLABEL=YES | NOSyntax DescriptionYESspecifies that <strong>SAS</strong> variable labels are used as DBMS column names during outputprocessing.NOspecifies that <strong>SAS</strong> variable names are used as DBMS column names.DetailsThis option is valid only <strong>for</strong> creating DBMS tables.ExampleIn this example, a <strong>SAS</strong> data set, NEW, is created with one variable C1. This variableis assigned a label of DEPTNUM. In the second DATA step, the MYDBLIB.MYDEPT

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

Saved successfully!

Ooh no, something went wrong!