SAS ® PASSTHRU to Microsoft SQL Server using ODBC
Nina L. Werner
Abstract
Nina L. Werner
Abstract
I wish I could live in SAS World; I do much of my data analysis there. However, my current environment houses all production data in Microsoft SQL Server 2008 R2 data warehouses. Microsoft SQL Server is a relational database with its own dialect of SQL (T-SQL or Transact-SQL.) SAS/ACCESS ® Interface to ODBC has several methods of retrieving SQL Server data for analyzing in SAS. Here’s an introduction to both implicit and explicit PASSTHRU (or, Pass-Through) with some hints for deciding which to apply. Explicit PASSTHRU will execute T-SQL code syntax inside SQL Server, while implicit PASSTHRU will use your SAS DATA step or PROC SQL code. Several useful options will be explained. No prior experience with ODBC is necessary.
A significance statement is not available in the OpenAlex record.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
I wish I could live in SAS World; I do much of my data analysis there. However, my current environment houses all production data in Microsoft SQL Server 2008 R2 data warehouses. Microsoft SQL Server is a relational database with its own dialect of SQL (T-SQL or Transact-SQL.) SAS/ACCESS ® Interface to ODBC has several methods of retrieving SQL Server data for analyzing in SAS. Here’s an introduction to both implicit and explicit PASSTHRU (or, Pass-Through) with some hints for deciding which to apply. Explicit PASSTHRU will execute T-SQL code syntax inside SQL Server, while implicit PASSTHRU will use your SAS DATA step or PROC SQL code. Several useful options will be explained. No prior experience with ODBC is necessary.
Key concepts: Open Database Connectivity, SQL/PSM, Data Transformation Services, Computer science, Stored procedure, Business Intelligence Markup Language, SQL injection, Language Integrated Query