03-09-2016 10:08 AM
Yes it's possible.
Data in LASR is available to you by a libname.
But (it's kinda big but), be aware of that the whole table will be transferred to your local SAS session where your data step executes. So in this sense, it's not certain that's a advantage to use LASR data (if you are on a remote host to the LASR server).
What kind of operations is this, and why do you need to use LASR data?
03-10-2016 03:47 AM
What I am doing is typical SCD loads, so I will have to figure out new, chg, close records. What I thought of going is to load my dimensions into memory the day before, so that when my new data comes along, and I need to do lookups for SCD, I can save time by avoiding the loads of the lookup table since it was loaded prior to batch start. The only way I thought of pre loading was to load to LASR. The LASR server and workspace on on the same physical machine.
Also, how will this affect my data step code, where I would have loaded the table to memory I now have to point to a LASR table via memory addr/ref????
declare hash h0(dataset: "libname.table", hashexp: exponent);
Many thanks for the help
03-10-2016 11:35 AM
03-11-2016 04:03 AM
found another option, have not yet explored. proc server,
thanks for all the help.