topic Re: SAS EG 8.3 is resulting only 10 records even if the table has more than 10k records in SAS Programming

SAS EG 8.3 is resulting only 10 records even if the table has more than 10k records

VVDR — Mon, 09 Aug 2021 05:06:31 GMT

Hi All,

I am posting this question on behalf of my Colleague.

My Colleague and myself running the same SAS code in SAS EG 8.3 version. I am getting full results (about 100s of records), but my colleague is getting only 10 records as an output ( it's happening for all the queries). I have verified the options in the tool tab. But it all looks same for both of us. Please advise me here.

Thanks.

Re: SAS EG 8.3 is resulting only 10 records even if the table has more than 10k records

jimbarbour — Mon, 09 Aug 2021 05:25:43 GMT

First, please have the following be run in your colleague's EG session:
PROC OPTIONS OPTION=OBS;

Second, has your colleague tried closing his or her EG session and opening a new session? (And then re-running)

Third, can you please post your colleague's SAS code and, more importantly, the entire log from their session?

Jim

Re: SAS EG 8.3 is resulting only 10 records even if the table has more than 10k records

Kurt_Bremser — Mon, 09 Aug 2021 06:34:49 GMT

see Maxim 50.

(check the first link of my footnote)

Re: SAS EG 8.3 is resulting only 10 records even if the table has more than 10k records

VVDR — Mon, 09 Aug 2021 08:49:19 GMT

Hi,

It is still showing 10 records only.

This is the example code.

Proc sql;

Select * from work.table;

Quit;

Work.Table has 100 observations and i am able to see all the records. But not my colleague.

Re: SAS EG 8.3 is resulting only 10 records even if the table has more than 10k records

Kurt_Bremser — Mon, 09 Aug 2021 09:16:02 GMT

Run a PROC CONTENTS on WORK.TABLE in both sessions to see what you start from.

Re: SAS EG 8.3 is resulting only 10 records even if the table has more than 10k records

VVDR — Mon, 23 Aug 2021 01:18:10 GMT

@Kurt_Bremser wrote:

see Maxim 50.

(check the first link of my footnote)

Thanks for your reply @Kurt_Bremser. Somehow it's data level permission issues and he is able to see all the records upon admins help with permission. Thanks again.