SAS will use implicit pass-through when it can to speed things up when using libname access.
In most instances, you should simply use libname access when you want to see both SAS and RDBMS data at the same time. You could pass the contents of an entire table in a macro variable or a set of macro variables and then use insert statements to include them, but it's not a good idea it won't be faster than using a libname connection and has a lot more risk of error (and is more work). As such, you can perform in queries by putting the list of values in a macro variable and submitting it but you cannot reference a SAS table directly. The only way you can access information from SAS in explicit pass-through is to transmit it as text in a macro variable.
#USE SAS SCHEMA STAT TRANSFER CODE#
Pass-through is literally taking code and submitting it for execution on the remote DBMS, SAS is just a dumb terminal. In SQL Passthrough, the connected session cannot see your SAS libraries, unless it is separately connected through DBMS-specific connection methods (unlikely).
#USE SAS SCHEMA STAT TRANSFER HOW TO#
Is it possible to copy a local SAS table into oracle via an SQL pass-through? If yes, how to proceed. With this method, SASHELP.cars is not found by the procedure. I used a first method (that works perfectly) with a libname to oracle: LIBNAME dblib ORACLE USER=usr PASSWORD="&dbpwd_sas" PATH="DM_CT_TEST" SCHEMA="SAS" īut I also try to use another method via SQL pass-through that doesn't work: PROC SQL NOPRINT ĬONNECT TO ORACLE (USER=usr PASSWORD="&dbpwd_sas" PATH="DM_CT_TEST") Actually I want to copy a table from one of my local SAS libraries to Oracle. I would like to create an oracle table via two different methods in order to compare performances. After making some searches that didn't lead to anything useful for me, I would like to ask you this question.
0 kommentar(er)
