SAS Enterprise Guide Review

Statistical functionality for non-technical users, but needs integration with scheduling tools

What is our primary use case?

We use this solution for moving users that need statistical data analysis and data transformation functionality that do NOT have a background in programming and/or SQL to a tool that allows for some degree of self-service. It also provides access to data sources (databases that require administrative access) that do not support individual user access.

How has it helped my organization?

Users that want to code SAS but don't have expertise or comfort coding and/or running SAS in a Unix background will use this as a SAS IDE, and not as a true graphical process environment with the ability to "re-use" common process patterns. If the user base can be given some good basic guidelines it can be a serious productivity improvement tool.

What is most valuable?

Statistical functionality and basic database interaction can become very straightforward for business users that don't have a background in SQL and data analysis. It allows business customers not familiar/comfortable with Unix environments to continue to use SAS functionality with interaction to data sources that are outside of their immediate control (application databases on remote hosts).

What needs improvement?

I would like to see integration with schedulers when run from hosting environments such as Citrix. Currently, SAS Enterprise guide in  CITRIX hosted environment appears to have access to Windows task manager to schedule EGP's. However, as soon as the client logs out due to windows "roaming profiles" being dynamic the scheduler does not work! It does not fail just doesn't do anything.

In administered/remote client/server environments( such as CITRIX), the ability for users to catalog and save database metadata independent of administrators interaction and support would be helpful.  Currently the user must (with the help of an administrator ) access a database from SAS Console with a valid credential and retrieve the database metadata (limited to what the user has access to via credential). If each user has potentially different access rights based on ID/password at the database an administrator with greater privileges must login to the database and catalog the metadata to cover ALL of the database metadata potentially used by any single user/group and then make it available to all groups. 

For how long have I used the solution?

We have been using this solution for three and a half years.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Add a Comment