| Product | Release |
|---|---|
| SAS/ACCESS Interface to HP Neoview | 9.2 |
| SAS/ACCESS Interface to Informix | 9.2 |
| SAS/ACCESS Interface to DB2 | 9.2 |
| SAS/ACCESS Interface to Sybase | 9.2 |
| SAS/ACCESS Interface to MySQL | 9.2 |
| SAS/ACCESS Interface to Oracle | 9.2 |
| SAS/ACCESS Interface to Microsoft SQL Server | 9.2 |
| SAS/ACCESS Interface to Teradata | 9.2 |
| SAS/ACCESS Interface to Netezza | 9.2 |
| SAS/ACCESS Interface to ODBC | 9.2 |
| SAS/ACCESS Interface to OLE DB | 9.2 |
| SAS/ACCESS Product of Choice |
| Previous Page | | | Next Page |
| Optimizing Your SQL Usage |
When you use the SAS/ACCESS LIBNAME statement with the DIRECT_EXE option set to DELETE, the SAS SQL DELETE statement gets passed to the DBMS for execution as long as it contains no WHERE clause. The DBMS deletes all the rows, but does not delete the table itself.
The following example illustrates how a DELETE statement gets passed to Oracle for the table EMP to be emptied:
libname myoralib oracle user=testuser password=testpass direct_exe=delete; proc sql; delete from myoralib.emp; quit;
This code causes Oracle to execute the following:
delete from emp
| Previous Page | | | Next Page | | | Top of Page |
Copyright © 2007 by SAS Institute Inc., Cary, NC, USA. All rights reserved.
