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.

The LIBNAME Statement <strong>for</strong> <strong>Relational</strong> <strong>Databases</strong> 4 ENABLE_BULK= LIBNAME Option 145where tab1.deptno=tab2.deptnousing libname mydblib oracle user=testuserpassword=testpass path=myserver direct_sql=nogensql;The following example prevents a <strong>SAS</strong> function from being processed by the DBMS.libname mydblib oracle user=testuser password=testpass direct_sql=nofunctions;proc print data=mydblib.tab1;where lastname=soundex (’Paul’);See Also“SQL_FUNCTIONS= LIBNAME Option” on page 186ENABLE_BULK= LIBNAME OptionAllows the connection to process bulk copy when loading data into a Sybase table.Default value: YESValid in: <strong>SAS</strong>/<strong>ACCESS</strong> LIBNAME statementDBMS support: SybaseSyntaxENABLE_BULK=YES | NOSyntax DescriptionNOdisables the bulk copy ability <strong>for</strong> the libref.YESenables the connection to per<strong>for</strong>m a bulk copy of <strong>SAS</strong> data into Sybase.DetailsBulk copy groups rows so that they are inserted as a unit into the Sybase table. Usingbulk copy can improve per<strong>for</strong>mance.If you use both the, ENABLE_BULK= LIBNAME option and the BULKLOAD=dataset option, the values of the two options must be the same or an error is returned.However, since the default value of ENABLE_BULK= is YES, you do not have tospecify ENABLE_BULK= in order to use the BULKLOAD= data set option.Note: In <strong>SAS</strong> 7 and previous releases, this option was called BULKCOPY=. In <strong>SAS</strong>8 and later, an error is returned if you specify BULKCOPY=. 4See Also“BULKLOAD= Data Set Option” on page 290

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

Saved successfully!

Ooh no, something went wrong!