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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>SAS</strong>/<strong>ACCESS</strong> Interface to Aster nCluster 4 Passing Joins to Aster nCluster 4493 LOG10 (log)3 LOWCASE (lower)3 MAX3 MIN3 MINUTE (date_part)3 MOD3 MONTH (date_part)3 QTR (date_part)3 REPEAT3 SIGN3 SIN3 SQRT3 STRIP (btrim)3 SUBSTR (substring3 SUM3 TAN3 TRANWRD (replace)3 TRIMN (rtrim)3 UPCASE (upper)3 YEAR (date_part)SQL_FUNCTIONS= ALL allows <strong>for</strong> <strong>SAS</strong> functions that have slightly differentbehavior from corresponding database functions that are passed down to the database.Only when SQL_FUNCTIONS=ALL can the <strong>SAS</strong>/<strong>ACCESS</strong> engine also pass these <strong>SAS</strong>SQL functions to Aster nCluster. Due to incompatibility in date and time functionsbetween Aster nCluster and <strong>SAS</strong>, Aster nCluster might not process them correctly.Check your results to determine whether these functions are working as expected. Formore in<strong>for</strong>mation, see “SQL_FUNCTIONS= LIBNAME Option” on page 186.3 COMPRESS (replace)3 DATE (now::date)3 DATEPART (cast)3 DATETIME (now)3 LENGTH3 ROUND3 TIME (now::time)3 TIMEPART (cast)3 TODAY (now::date)3 TRANSLATEPassing Joins to Aster nClusterFor a multiple libref join to pass to Aster nCluster, all of these components of theLIBNAME statements must match exactly.3 user ID (USER=)3 password (PASSWORD=)3 server (SERVER=)3 database (DATABASE=)

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

Saved successfully!

Ooh no, something went wrong!