It's a great tool to merge actual data analysis (which Lumira doesn't do that well) with visualization (which Lumira does well) - so it can be seen as Lumira for data analysts. However, a lot of the 'predictive' side is hidden/black box which can be frustrating for those analysts, so you could argue it is too complex for casual users, but too 'black box' for analysts.
SAS Enterprise Guide is good at taking various datasets and giving analyst/user ability to do some transformations without substantial amounts of code. Once the data is inside SAS, the memory of it is very efficient. Using SAS for data analysis can be helpful. It will give good statistics for you, and it has a robust set of functions that aid analysis.
It doesn't require you to have a Ph.D. to build models!
You can use it to address a very large and wide dataset without worrying about sampling.
Automation is in the product DNA. You can prepare your data, ingest it into the "Kernel", then get insights about what was found, decide to publish it and schedule scoring tasks or model refresh in the same product.
Process time of data is a bit long. It depends on the size of your data and complexity of your project tree.
There is not enough online free training videos.
While working with the project tree sometimes the links between the modules are broken or the order for running the modules get mixed up. You should know your project tree by heart.
It's not all bad, but I don't believe that an enterprise purchase of SAS is worth the expense considering the widely available set of tools in the data analytics space at the moment. In my company, it's a good tool because others use it. Otherwise, I wouldn't purchase a new set of it because it doesn't have some of the better analytical functions in it.
The documentation provides an explanation about what features are available but not necessarily what's happening behind the scenes. On the other side, the "community" has grown since the acquisition and most questions are properly addressed by SAP folks. Since the "product maintenance" mode announcement was made, there wasn't much new content published except on the Smart Predict side (which is built by the SAP Predictive Analytics team)
Although I use SAS support for information on functions, these are SAS related and haven't really come across anything that is specifically for SAS EG.
I've not worked hands-on with the implementation team, but there were no escalations barring a few hiccups in the deployment due to change in requirement & adoption to our company's remote servers.
We have typically used Spotfire for data analysis but decided to move to SAP Business Objects due to its innate connection with SAP. I found Lumira to be good for visualizations but it is not meant for data analysis. Therefore, we have introduced Predictive Analytics to see if it can fill that gap. So far, it's been far less intuitive than Spotfire to get started, and as far as I am aware so far, it does not bring many additional capabilities. I do, however, like that it utilizes the Lumira look/feel and integrates very well.
Why I prefer SAS EG: Data processing speed is much faster than that R Studio. It can load any amount of data and any type of data like structured or unstructured or semi-structured. Its output delivery system by which we have the output in PDF file makes it very comfortable to use and share that file to clients very easily. Inbuilt functions are very powerful and plentiful. Facility of writing macros makes it far away from its competitors.
Positive (cost): SAS made a bundle that include unlimited usage of SAS/Enterprise Guide with a server solution. That by itself made the company save a lot of money by not having to pay individual licences anymore.
Positive (insight): Data analysts in business units often need to crunch data and they don't have access to ETL tools to do it. Having access to SAS/EG gives them that power.
Positive (time to market): Having the users develop components with SAS/EG allows for easier integration in a production environment (SAS batch job) as no code rework is required.
