Usage Note 23194: When using SAS/ACCESS software, the PROC SQL queries that are included in my code do not always pass through to the DBMS engine. How can I make sure my queries are passed through?
To be a candidate for pass-through to a DBMS, a PROC SQL query must contain a reference to a single libref from a SAS/ACCESS libname engine, and the query must contain at least one of the following:
- JOINS (inner or outer).
- The DISTINCT keyword.
- SQL AGGREGATE functions.
- UNIONS.
When these conditions are met, the SQL textualizer parses the SAS query to determine whether the candidate query should be passed through to the DBMS. If the query contains any of the following SAS-specific elements, it is not passed through:
- Data set options.
- INTO clause.
Prior to Release 8.2 of SAS, if the query contained any SAS functions, it would not be passed through. However, beginning with Release 8.2 of SAS, the ACCESS libname engines do support a subset of SAS functions for which underlying DBMSs have equivalents. Queries that contain these supported functions are passed along with the query to the DBMS.
Note: SAS functions do not by themselves trigger a pass-through. Instead, a query must be a candidate for pass-through as described above. Once the query is a candidate, any SAS function for which the DBMS engine has an equivalent is simply passed along with the rest of the query.
You can find information about which SAS functions are supported by which ACCESS libname engines, in the SAS Online Help for SAS/ACCESS, Release 8.2.
Operating System and Release Information
SAS System | SAS/ACCESS Interface to Teradata | All | n/a | |
SAS System | SAS/ACCESS Interface to System 2000 | All | n/a | |
SAS System | SAS/ACCESS Interface to SAP BW | All | n/a | |
SAS System | SAS/ACCESS Interface to Sybase | All | n/a | |
SAS System | SAS/ACCESS Interface to R/3 | All | n/a | |
SAS System | SAS/ACCESS Interface to PeopleSoft | All | n/a | |
SAS System | SAS/ACCESS Interface to PC Files | All | n/a | |
SAS System | SAS/ACCESS Interface to Oracle Rdb | All | n/a | |
SAS System | SAS/ACCESS Interface to OLE DB | All | n/a | |
SAS System | SAS/ACCESS Interface to Oracle | All | n/a | |
SAS System | SAS/ACCESS Interface to ODBC | All | n/a | |
SAS System | SAS/ACCESS Interface to Microsoft SQL Server | All | n/a | |
SAS System | SAS/ACCESS Interface to Informix | All | n/a | |
SAS System | SAS/ACCESS Interface to IMS-DL/I | All | n/a | |
SAS System | SAS/ACCESS Interface to DB2 | All | n/a | |
SAS System | | All | n/a | |
SAS System | SAS/ACCESS Interface to CA-OpenIngres | All | n/a | |
SAS System | SAS/ACCESS Interface to CA-IDMS | All | n/a | |
SAS System | SAS/ACCESS Interface to CA-Datacom/DB | All | n/a | |
SAS System | SAS/ACCESS Interface to Baan | All | n/a | |
SAS System | SAS/ACCESS Interface to Adabas | All | n/a | |
SAS System | Base SAS | All | n/a | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Usage Note |
Priority: | low |
Date Modified: | 2003-02-25 20:11:44 |
Date Created: | 2003-02-25 14:31:38 |