13.07.2015 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Data Set Options <strong>for</strong> <strong>Relational</strong> <strong>Databases</strong> 4 DBINDEX= Data Set Option 303ExamplesIf you specify DBGEN_NAME=<strong>SAS</strong>, <strong>SAS</strong> renames a DBMS column named Dept$Amtto _COLn. If you specify DBGEN_NAME=DBMS, <strong>SAS</strong> renames the Dept$Amt column toDept_Amt.See AlsoTo assign this option to a group of relational DBMS tables or views, see the“DBGEN_NAME= LIBNAME Option” on page 124.“VALIDVARNAME= System Option” on page 423DBINDEX= Data Set OptionDetects and verifies that indexes exist on a DBMS table.Default value: DBMS-specificValid in: DATA and PROC steps (when accessing DBMS data using <strong>SAS</strong>/<strong>ACCESS</strong>software)DBMS support: Aster nCluster, DB2 under UNIX and PC Hosts, Greenplum, HP Neoview,In<strong>for</strong>mix, Microsoft SQL Server, MySQL, Netezza, ODBC, OLE DB, Oracle, Sybase,Sybase IQ, TeradataSyntaxDBINDEX=YES | NO | index-nameSyntax DescriptionYEStriggers the <strong>SAS</strong>/<strong>ACCESS</strong> engine to search <strong>for</strong> all indexes on a table and return themto <strong>SAS</strong> <strong>for</strong> evaluation. If <strong>SAS</strong>/<strong>ACCESS</strong> finds a usable index, it passes the joinWHERE clause to the DBMS <strong>for</strong> processing. A usable index should have at least thesame attributes as the join column.NOno automated index search is per<strong>for</strong>med.index-nameverifies the index name that is specified <strong>for</strong> the index columns on the DBMS table. Itrequires the same type of call as when DBINDEX=YES is used.DetailsIf indexes exist on a DBMS table and are of the correct type, you can use this option topotentially improve per<strong>for</strong>mance when you are processing a join query that involves alarge DBMS table and a relatively small <strong>SAS</strong> data set that is passed to the DBMS.CAUTION:Improper use of this option can impair per<strong>for</strong>mance. See “Using the DBINDEX=,DBKEY=, and MULTI_DATASRC_OPT= Options” on page 48 <strong>for</strong> detailedin<strong>for</strong>mation about using this option. 4

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!