01-15-2017 03:40 PM
i just purchased a computer with i7 and 16gb ram etc. for some reason though, when I double click on the data in the explorer tab, the view table takes ages to pop up (30 seconds ish). This is super abnormal because my personal desktop with lesser spec is a lot faster. It opens view table at an instant like most other computers that I used in my life. Did you by any chance know the solution to this?
01-15-2017 05:22 PM
What's the libname statement for the library containing the table?
Is it a SASHELP view you are opening? If so what other libraries are defined?
01-15-2017 05:38 PM
Long shot but to be thorough: where is your work directory located?
Do you open a table or a view?
Are you using EG or SAS desktop?
Which explorer are you refering to? The SAS explorer?
01-15-2017 05:46 PM
Are you comparing apples with apples? Is this a comparison between the same view definition using the same data?
When you use a view (i.e. when you open it in a viewer) the view gets executed. If that's an intense query then it can take some time.
Some of the clients like SAS EG have also option settings limiting how many rows get loaded at once to the viewer if opening tables or views. You might want to investigate these settings as well as loading too many rows at once can heavily impact on viewer performance.
01-15-2017 06:23 PM
i essentially double click on data d1 in the work file. super simple and small data. it takes 30+ seconds to actually view table.
i am not a sas expert but would really love to get your helps.
01-15-2017 07:39 PM
I rarely use viewtable, although I have vu and vuh command macros on mouse actions. Over 20 functions on mouse actions. Some of these date back to the late 70s(ISPF) and have worked flaelessly without need to migrate with a new version of SAS. This functinnality has been turned off in EE and will not work in EG, UE or SAS studio The following command macros, can either be executed on the 'old text editor' command line, on a mouse action or function key. avgh proc means highlighted dataset avg proc means last dataset cnt cnt name*sex - last dataset number unique combinations cnth cnt name*sex - hi-lited dataset cntv cnt hi-lited variable last dataset con contents last dataset conh contents hi-lited dataset *debug macro debug hi-lited *dmp contents with sample data *dmph contents with sample data hi-lited dataset evl evaluate highlighted formula *frq freq sex*age last dataset *frqh freq sex*age hi-lited dataset frqv freq hilited variable last dataset iota column of consecutive integers *ls40 40 obs last dataset *ls40h 40 obs hi-lited dataset lsal all obs last dataset parh does hi-lited code have matched paraentheses (tells you what is missing) proch syntax for the proc - hi-lite 'proc reg' and get syntax with example *prtw prtw 'sex="M"' - last dataset subset printed *prtwh prtw 'sex="M"' - hi-lited dataset subset printed sumh statistics on hi-lited column of numbers sumv statistics on hi-lited variable last dataset unv proc univariate on variable in last dataset unvh proc univariate on variable in highlighted dataset vu viewtable last dataset vuh viewtable hi-lited dataset *xlsh view and edit hi-lited dataset in excel (may need a sleep w slow systems) *xplo xplo SUBSUM put exploded chars in past buffer *xplop exploded banner using Puthon exl open excel on last dataset exlh opend excel on highlighted dataset Start with a simple one and add over the years?
01-15-2017 07:42 PM
M0 is def buggy, upgrade if possible.
Also, turn off a bunch of the features here: