| Product | Release |
|---|---|
| SAS/ACCESS Interface to Sybase | 9.21 |
| SAS/ACCESS Interface to Oracle | 9.21 |
| SAS/ACCESS Interface to DB2 | 9.21 |
| SAS/ACCESS Interface to Greenplum | 9.21 |
| SAS/ACCESS Interface to Netezza | 9.21 |
| SAS/ACCESS Interface to ODBC | 9.21 |
| SAS/ACCESS Interface to Teradata | 9.21 |
| SAS/ACCESS Interface to Sybase IQ | 9.21 |
| SAS/ACCESS Interface to MySQL | 9.21 |
| SAS/ACCESS Interface to Microsoft SQL Server | 9.21 |
| SAS/ACCESS Interface to HP Neoview | 9.21 |
| SAS/ACCESS Interface to Informix | 9.21 |
| SAS/ACCESS Interface to OLE DB | 9.21 |
| Previous Page | | | Next Page |
| Performance Considerations |
![[cautionend]](../../../../common/62850/HTML/default/images/cautend.gif)
It is sometimes more efficient to extract (copy) DBMS data to a SAS data file than to repeatedly read the data by using a SAS view. SAS data files are organized to provide optimal performance with PROC and DATA steps. Programs that use SAS data files are often more efficient than SAS programs that read DBMS data directly.
Consider extracting data when you work with a large DBMS table and plan to use the same DBMS data in several procedures or DATA steps during the same SAS session.
You can extract DBMS data to a SAS data file by using the OUT= option, a DATA step, or ACCESS procedures.
| Previous Page | | | Next Page | | | Top of Page |
Copyright © 2009 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
