This document discusses using SQL pass-through queries in SAS to more efficiently extract and transform data from relational database management systems (RDBMS) like Oracle, DB2, and SQL Server. It describes how pass-through queries process data directly in the RDBMS using native SQL functions rather than bringing entire tables into SAS, improving speed for complex queries. It also addresses differences between RDBMS like naming conventions and numeric precision that can cause issues if not handled properly in pass-through queries.

1. SQL Pass-Through and the ODBC Interface: Extract and Transform Your Data FASTER – For PC SAS Users

3. Definitions

5. ODBC Connection Setup

6. Syntax

7. ODBC Libname Statement (Implicit) libname CDB ODBC datasrc=db2p user=uid password=yourpwd schema=GWY1; proc sql ; create table WORK.ACCOUNT as select ACCT_NUM, OPEN_ENRLM_BEG_DT, OPEN_ENRLM_END_DT FROM CDB.ACCOUNT; quit;

9. Why Use Explicit Pass-Through?

10. Processing Location Affects Processing Speed "No one will believe you solved this problem in one day! We've been working on it for months. Now, go act busy for a few weeks and I'll let you know when it's time to tell them." --submission from a real-life “Dilbert Quotes” contest

11. Processing Location... Regular Query does processing work in SAS on your PC using SAS functions Pass-Through Query does processing work in RDBMS where the data is stored using “native” Oracle/DB2 functions Faster!!

13. Differences in Numeric Precision – Oracle example

15. Original Query proc sql; create table work.s1_claim_row as select put(claim_uid,best16.) as claim_uid length= 16 from prodj.s1_claim ; quit;

17. Solution (SAS/Access Interface to ODBC) proc sql; connect to odbc(datasrc = "PRODJ" user=xxxxxxxxxxx password=xxxxxxxxxxxx); create table work.s1_claim_row as select * from connection to odbc (select to_char(claim_uid,'0000000000000000') as claim_uid from onesource_o.s1_claim ) ; disconnect from odbc; quit;

18. Solution (SAS/Access Interface to Oracle) proc sql; connect to oracle(path = "prodj.cigna.com" user=xxxxxxx password=xxxxxxx); create table work.s1_claim_row as select * from connection to oracle (select to_char(claim_uid,'0000000000000000') as claim_uid from onesource_o.s1_claim ) ; disconnect from oracle; quit;

19. Differences in Naming Conventions – DB2 example

20. Original Query libname CDB ODBC datasrc=db2p user=uid password=yourpwd schema=GWY1; proc sql ; create table WORK.ACCOUNT as select ACCT_NUM, OPEN_ENRLM_BEG_DT, OPEN_ENRLM_END_DT FROM CDB.ACCOUNT; quit;

23. Solution proc sql ; connect to odbc(datasrc = "db2p" user=uid password=yourpwd); create table WORK.ACCOUNT as select * from connection to odbc (select ACCT_NUM, OPEN_ENRLM_BEG_DT, OPEN_ENRLM_END_DT FROM GWY1.ACCOUNT); disconnect from odbc; quit;

24. Conclusion