Late response on this. (Like the EG issue...) But anyway. It seems that memory can be an issue, even I don't know wich.. We have lot of data on SQL Server that we often open in SAS EG. It seems to me that a very limited amount of rows are read if the table contain lot of columns. More rows are loaded on 'slim' tables. Forthermore it seems that a new database read is performed after each 'scroll latency'. Why? I don't know. Quite annoying for end users. E.g. Excel is fast in comparison. Is it possible to 'tell' sas to continue read more data in the background when viewing, or is it a config setting that is the root cause. ... View more

Hi, Just saw this old discussion. Did you get any solution? I have a similar problem. The answers about sorting, select distinct and transferring data is not the problem. (Just attempts of explantions). 🙂 In my query I get 30000 raws in the result-table. In SQL Server Management Studio it took more or less 10 sec. In EG, it took half an hour!! I have preassigned my library to get advantages from pass-though. This works well in 99% of our queries. Explicit pass-through will definately help, even it is not a smooth solution. Then.... I tried with select top n ... in the sql-code within the parentesis (SQL Server-side). Nice!! I wrote select top 50000... It helped even if my result-dataset was only 30k. With no top-stmt it took much longer time. In my case it depends on the complexity of the query and the tables in the query. When I removed one table (not the biggest) it used again 10sec to get 30k raws in the result-dataset. ... View more