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

186 SQL_FUNCTIONS= LIBNAME Option 4 Chapter 10See Also“CONNECTION= LIBNAME Option” on page 108SQL_FUNCTIONS= LIBNAME OptionCustomizes the in-memory SQL dictionary function list for this particular LIBNAME statement.Default value:Valid in:noneSAS/ACCESS LIBNAME statementDBMS support: Aster nCluster, DB2 under UNIX and PC Hosts, DB2 under z/OS,Greenplum, HP Neoview, Informix, MySQL, Netezza, ODBC, OLE DB, Oracle, Sybase,Sybase IQ, TeradataSyntaxSQL_FUNCTIONS=ALL | "" |"EXTERNAL_APPEND="Syntax DescriptionALLcustomizes the in-memory SQL dictionary function list for this particular LIBNAMEstatement by adding the set of all existing functions, even those that might be riskyor untested.EXTERNAL_REPLACE= [not valid for Informix, OLE DB]indicates a user-specified, external SAS data set from which the complete functionlist in the SQL dictionary is to be built. The assumption is that the user has alreadyissued a LIBNAME statement to the directory where the SAS data set exists.EXTERNAL_APPEND= [not valid for Informix, OLE DB]indicates a user-specified, external SAS data set from which additional functions areto be added to the existing function list in the SQL dictionary. The assumption isthat the user has already issued a LIBNAME statement to the directory where theSAS data set exists.DetailsUse of this option can cause unexpected results, especially if used for NULL processingand date, time, and timestamp handling. For example, when executed withoutSQL_FUNCTIONS= enabled, this SAS code returns the SAS date 15308:proc sql;select distinct DATE () from x.test;quit;However, with SQL_FUNCTIONS=ALL, the same code returns 2001-1-29, which isan ODBC date format. So you should exercise care when you use this option.Functions that are passed are different for each DBMS. See the documentation foryour SAS/ACCESS interface for list of functions that it supports.