Date:         Wed, 4 Jan 2006 08:57:58 +0000
Reply-To:     Guido T <cymraeg_erict@HOTMAIL.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Guido T <cymraeg_erict@HOTMAIL.COM>
Subject:      Re: The option INOBS= in PROC SQL
Comments: To: rune@FASTLANE.NO
In-Reply-To:  <B8ydnVM-1aWrGCbeRVnzvA@telenor.com>
Content-Type: text/plain; format=flowed

>From: Rune Runnestø <rune@FASTLANE.NO>
>To: SAS-L@LISTSERV.UGA.EDU
>Subject: The option INOBS= in PROC SQL
>Date: Wed, 4 Jan 2006 09:20:06 +0100
>
>Below is two proc sql that differ only in the inobs= option. I just wonder
>why the proc sql that use the inobs=10 doesn't fetch the *first* of the
>rows
>that are in the result from the first proc sql.
>
>---
>*the first query;
>  proc sql;
>   select
>    ffid,
>    name,
>    pointsused
>   from sasuser.frequentflyers
>   where membertype='GOLD' and pointsused > 0
>   order by pointsused;
>  quit;
>
>*the second query;
>  proc sql inobs = 10;
>   select
>    ffid,
>    name,
>    pointsused
>   from sasuser.frequentflyers
>   where membertype='GOLD' and pointsused > 0
>   order by pointsused;
>  quit;
>
>
>Regards
>Rune

Hi Rune,

The INOBS option just restricts the number of obs input from your source
dataset (sasuser.frequentflyers) after the where clause has been applied (I
think), without any concern for the later ORDER BY POINTSUSED.  These
records could be any of the records from sasuser.frequentflyers, depending
on how they are stored.

++ Guido