The IMSTAT procedure can help with most of what you identify. I don't know many details of licensing, but check whether you can use the data and server management statements for the IMSTAT procedure, such as the TABLE and UPDATE statements.
For your "Flow with PROC IMSTAT" comments:
Your three items are accurate predictions, it should be very fast. I’d also suggest a SAVE statement or some other means to make a copy for reload.
For the questions:
Q1—there is table-level locking. Requests for data that are already in-flight will see the old data. After the UPDATE request is complete, everyone sees new data.
Q2—There will be down time while the in-memory table is dropped and the replacement is loaded.
For the "Flow without PROC IMSTAT", consider reording the steps:
1) Update the “original” data (SAS data set, Oracle, other data source) first.
2) DROPTABLE the in-memory table and then PROC LASR ADD from the updated replacement
Users will experience downtime between the DROPTABLE and ADD.
Some of what I wrote assumes a distributed server. Let me know what I can clarify, and I'm really hoping that you have the IMSTAT procedure and find it useful.
... View more