About JBailey

JBailey · ‎06-07-2019

Hi, This is exciting, but it isn't SOAP. There is a new SAS/ACCESS product for Salesforce. This product requires SAS 9.4M6. For more information take a look at the doc. SAS Doc (Non-Relational) https://go.documentation.sas.com/?cdcId=pgmsascdc&cdcVersion=9.4_3.4&docsetId=acnrdb&docsetTarget=titlepage.htm&locale=en Best wishes, Jeff @JBailey

JBailey · ‎06-07-2019

Hi, This is exciting. There is a new SAS/ACCESS product for Salesforce. This product requires SAS 9.4M6. For more information take a look at the doc. SAS Doc (Non-Relational) https://go.documentation.sas.com/?cdcId=pgmsascdc&cdcVersion=9.4_3.4&docsetId=acnrdb&docsetTarget=titlepage.htm&locale=en Best wishes, Jeff @JBailey

JBailey · ‎06-07-2019

Hi, This is exciting. There is a new SAS/ACCESS product for Salesforce. This product requires SAS 9.4M6. For more information take a look at the doc. SAS Doc (Non-Relational) https://go.documentation.sas.com/?cdcId=pgmsascdc&cdcVersion=9.4_3.4&docsetId=acnrdb&docsetTarget=titlepage.htm&locale=en Best wishes, Jeff @JBailey

JBailey · ‎06-07-2019

Hi, This is exciting. There is a new SAS/ACCESS product for Salesforce. This product requires SAS 9.4M6. For more information take a look at the doc. SAS Doc (Non-Relational) https://go.documentation.sas.com/?cdcId=pgmsascdc&cdcVersion=9.4_3.4&docsetId=acnrdb&docsetTarget=titlepage.htm&locale=en Best wishes, Jeff @JBailey

JBailey · ‎06-04-2019

Hi @KSAS56 If I have this right, you are driving this process from SSIS by connecting to SAS via a SAS OLE DB provider? If this is the case, I think you may have to create a SAS Data step view that converts the SAS date into something that SSIS can understand. This will enable the process to happen in one-fell-swoop; you shouldn't have to load the data into a temporary table then massage it. On the other hand, it is much easier to do this with SAS/ACCESS Interface to Microsoft SQL Server or SAS/ACCESS Interface to ODBC. Best wishes, Jeff

JBailey · ‎06-03-2019

Hi @oskrandres Hopefully, you have found a solution to this issue. SAS began support for Sentry (which I think is what you are referencing here) at SAS 9.4M5. You may need to upgrade your SAS environment to get this to work. The following information will help others, and perhaps you. SAS' bulk load functionality may be causing issues with write/read. Impala bulk load uses the same techniques as SAS/ACCESS Interface to Hadoop; direct writes to HDFS. Reading can also use direct HDFS access. To make use of these features, HDFS port(s) (8020?) must be open, and users must have read and write permissions to /tmp (HDFS file system). See the HDFS_TEMPDIR= option in the SAS/ACCESS Interface to Impala doc. Take a look at the doc. It may help shine some light on this: https://go.documentation.sas.com/?docsetId=acreldb&docsetTarget=p0qwbige1lq1p0n17mifkd4na4pl.htm&docsetVersion=9.4&locale=en Also, ensure that your SAS administrator has applied all available SAS Hot Fixes. Once again, support for this began at SAS 9.4M5. Hope this helps, Jeff

JBailey · ‎05-31-2019

Hi @ccaulkins9 Why, YES! I think I did;) Thank you! Best wishes, Jeff

JBailey · ‎05-30-2019

Thanks, @Patrick! You have made my day!

JBailey · ‎05-30-2019

Hi @SASUser1001, Azure SQL Database and Azure SQL Data Warehouse are two distinct databases. For example, SAS/ACCESS Interface to Microsoft SQL Server supports Azure SQL Database, but not Azure SQL Data Warehouse. You are probably asking, why? The Data Direct ODBC driver for Microsoft SQL Server that ships with our product does not support Azure Data Warehouse; it will eventually. Once the DD driver supports support Azure SQL Data Warehouse, we plan to look into adding support in SAS/ACCESS to Microsoft SQL Server. Fortunately, Microsoft provides a free ODBC driver that can be used with SAS/ACCESS Interface to ODBC to support both Azure databases. Here is the Azure SQL Data Warehouse doc. https://docs.microsoft.com/en-us/azure/sql-data-warehouse/sql-data-warehouse-connect-overview There is a link in the above doc that will take you to the following ODBC driver download page. https://docs.microsoft.com/en-us/sql/connect/odbc/windows/microsoft-odbc-driver-for-sql-server-on-windows?view=sql-server-2017 Here is the money quote, "The ODBC Driver for SQL Server supports connections to Azure SQL Database, Azure SQL Data Warehouse, SQL Server 2017, SQL Server 2016, SQL Server 2014, SQL Server 2012, SQL Server 2008 R2, SQL Server 2008, and SQL Server 2005." Hopefully, this will help you. Best wishes, Jeff PS: @Patrick, you are way too kind, but thank you for the nice call-out.

JBailey · ‎05-15-2019

Hi @WorkingMan I found your Tech Support track. It does sound like there is Kerberos weirdness taking place. @RPoumarede has created a great Hadoop/Kerberos article on the SAS communities. Take a look and see if it helps. https://communities.sas.com/t5/SAS-Communities-Library/5-tips-for-SAS-ACCESS-TO-KERBERIZED-HADOOP/ta-p/358746 Let me know if you need more assistance. Best wishes, Jeff

JBailey · ‎05-01-2019

Hi @DanielYar I am happy that you are making progress. If you need anything else, holler! Best wishes, Jeff

JBailey · ‎04-26-2019

Hi @DanielYar Are you using SAS Enterprise Guide? Best wishes, Jeff

JBailey · ‎04-25-2019

Hi @DanielYar, This sounds like a job for SAS Formats. Fortunately, there is a video for that. Creating User-Defined Formats with the FORMAT Procedure in SAS® Viya™ Hope this helps. Best wishes, Jeff

JBailey · ‎04-04-2019

Hi @fri0 Join processing can cause an increase in the size of data that is written to work. I am not sure where the space issue actually is, but this type of error is always a "Hey, I can't get enough of something" problem. Best wishes, Jeff

JBailey · ‎04-03-2019

Hi @fri0 This error usually occurs when SAS runs out of a resource. I would verify that SAS work has sufficient space. Best wishes, Jeff

Online Status	Offline
Date Last Visited	3 weeks ago