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.

126 DBLIBINIT= LIBNAME Option 4 Chapter 10DBMS support: Aster nCluster, DB2 under UNIX and PC Hosts, Greenplum, HPNeoview, In<strong>for</strong>mix, Microsoft SQL Server, MySQL, Netezza, ODBC, OLE DB, Oracle,Sybase, Sybase IQ, TeradataSyntaxDBINDEX=YES | NOSyntax DescriptionYESspecifies that <strong>SAS</strong> uses columns in the WHERE clause that have defined DBMSindexes.NOspecifies that <strong>SAS</strong> does not use indexes that are defined on DBMS columns.DetailsWhen you are processing a join that involves a large DBMS table and a relatively small<strong>SAS</strong> data set, you might be able to use DBINDEX= to improve per<strong>for</strong>mance.CAUTION:Improper use of this option can degrade per<strong>for</strong>mance. 4See AlsoTo apply this option to an individual data set, see the “DBINDEX= Data Set Option”on page 303.For detailed in<strong>for</strong>mation about using this option, see “Using the DBINDEX=,DBKEY=, and MULTI_DATASRC_OPT= Options” on page 48.DBLIBINIT= LIBNAME OptionSpecifies a user-defined initialization command to execute once within the scope of the LIBNAMEstatement or libref that established the first connection to the DBMS.Default value: noneValid in: <strong>SAS</strong>/<strong>ACCESS</strong> LIBNAME statementDBMS support: Aster nCluster, DB2 under UNIX and PC Hosts, DB2 under z/OS,Greenplum, HP Neoview, In<strong>for</strong>mix, Microsoft SQL Server, MySQL, Netezza, ODBC,OLE DB, Oracle, Sybase, Sybase IQ, TeradataSyntaxDBLIBINIT=DBMS-user-command

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

Saved successfully!

Ooh no, something went wrong!