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.

591CHAPTER20<strong>SAS</strong>/<strong>ACCESS</strong> Interface toMicrosoft SQL ServerIntroduction to <strong>SAS</strong>/<strong>ACCESS</strong> Interface to Microsoft SQL Server 591LIBNAME Statement Specifics <strong>for</strong> Microsoft SQL Server 592Overview 592Arguments 592Microsoft SQL Server LIBNAME Statement Examples 595Data Set Options <strong>for</strong> Microsoft SQL Server 595SQL Pass-Through Facility Specifics <strong>for</strong> Microsoft SQL Server 597Key In<strong>for</strong>mation 597CONNECT Statement Examples 597Connection To Component Examples 598DBLOAD Procedure Specifics <strong>for</strong> Microsoft SQL Server 598Overview 598Examples 599Passing <strong>SAS</strong> Functions to Microsoft SQL Server 600Locking in the Microsoft SQL Server Interface 600Naming Conventions <strong>for</strong> Microsoft SQL Server 601Data Types <strong>for</strong> Microsoft SQL Server 602Overview 602Microsoft SQL Server Null Values 602LIBNAME Statement Data Conversions 602Introduction to <strong>SAS</strong>/<strong>ACCESS</strong> Interface to Microsoft SQL ServerThis section describes <strong>SAS</strong>/<strong>ACCESS</strong> Interface to Microsoft SQL Server. For a list of<strong>SAS</strong>/<strong>ACCESS</strong> features that are available <strong>for</strong> this interface, see “<strong>SAS</strong>/<strong>ACCESS</strong> Interfaceto Microsoft SQL Server: Supported Features” on page 79.<strong>SAS</strong>/<strong>ACCESS</strong> Interface to Microsoft SQL Server has been tested and certified againstData Direct Technologies Connect ODBC and Data Direct SequeLink ODBC products.

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

Saved successfully!

Ooh no, something went wrong!