@Kurt_Bremser    DWH_ARRG is a table in DBMS. ... View more

@Kurt_Bremser @Tom @Reeza @Timmy2383 @VDD    Trying to create a subset from external database source (like DB2, GoogleBQ)   My data step is as below. No mixing done. We see SQL lines  because the tracelog is enabled. Please refer screenshot for details.                       Data tgt.arrg_5 ; set bq.DWH_ARRG(obs=5); run;      Yes, my query is why SQL displayed in the trace log does not show "LIMIT 5" or "TOP 5", whatever the DBMS equivalent is for OBS=5. My screenshot contains similar trace log both for OBS=5 and without it. How to explain to Non-SAS people that why trace log does not show the difference.     Also, how to explain to Non-SAS people on the below statement as the trace log does not depict it. We are dealing with source tables with huge number of records. "It is possible that the traces that SAS shows do not include commands that would limit the number of records returned from a    query."   Need help to prove that the intermediate result set (say 50 records) from the submitted query on DB source table( say having 100 records) does not contain “huge” number of records being pulled into SAS Environment and that only 5 observations are being “output” in SAS dataset.   ... View more

Below is the detail after enabling trace log :   1 options sastrace=',,,ds' sastraceloc=saslog nostsuffix; 2 3 4 libname tgt "/abc/xyz"; NOTE: Libref TGT was successfully assigned as follows: Engine: V9 Physical Name: /abc/xyz ODBC: AUTOCOMMIT is YES for connection 0 5 libname bq ODBC DSN="xxx" schema="TD"; NOTE: Libref BQ was successfully assigned as follows: Engine: ODBC Physical Name: GoogleBQ 6 Data tgt.arrg_5 ; ODBC_1: Prepared: on connection 0 SELECT * FROM TD.DWH_ARRG 7 set bq.DWH_ARRG(obs=5); 8 run; ODBC_2: Executed: on connection 0 Prepared statement ODBC_1 NOTE: There were 5 observations read from the data set BQ.DWH_ARRG. ... View more