When you use conventional
processing to access data that is inside a DBMS, SAS asks the
SAS/ACCESS
engine for all table rows of the table that is being processed. The
SAS/ACCESS engine generates an SQL SELECT * statement, which is passed
to the DBMS. That SELECT statement fetches all rows in the table,
and the
SAS/ACCESS engine returns them to SAS. The number of rows
in the table grows over time, so network latency grows because the
amount of data that is fetched from the DBMS to SAS increases.
SAS In-Database processing
integrates SAS solutions, SAS analytic processes, and third-party
DBMSs. Using SAS In-Database processing, you can run scoring models,
Base SAS and
SAS/STAT procedures, and formatted SQL queries inside
the database.
SAS Products Needed to Use In-Database Features
|
|
|
|
format publishing and
the SAS_PUT() function
|
-
-
SAS/ACCESS DBMS interfaces
|
| DB2 for UNIX and PC Hosts |
| Netezza |
| Teradata |
|
|
|
-
-
SAS/ACCESS DBMS interfaces
-
-
SAS Model Manager (optional)
|
| Aster nCluster
|
| DB2 for UNIX and PC Hosts |
| Greenplum |
| Netezza |
| Teradata |
|
Base SAS procedures:
| FREQ |
| RANK |
| REPORT |
| SORT |
| SUMMARY/MEANS |
| TABULATE |
|
-
-
SAS/ACCESS DBMS interfaces
|
| Aster nCluster
|
| DB2 under UNIX and PC Hosts |
| Greenplum |
| Netezza |
| Oracle |
| Teradata |
|
SAS/STAT procedures:
| CORR |
| CANCORR |
| DMDB |
| DMINE |
| DMREG |
| FACTOR |
| PRINCOMP |
| REG |
| SCORE |
| TIMESERIES |
| VARCLUS |
|
-
-
SAS/ACCESS Interface to Teradata
-
SAS/STAT (for CANCORR, FACTOR,PRINCOMP,
REG, SCORE, VARCLUS)
-
-
SAS Enterprise Miner (for DMDB,
DMINE, DMREG)
-
SAS Analytics Accelerator
|
|
For more information,
see
SAS In-Database Products: Administrator’s Guide and
SAS
In-Database Products: User’s Guide.