BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
gyambqt
Obsidian | Level 7

Hi Experts,

I have a SQL as shown below:

 

 

select stg.* from(
select stg.ID, stg.revision_dttm, stg.no,date, stg.value,
row_number() over(partition by stg.ID order by stg.value desc,
stg.date desc) as tmp_row
from table1 stg
) stg


inner join table2 tref1
on stg.ID = tref1.ID and
stg.revision_dttm = tref1.revision_dttm
and tref1.id2='1'

 

 

each time when I run script above I was getting different result for tmp_row. why is this happening?

 

 

 

run1:

ID               revision_dttm                    no                       value                  date                             tmp_row
1                2020-02-14 08:12:49         a                         0                     2020-01-20 00:00:00         1
1               2020-02-14 08:12:49          b                         0                       2020-01-20 00:00:00        2

 

run2:

ID               revision_dttm                    no                       value                  date                             tmp_row
1                2020-02-14 08:12:49         a                         0                     2020-01-20 00:00:00         2
1               2020-02-14 08:12:49          b                         0                       2020-01-20 00:00:00        1

 

1 ACCEPTED SOLUTION

Accepted Solutions
JBailey
Barite | Level 11

Hi @gyambqt 

 

Just a guess.

 

The ORDER BY clause sorts on stg.value and stg.date. These values are the same in your output. So, the sort is coming into the PARTITION clause in a different order but is still correct. Greenplum is a highly parallel database. Nodes could be producing intermediate result sets at different times. Thus, producing a random assignment of the tmp_row value. 

 

Best wishes,

@JBailey 

View solution in original post

1 REPLY 1
JBailey
Barite | Level 11

Hi @gyambqt 

 

Just a guess.

 

The ORDER BY clause sorts on stg.value and stg.date. These values are the same in your output. So, the sort is coming into the PARTITION clause in a different order but is still correct. Greenplum is a highly parallel database. Nodes could be producing intermediate result sets at different times. Thus, producing a random assignment of the tmp_row value. 

 

Best wishes,

@JBailey 

hackathon24-white-horiz.png

The 2025 SAS Hackathon has begun!

It's finally time to hack! Remember to visit the SAS Hacker's Hub regularly for news and updates.

Latest Updates

How to Concatenate Values

Learn how use the CAT functions in SAS to join values from multiple variables into a single value.

Find more tutorials on the SAS Users YouTube channel.

SAS Training: Just a Click Away

 Ready to level-up your skills? Choose your own adventure.

Browse our catalog!

Discussion stats
  • 1 reply
  • 745 views
  • 0 likes
  • 2 in conversation