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 QUOTE_CHAR= LIBNAME Option 173SyntaxQUERY_TIMEOUT=number-of-secondsDetailsThe default value of 0 indicates that there is no time limit <strong>for</strong> a query. This option isuseful when you are testing a query or if you suspect that a query might contain anendless loop.See AlsoTo apply this option to an individual data set, see the “QUERY_TIMEOUT= Data SetOption” on page 361.QUOTE_CHAR= LIBNAME OptionSpecifies which quotation mark character to use when delimiting identifiers.Default value: noneValid in: <strong>SAS</strong>/<strong>ACCESS</strong> LIBNAME statementDBMS support: Aster nCluster, Greenplum, HP Neoview, Microsoft SQL Server, Netezza,ODBC, OLE DB, Sybase IQSyntaxQUOTE_CHAR=characterSyntax Descriptioncharacteris the quotation mark character to use when delimiting identifiers, such as thedouble quotation mark (").DetailsThe provider usually specifies the delimiting character. However, when there is adifference between what the provider allows <strong>for</strong> this character and what the DBMSallows, the QUOTE_CHAR= option overrides the character returned by the provider.Microsoft SQL Server: QUOTE_CHAR= overrides the Microsoft SQL Server default.ODBC: This option is mainly <strong>for</strong> the ODBC interface to Sybase, and you should use itwith the DBCONINIT and DBLIBINIT LIBNAME options. QUOTE_CHAR= overridesthe ODBC default because some drivers return a blank <strong>for</strong> the identifier delimiter eventhough the DBMS uses a quotation mark—<strong>for</strong> example, ODBC to Sybase.

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

Saved successfully!

Ooh no, something went wrong!