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.

574 Introduction to <strong>SAS</strong>/<strong>ACCESS</strong> Interface to In<strong>for</strong>mix 4 Chapter 19Introduction to <strong>SAS</strong>/<strong>ACCESS</strong> Interface to In<strong>for</strong>mixOverviewThis section describes <strong>SAS</strong>/<strong>ACCESS</strong> Interface to In<strong>for</strong>mix. See “<strong>SAS</strong>/<strong>ACCESS</strong>Interface to In<strong>for</strong>mix: Supported Features” on page 78 <strong>for</strong> a list of <strong>SAS</strong>/<strong>ACCESS</strong>features that are available in this interface. For background in<strong>for</strong>mation aboutIn<strong>for</strong>mix, see “Overview of In<strong>for</strong>mix Servers” on page 588.Default EnvironmentWhen you access In<strong>for</strong>mix tables by using <strong>SAS</strong>/<strong>ACCESS</strong> Interface to In<strong>for</strong>mix, thedefault In<strong>for</strong>mix read isolation level is set <strong>for</strong> committed reads, and <strong>SAS</strong> spooling is on.Committed reads enable you to read rows unless another user or process is updatingthe rows. Reading in this manner does not lock the rows. <strong>SAS</strong> spooling guarantees thatyou get identical data each time you re-read a row because <strong>SAS</strong> buffers the rows afteryou read them the first time. This default environment is suitable <strong>for</strong> most users. Ifthis default environment is unsuitable <strong>for</strong> your needs, see “Locking in the In<strong>for</strong>mixInterface” on page 584.To see the SQL statements that <strong>SAS</strong> issues to the In<strong>for</strong>mix server, include the<strong>SAS</strong>TRACE= option in your code:option sastrace=’,,,d’;If you use quotation marks in your In<strong>for</strong>mix SQL statements, set yourDELIMIDENT= environment variable to DELIMIDENT=YES or In<strong>for</strong>mix might rejectyour statements. Because some <strong>SAS</strong> options that preserve case generate SQLstatements that contain quotation marks, you should set DELIMIDENT=YES in yourenvironment.LIBNAME Statement Specifics <strong>for</strong> In<strong>for</strong>mixOverviewThis section describes the LIBNAME statement that <strong>SAS</strong>/<strong>ACCESS</strong> Interface toIn<strong>for</strong>mix supports and includes an example. For details about this feature, see“Overview of the LIBNAME Statement <strong>for</strong> <strong>Relational</strong> <strong>Databases</strong>” on page 87.Here is the LIBNAME statement syntax <strong>for</strong> accessing In<strong>for</strong>mix.LIBNAME libref in<strong>for</strong>mix ;Argumentslibrefspecifies any <strong>SAS</strong> name that serves as an alias to associate <strong>SAS</strong> with a database,schema, server, or group of tables and views.

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

Saved successfully!

Ooh no, something went wrong!