02-14-2018 11:45 AM
We are working on a technology transformation which involves deploying SAS Enterprise Guide with Redshift. We are using the RedShift ODBC driver and have found some issues. Most notably, we have some tables in RedShift which are large (multiple millions of rows). We noticed that SAS is sending a Select * to bring back all rows from the table before displaying them.
The experience in Enterprise Guide is horrible since this is a large dataset.
We tried the Tools->Options->Data->Performance to limit the number of rows to 10000 but this doesn't appear to be making any impact. The database is still doing a select * and taking forever to populate the grid on Enterprise Guide.
I have reviewed some of the AWS Redshift ODBC documentation and saw a couple of options such as UseDeclareFetch, SingleRowMode and UseMultipleStatements. I was wondering whether anyone else has come across this issue and been able to resolve it by configuring these parameters in the ODBC connection ini files or even fix it within the configuration of Enterprise Guide itself so that the 10000 limit is passed onto the ODBC driver properly.
Would appreciate any guidance on the above issue.
02-14-2018 12:04 PM
Hello @mcsherrya, Andrew,
perhaps I am wrong but it does not seem to be a problem on RedShift, but on configuration or the software version.
Have you already come across any of these links?
https://communities.sas.com/t5/SAS-Enterprise-Guide/EG-7-1-very-slow-data-view-performance/td-p/2019... ( @CaseySmith mentions "This issue was fixed in EG 7.12")
http://support.sas.com/kb/56/180.html (if data is coming from a large DBMS table, not SAS table, also fixed in EG 7.12)
02-20-2018 03:42 AM
I do not believe that this solution applies as we are on 7.15 of Enterprise Guide. The documentation links seem to point to a fix in 7.12 but clearly we are beyond that point.
02-20-2018 04:09 AM
Appreciate your help. We have a ticket open with SAS but they are being a little slow to respond. I was just checking the community to see whether anyone else has come across and perhaps overcame a similar issue.
02-20-2018 04:12 AM
I see. The notes above helped me with an EG 7.12+ (cannot recall the version) in AWS, but as I found later the problem stood still for later than 7.12. However, and as you said, your case might be completely different.