DATA Step, Macro, Functions and more

Connecting to Oracle SQL Joining or in SAS

Accepted Solution Solved
Reply
Contributor
Posts: 37
Accepted Solution

Connecting to Oracle SQL Joining or in SAS

[ Edited ]

Hi Gurus,

 

I have a situration where the SQL queue has some joining , do you think if this is a solution if i retreive data from each table and merge it in SAS locally instead of sending join queue to Oracle?

 

in regards to performance issue if the dataset is around 50GB.

 

Thanks

 

 


Accepted Solutions
Solution
‎02-04-2017 08:17 PM
Super User
Super User
Posts: 7,039

Re: Connecting to Oracle SQL Joining or in SAS

[ Edited ]

In general it will be faster to join in the source database rather than extracting.  Moving 50Gb of data would take a long time.

 

The only exception would be is if your join is essentially replicating data such that the result of the join is much larger than just pulling the source tables individually.  For example if the join was to convert a small code variable in your large fact table into a long descriptive text by joining with a dimension (lookup, format) table. In that case it might be faster post pone the lookup. Instead just keep the coded value in the large table so that less data needs to move from Oracle to SAS.  Then you could convert the code to the description in SAS.  For example you could convert the dimension table to a FORMAT and attach it to the variable with coded value.

View solution in original post


All Replies
Solution
‎02-04-2017 08:17 PM
Super User
Super User
Posts: 7,039

Re: Connecting to Oracle SQL Joining or in SAS

[ Edited ]

In general it will be faster to join in the source database rather than extracting.  Moving 50Gb of data would take a long time.

 

The only exception would be is if your join is essentially replicating data such that the result of the join is much larger than just pulling the source tables individually.  For example if the join was to convert a small code variable in your large fact table into a long descriptive text by joining with a dimension (lookup, format) table. In that case it might be faster post pone the lookup. Instead just keep the coded value in the large table so that less data needs to move from Oracle to SAS.  Then you could convert the code to the description in SAS.  For example you could convert the dimension table to a FORMAT and attach it to the variable with coded value.

Contributor
Posts: 37

Re: Connecting to Oracle SQL Joining or in SAS

thx Tom

☑ This topic is solved.

Need further help from the community? Please ask a new question.

Discussion stats
  • 2 replies
  • 160 views
  • 2 likes
  • 2 in conversation