@CaseySmith      Unfortunately even in SAS EG 8.5  ( the latest SAS EG version for SAS 9)  this Option is still missing. Very Disappointing. ... View more

Yes . The Temporary Table Support has been added to Snowflake in SAS     https://documentation.sas.com/doc/en/sasstudiocdc/3.8/pgmsascdc/acreldb/n0irpkyp22l7vzn1il9lx6f4wmx9.htm ... View more

@UttamKumar       Hi Uttam,  I am getting started with SAS Viya . I have a question on Path-based CASLIBS. I could not find a proper answer to this question. My question is regarding Path-based CASLIBS. Where exactly (meaning which server) is it path located? In a distributed SAS Viya environment, the user first connects via SAS Studio to SPRE and then starts a CAS Session. Since the SPRE, CAS Controller and each of the Worker Nodes are on separate machines, where exactly is the CASLIB path located? My initial thought was since CASLIB is a CAS server concept, all the paths it refers to are located on the CAS Controller Only but I think that is not always true. Also if the CASLIB Datasource path is on CAS Controller how does the user who connects to SPRE ( via SAS Studio) be able to place a file in the CAS Controller path? Does he have to log in to the CAS Controller machine using a SSH client like WINSCP to place the file in that path before he can create an In-memory table from that file using that CASLIB to do analysis or can the SAS Studio have access to this CAS Controller path ( even though it is a separate machine from SPRE) in some manner so user can just copy a file to the path using SAS Studio and then create an In-memory table using that CASLIB to do analysis on the table? My understanding of this Path concept is still not very clear mainly because multiple machines are involved here and I have never worked in such an architecture. Can you please elaborate on this if possible?   My understanding of this  Path concept is still not very clear mainly because multiple machines are involved here and I have never worked on such an architecture.   Can you please elaborate on this if possible?     Appreciate your help. ... View more

Yes  I did try that  but still did not work.   It turns out that my Networking Team have now fixed the issue .  There was a firewall blocking access to the OKTA URL from SAS server and once that was opened my issue got resolved.     @um3rella   BTW Since you are of the SNOWFLAKE & SAS Users  i found in this community, i wanted to check if you too faced this problem i reported here https://communities.sas.com/t5/SAS-Programming/Temporary-Table-support-in-Snowflake-from-SAS/m-p/735319#M229069   in your Testing of Snowflake from SAS .Basically if i want to join a SAS dataset with a SnowFlake Table I am unable to make use of the TEMPOARARY Table concept in SNOWFLAKE ( similar to VOLATILE TABLE  in Teradata) to do the join in a more efficient manner. Looks like R&D is still looking into this.   ... View more

@um3rella    I  am actually  trying to test SAS/ACCESS Interface to SNOWFLAKE  using Native  SSO ( OKTA as IDP)  per the link given here : https://docs.snowflake.com/en/user-guide/admin-security-fed-auth-use.html#native-sso-okta-only. But it does not work. I have added  the authenticator=https://<okta_account_name>.okta.com  , where  i have used my company okta account name  as per details given here : https://docs.snowflake.com/en/user-guide/odbc-parameters.html   ( search under authenticator conection paramater) . As per the documentation i have added this to the Snowflake DSN entry in the ODBC.ini  file. I am then trying to make  connection with the DSN option on the Libname statement as follows   but it throws an Error .   LIBNAME SF snow DSN=SF_Test user='test01' password="xxxxxxx" schema=INFORMATION_SCHEMA ; ERROR: CLI error trying to establish connection: [Snowflake][Snowflake] (6) Assertion failure: error_in_response_json ERROR: Error in the LIBNAME statement.   However my connection to the snowflake works if use a service account defined in snowflake with default authentication (snowflake)  and then run the Libname with DSN option and the Service account and password.. But i have to use OKTA since it is my company standard for authentication   SAS support mentioned this ( OKTA)  should work.  In their response they told me  "The SASACCESS  to Snowflake engine should  support the various authentication options currently supported by the driver via the 'Authenticator' driver option added through the CONOPTS syntax or in a DSN within the odbc.ini file. The only real restriction is that the authenticator must support programmatic authentication vs something that requires third party interaction such as 'externalbrowser'.  "   So i am surprised your connection using SSO with externalbrowser  atleast  works with no Errors.   I guess i have to reach out to SAS Tech support and do some more research.  Have you reached out to them? ... View more

@JBailey     Thanks Jeff. At our company , we are planning to replace Teradata with Snowflake . We have several SAS codes written which are currently using the VOLATILE table in Teradata as means of  quickly loading a SAS dataset ( 30K records or less) so that it can be joined with another Teradata table using Pass through in an efficient manner. But if we convert such a code to using SNOWFLAKE the inability of SAS/ACCESS Interface to SNOWFLAKE currently not supporting the loading of a SAS dataset into a TEMPORARY Table in SNOWFLAKE would cause the user to rely on the DBA giving permissions to create and drop TRANSIENT Table in SNOWFLAKE  and then load  the SAS dataset to such a table  to achieve the same join . Also the user has to make sure the TRANSIENT table is explicitly dropped at end each SAS code so that it does not carry over to next session and incur charges . This is ok for few users but with several SAS Users this becomes a burden for the DBA to grant such access and ensure users  drop the table explicitly . According to this blog post date , the TEMPORARY Table concept in SNOWFLAKE existed since 2018 : https://copycoding.com/d/temporary-vs-transient-tables-in-snowflake . Maybe it has undergone few changes since then I hope SAS R&D takes the above into account and implements this much needed feature as soon as possible. Thanks ... View more

@SASKiwi     This code below works as expected . But  unfortunately the inserting of records  using a SAS dataset does not work.  Also the DBMSTEMP=YES  option is not supported  on the snowflake Libname statement.   I hope SAS  will make changes via some  HOTFIX to support  the insertion of data from SAS Dataset into a TEMPORARY Table in Snowflake via SAS. I have a ticket with SAS Tech support on this .Yet to hear back from them.   Libname _ALL_ clear; LIBNAME T snow DSN=SF_Test user=User01 password="XXXXXX" schema=test connection=GLOBAL ; Proc Sql; Connect USING T; execute ( Create TEMPORARY TABLE SF_Temp( ID NUMBER , Name VARCHAR(50)) ON COMMIT PRESERVE ROWS ) by T; execute ( COMMIT WORK ) by T; execute ( INSERT INTO SF_Temp Values (100, 'John Doe' ),(200, 'Jim John') ) by T; select * from connection to T ( Select * from SF_Temp ); Quit; Output:     ... View more

@SASKiwi  Thanks for the Reply  but  unfortunately this too ends up with same  Error :   ERROR: File T.SF_Temp.DATA does not exist. ... View more

Did you ever find a solution to this question? Just curious to know. Thanks. ... View more