Hi All,
Thanks for the replies so far. To wrap up this thread...
Sorry, I think mentioning an external database was a red herring and opened a can of worms. I only mentioned it since it was the cause of the long running job.
Here is my code, edited slightly for privacy:
* fact table ;
data workspde.main_fact_table;
set odbclib.vw_record;
where
hospital_type eq 2
and
record_status ne 4
;
run;
* lookup tables - this took about 2 hours ;
* there is a reason I wasn't using pass through ;
proc copy in=odbclib out=workspde;
select lookup1 lookup2;
run;
* join ;
proc sql _method;
create table workspde.final as
select
*
from
workspde.main_fact_table a
left join
workspde.lookup1 b
on
a.key1=b.key1
left join
workspde.lookup2 c
on
a.key2=c.key2
;
quit;
About 2 mins into the join, I clicked stop. I think EG stopped about 10 mins later; I don't know for sure as I was in other windows at the time.
So at the time I clicked stop I wasn't running a query against an external database. I was using a SPDE library if that matters?
Like I said, I think EG can only work with what SAS Foundation provides. I don't have DMS available to test whether interrupting a similar join would immediately stop or not.
What I can say is that, speaking objectively and without bias (I love SAS software!) is that, for this situation, my user experience is better when I undertake a similar action in SSMS or Oracle SQL Developer. Clicking stop immediately stops the query.
I'll see if Chris' suggestions help.
Please post your question as a self-contained data step in the form of "have" (source) and "want" (desired results).
I won't contribute to your post if I can't cut-and-paste your syntactically correct code into SAS.
