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

168 PRESERVE_TAB_NAMES= LIBNAME Option 4 Chapter 103 Specify the global system option VALIDVARNAME=ANY and use name literals inthe SAS language. For example:proc print data=mydblib.mytable;format ’Total$Cost’n 22.2;If you are creating a table in PROC SQL, you must also include thePRESERVE_COL_NAMES=YES option in your LIBNAME statement. Here is anexample:libname mydblib oracle user=testuser password=testpasspreserve_col_names=yes;proc sql dquote=ansi;create table mydblib.mytable ("my$column" int);PRESERVE_COL_NAMES= does not apply to the SQL pass-through facility.See AlsoTo apply this option to an individual data set, see the naming in your DBMSinterface for the “PRESERVE_COL_NAMES= Data Set Option” on page 358.Chapter 2, “SAS Names and Support for DBMS Names,” on page 11“VALIDVARNAME= System Option” on page 423PRESERVE_TAB_NAMES= LIBNAME OptionPreserves spaces, special characters, and case sensitivity in DBMS table names.Alias: PRESERVE_NAMES= (see “Details”)Default value: DBMS-specificValid in: SAS/ACCESS LIBNAME statementDBMS 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 IQ, TeradataSyntaxPRESERVE_TAB_NAMES=YES | NOSyntax DescriptionNOspecifies that when you create DBMS tables or refer to an existing table, the tablenames are derived from SAS member names by using SAS member namenormalization. However, the database applies DBMS-specific normalization rules tothe SAS member names. Therefore, the table names are created or referenced in thedatabase following the DBMS-specific normalization rules.When you use SAS to read a list of table names (for example, in the SAS Explorerwindow), the tables whose names do not conform to the SAS member name