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

SAS/ACCESS Interface to ODBC 4 LIBNAME Statement Data Conversions 679For more information about how SAS handles NULL values, see “Potential ResultSet Differences When Processing Null Data” in SAS/ACCESS for Relational Databases:Reference.To control how SAS missing character values are handled by the DBMS, use theNULLCHAR= and NULLCHARVAL= data set options.LIBNAME Statement Data ConversionsThis table shows all data types and default SAS formats that SAS/ACCESS Interfaceto ODBC supports. It does not explicitly define the data types as they exist for eachDBMS. It lists the SQL types that each DBMS data type would map to. For example, aCHAR data type under DB2 would map to an ODBC data type of SQL_CHAR. All datatypes are supported.Table 23.4ODBC Data Types and Default SAS FormatsODBC Data TypeDefault SAS FormatSQL_CHAR $nSQL_VARCHAR $nSQL_LONGVARCHAR $nSQL_BINARYSQL_VARBINARYSQL_LONGVARBINARYSQL_DECIMALSQL_NUMERIC$n.*$n.*$n.*m or m.n or none if m and n are not specifiedm or m.n or none if m and n are not specifiedSQL_INTEGER 11.SQL_SMALLINT 6.SQL_TINYINT 4.SQL_BIT 1.SQL_REALSQL_FLOATSQL_DOUBLEnonenonenoneSQL_BIGINT 20.SQL_INTERVAL $nSQL_GUID $nSQL_TYPE_DATESQL_TYPE_TIMESQL_TYPE_TIMESTAMPDATE9.TIME8.ODBC cannot support fractions of seconds fortime valuesDATETIMEm.n where m and n depend onprecision* Because the ODBC driver does the conversion, this field displays as if the $HEXn. format wereapplied.