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.

The LIBNAME Statement <strong>for</strong> <strong>Relational</strong> <strong>Databases</strong> 4 FASTEXPORT= LIBNAME Option 147SyntaxESCAPE_BACKSLASH=YES | NOSyntax DescriptionYESspecifies that an additional backslash is inserted in every literal value that alreadycontains a backslash.NOspecifies that backslashes that exist in literal values are not preserved. An errorresults.DetailsMySQL uses the backslash as an escape character. When data that is copied from a<strong>SAS</strong> data set to a MySQL table contains backslashes in literal values, the MySQLinterface can preserve these if ESCAPE_BACKSLASH=YES.See AlsoTo apply this option to an individual data set, see the “ESCAPE_BACKSLASH= DataSet Option” on page 326.FASTEXPORT= LIBNAME OptionSpecifies whether the <strong>SAS</strong>/<strong>ACCESS</strong> engine uses the TPT API to read data.Default value: NOValid in: <strong>SAS</strong>/<strong>ACCESS</strong> LIBNAME statementDBMS support: TeradataSyntaxFASTEXPORT=YES | NOSyntax DescriptionYESspecifies that the <strong>SAS</strong>/<strong>ACCESS</strong> engine uses the Teradata Parallel Transporter (TPT)API to read data from a Teradata table.NOspecifies that the <strong>SAS</strong>/<strong>ACCESS</strong> engine does not use the TPT API to read data from aTeradata table.

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

Saved successfully!

Ooh no, something went wrong!