The LIBNAME Statement for Relational Databases |
Default value: | COMPAT |
Valid in: | SAS/ACCESS LIBNAME statement |
DBMS support: | Aster nCluster, DB2 under UNIX and PC Hosts, DB2 under z/OS, Greenplum, HP Neoview, Informix, Microsoft SQL Server, MySQL, Netezza, ODBC, OLE DB, Oracle, Sybase, Sybase IQ, Teradata |
Syntax | |
Syntax Description | |
Details | |
Examples |
Syntax |
DBSASLABEL=COMPAT | NONE |
specifies that the labels returned should be compatible with what the application normally receives--meaning that engines exhibit their normal behavior.
specifies that the engine does not return a column label. The engine returns blanks for the column labels.
Details |
By default, the SAS/ACCESS interface for your DBMS generates column labels from the column names, rather than from the real column labels.
You can use this option to override the default behavior. It is useful for when PROC SQL uses column labels as headers instead of column aliases.
Examples |
The following example demonstrates how DBSASLABEL= is used as a LIBNAME option to return blank column labels so that PROC SQL can use the column aliases as the column headings.
libname x oracle user=scott pw=tiger; proc sql; select deptno as Department ID, loc as Location from mylib.dept(dbsaslabel=none);
Without DBSASLABEL=NONE, aliases would be ignored, and DEPTNO and LOC would be used as column headings in the result set.
Copyright © 2010 by SAS Institute Inc., Cary, NC, USA. All rights reserved.