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

The LIBNAME Statement for Relational Databases 4 DBMSTEMP= LIBNAME Option 131DBMSTEMP= LIBNAME OptionSpecifies whether SAS creates temporary or permanent tables.Default value:Valid in:NOSAS/ACCESS LIBNAME statementDBMS support: Aster nCluster, DB2 under UNIX and PC Hosts, DB2 under z/OS,Greenplum, HP Neoview, Microsoft SQL Server, MySQL, Netezza, ODBC, OLE DB,Oracle, Sybase IQ, TeradataSyntaxDBMSTEMP=YES | NOSyntax DescriptionYESspecifies that SAS creates one or more temporary tables.NOspecifies that SAS creates permanent tables.DetailsTo specify this option, you must first specify CONNECTION=GLOBAL, except forMicrosoft SQL Server, which defaults to UNIQUE. To significantly improveperformance, you must also set DBCOMMIT=0. The value for SCHEMA= is ignored.You can then access and use the DBMS temporary tables using SAS/ACCESS enginelibrefs that share the global connection that SAS used to create those tables.To join a temporary and a permanent table, you need a libref for each table and theselibrefs must successfully share a global connection.DB2 under z/OS, Oracle, and Teradata: Set INSERTBUFF=1000 or higher tosignificantly improve performance.ODBC: This engine supports DB2, MS SQL Server, or Oracle if you are connected tothem.ExamplesThis example shows how to use this option to create a permanent and temporarytable and then join them in a query. The temporary table might not exist beyond asingle PROC step. However, this might not be true for all DBMSs.options sastrace=(,,d,d) nostsuffix sastraceloc=saslog;LIBNAME permdata DB2 DB=MA40 SCHEMA=SASTDATA connection=global dbcommit=0USER=sasuser PASSWORD=xxx;LIBNAME tempdata DB2 DB=MA40 SCHEMA=SASTDATA connection=global dbcommit=0dbmstemp=yes USER=sasuser PASSWORD=xxx;proc sql;create table tempdata.ptyacc as