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

The LIBNAME Statement for Relational Databases 4 STRINGDATES= LIBNAME Option 191NONEprevents those SAS procedures that are enabled for in-database processing fromgenerating SQL for in-database processing. This is a primary state.DBMSallows SAS procedures that are enabled for in-database processing to generate SQLfor in-database processing of DBMS tables through supported SAS/ACCESS engines.This is a primary state.DBMS=’engine1 engine2 ... enginen’specifies one or more SAS/ACCESS engines. It modifies the primary state.Restriction:The maximum length of an engine name is 8 characters.EXCLUDEDB=engine |’engine1 engine2 ... enginen’prevents SAS procedures from generating SQL for in-database processing for one ormore specified SAS/ACCESS engines.Restriction: The maximum length of an engine name is 8 characters.EXCLUDEPROC="engine=’proc1 proc2 ... procn’ enginen=’proc1 proc2 ... procn’ "identifies engine-specific SAS procedures that do not support in-database processing.Restrictions: The maximum length of a procedure name is 16 characters.An engine can appear only once, and a procedure can appear only once for agiven engine.""resets the value to the default that was shipped.DetailsUse this option with such procedures as PROC FREQ to indicate what SQL isgenerated for in-database processing based on the type of subsetting that you need andthe SAS/ACCESS engines that you want to access the source table.You must specify NONE and DBMS, which indicate the primary state.The maximum length of the option value is 4096. Also, parentheses are requiredwhen this option value contains multiple keywords.Not all procedures support SQL generation for in-database processing for everyengine type. If you specify a setting that is not supported, an error message indicatesthe level of SQL generation that is not supported, and the procedure can reset to thedefault so that source table records can be read and processed within SAS. If this is notpossible, the procedure ends and sets SYSERR= as needed.You can specify different SQLGENERATION= values for the DATA= and OUT= datasets by using different LIBNAME statements for each of these two data sets.See Also“SQLGENERATION= System Option” on page 420Chapter 8, “Overview of In-Database Procedures,” on page 67Table 12.2 on page 421STRINGDATES= LIBNAME OptionSpecifies whether to read date and time values from the database as character strings or asnumeric date values.