Sometime, one wants to work on a large table's subset and load it in memory for fast processing using the sasfile statement.
At the moment, one has to create a new table from the large table, and then load the table in memory.
This generates an unnecessary and large amount of disk access to read and write the wanted data.
It would be useful if the wanted data could be loaded directly as in:
set YEAR2012(keep=MONTH V;
sasfile SEP2012 load;
Since sasfile supports certain write operations (proc append, fsedit in edit mode, sql insert/update/delete), it cannot apply to views (which are always read-only).
In-memory reporting spells "Visual Analytics" nowadays, so don't eat your heart out...
If you want to stay in Base/SHARE land, another option would be to have an ability to output directly to an in-memory data set.
Perhaps a new libname engine, or a new ds-option...
Valid comment. Loading a view would mean the sasfile is read-only.
@ Linus. By the time VA can be used. 90% of the work has been done (behind the scene,to ready the data). It's this phase that need efficient data processing tools. VA does not replace "Base/SHARE land".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.