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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Macro Variables and System Options <strong>for</strong> <strong>Relational</strong> <strong>Databases</strong> 4 DBIDIRECTEXEC= System Option 405DBIDIRECTEXEC= System OptionLets the SQL pass-through facility optimize handling of SQL Statements by passing them directlyto the databases <strong>for</strong> execution.Default value: NODBIDIRECTEXECValid in: configuration file, <strong>SAS</strong> invocation, OPTIONS statement, <strong>SAS</strong> System OptionswindowDBMS support: Aster n Cluster, 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, TeradataSyntaxDBIDIRECTEXEC | NODBIDIRECTEXECSyntax DescriptionDBIDIRECTEXECindicates that the SQL pass-through facility optimizes handling of SQL statementsby passing them directly to the database <strong>for</strong> execution, which optimizes per<strong>for</strong>mance.Using this option, you can process CREATE TABLE AS SELECT and DELETEstatements.NODBIDIRECTEXECindicates that the SQL pass-through facility does not optimize handling of SQLstatements.DetailsYou can significantly improve CPU and input/output per<strong>for</strong>mance by using this option,which applies to all hosts and all <strong>SAS</strong>/<strong>ACCESS</strong> engines.Certain database-specific criteria exist <strong>for</strong> passing SQL statements to the DBMS.These criteria are the same as the criteria that exist <strong>for</strong> passing joins. For details <strong>for</strong>your DBMS, see “Passing Joins to the DBMS” on page 43 and “When Passing Joins tothe DBMS Will Fail” on page 45.When these criteria are met, a database can process the CREATE TABLE table-nameAS SELECT statement in a single step instead of as three separate statements(CREATE, SELECT, and INSERT). For example, if multiple librefs point to differentdata sources, the statement is processed normally, regardless of how you set this option.However, when you enable it, PROC SQL sends the CREATE TABLE AS SELECTstatement to the database.You can also send a DELETE statement directly to the database <strong>for</strong> execution, whichcan improve CPU, input, and output per<strong>for</strong>mance.Once a system administrator sets the default <strong>for</strong> this option globally, users canoverride it within their own configuration file.When you specify DBIDIRECTEXEC=, PROC SQL can pass this statement directlyto the database:CREATE TABLE table-name AS SELECT query

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

Saved successfully!

Ooh no, something went wrong!