Please share with the community what you think needs improvement with SAS Enterprise Guide.
What are its weaknesses? What would you like to see changed in a future version?
I had difficulty with the diagrammatic flow chart style representation of projects. When projects got too large and complex (which was basically every project, except the most trivial). There just wasn't enough real estate to display the flow chart and dependencies without a lot of scrolling, even when a flow was down to minimum tasks. My recourse was making the flow less "atomic". E.g., rather than use the various subset, etc., tasks as program nodes to display the details, I would write chunks of code that did a few things and use them as SAS program nodes.
For improvement, I think the user interface is too complicated. For some of the advanced functions, you need to learn some SAS code in order to get what you want. I'm ideally looking for is something that is purely code free and user friendly, which doesn't require any kind of programming. For additional features I really want something that can make it easier for me to schedule the programs. I do know that SAS now has a solution to schedule the program, but if it could be something built-in within the SAS Enterprise Guide, that would be great.
Now that I have experience with Tableau, I think the visualization part of SAS EG could be more user-friendly and easier to use. Tableau is very easy to use. It just does a lot of work by itself, including color schemes. I think that could be incorporated easily into SAS EG, which would make it a much better product. Then you would not need Tableau. Tableau just adds a few visualization aspects onto it, but it doesn't have powerful analytics like SAS. You can join a number of tables in SAS. That's what I find very useful. You can keep on doing that. You can just change one and get another report. You can save the script and run it again. SAS has all kinds of useful features, so I think it is very good for analysis. We actually saved millions of dirhams on licensing data, just by sitting here and getting data for a month. Now they're developing their routine using it as if it's Excel. I need to develop it because they don't really have it here. They were only using Tableau, but Tableau basically just sums up the analysis. It cannot do certain analyses. Mostly it's summing up and finding the fraction and percentage. You can easily do that, but it is a bit tricky to use because you cannot join so many tables and you cannot double it. That kind of function is not there in Tableau. That is the main drawback in Tableau. SAS is very good actually. It's not really user-friendly and it's difficult to configure as well. It's difficult to configure the graphs and charts. In Tableau, it's really easy to do that and I think that can easily be developed in SAS, considering that there are complex analysis functions already provided by the solution. It should also be easy to integrate any database like PostgreSQL. I have spent more than one hour on more than one occasion trying to connect it, but it did not work. I think that should not be the case. It should be just really comfortable to do this.
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.
I would like to see better Charting in this solution.