The "problem" here is that CAS is mainly built for analytics, not for DB operations.
Which we can see in the syntax limitations of PROC FEDSQL, data step and PROC CASL.
3.) So B would have 45'' records after the operation?
Is this repeated, like daily?
What is your pain point, from a user and/or maintenance perspective?
Again (partly) untested, but if you have avialable RAM, you could possible overcome limitations of UPDATE, recreate the table using a FEDSQL join query
proc fedsql sessref=MySession;
create table public.C as
select
coalesce(x.id,y.id) as id,
coalesce(x.name, y.name) as name,
coalesce(x.height, y.height) as height
from public.a x
full join public.b y
on x.ID = y.ID;
drop table public.b;
quit;
/* renaming back to 'B' */
proc casutil...
altertable...
... View more
