SAS Enterprise Guide Reviews

My main use case for SAS Enterprise Guide is performing statistical analysis, scheduling job codes, and scheduling flows.

I use SAS Enterprise Guide for performing statistical analysis on clinical research data, for performing some clinical-related CSR activities, and for performing statistical analysis using various statistical concepts. I also schedule jobs and flows to automate my work.

I use SAS Enterprise Guide to perform workflows so I do not need to perform them manually. I schedule it so it performs automatically.

The best feature of SAS Enterprise Guide is scheduling jobs and flows.

The scheduling jobs and flows feature stands out to me because of its ease of use and reliability, as I have to perform so many tasks. By scheduling jobs and code, it makes tasks much easier for me.

By using SAS Enterprise Guide, which I currently use after previously using SAS 9.4, the time-saving feature of scheduling jobs and code and performing statistical analysis more advanced along with some low-code features makes our timeline very easy to achieve.

In SAS Enterprise Guide, I also use data management and statistical analysis, and the statistical analysis accuracy along with data management, data cleaning, and data performing is very good.

Some data visualization tools may be improved by SAS Enterprise Guide.

The interface of SAS Enterprise Guide is good, and I would not add anything else about the needed improvements.

I have been using SAS Enterprise Guide for more than two years.

SAS Enterprise Guide is stable.

SAS Enterprise Guide is highly scalable, and I am happy with its scalability.

The customer support of SAS is always outstanding, and I am very happy with it.

My experience with pricing, setup cost, and licensing is very positive, and I am happy with the costing and setup cost.

I have seen investment using SAS Enterprise Guide as it has some capabilities which require very little manpower, and also scheduling jobs and flows reduces human intervention. Timeline is saved and money is also saved, and I can see a return.

I suggest others go through SAS training before utilizing SAS Enterprise Guide because it is far more advanced than one might initially think.

I want to give one piece of advice to all SAS 9.4 users that you should switch to SAS Enterprise Guide and also look for SAS Viya too. I give this review a rating of 9.

The primary use case for this solution is data searching, modeling, data insights, and analysis.

One of the features of the SAS Enterprise Guide is that it has a server, and we can access the server. It's easier for us to access the solution and comparatively faster than a desktop.

Recently, we realized that SAS Enterprise Guide is not so stable and gives us some outputs which are not suitable, but it works well on rerunning the program. Sometimes it's quite hard to report its stability issues. Most of the time, its stability issues need to be reported with which our colleagues help. Another issue is that SAS Enterprise Guide gives us hardware output, but when we run a program that does not run correctly, we don't know what's wrong even though the output is good.

When we try to report to technical support and they run the program, they cannot find anything from the log, but it is the same issue we find in the solution when we run it afterward. Sometimes we need to restart the computer, and it works, which is not so good. We set up quite a few programs to autorun, and sometimes the customer is not confident that the result would be good.

It would be easier to use the solution if it had more functions. The solution needs to be more stable.

The additional feature I want to see in the future would be visualization because, currently, the visualization from SAS is a bit like Python or similar ones in general.

I have been using the latest version of SAS Enterprise Guide for many years.

I rate the stability of this solution a seven out of ten.

Currently, we are quite happy with the solution. It is scalable.

There are around 100 users in our company using SAS Enterprise Guide. Even our central team uses it.

We do not call the technical team of SAS for help. We seek help from our IT. So, it's hard to get this call.

The other products we used were similar to SAS. We don't have to use Python extensively because most of the data is already present. It is important to consider that SAS is open-source software, and sometimes I realize that I have some confidential data.

The solution was fine to deploy.

Overall, I would rate it seven out of ten.

SQL can be used with SAS. We also use Microsoft SQLs, which I still use on occasion. Part of the background is that the coding can be done using SQL. SAS allows you to write SCL statements and is mostly drag and drop, similar to Microsoft Access.

That is the SAS Enterprise Guide's drag-and-drop functionality.

I like the ease of use. 

Similar to Microsoft Access, you can drag and drop. You can simply drag and drop objects onto the page and create various flows to establish your query within the project. You can extract those queries from the preview as needed. 

The application uses standard SQL in the background. You can go behind the scenes and use the information you want to change. 

I like the interface where you can get help if you need it. They also have functions that can be called up to perform various tasks. For example, If you want to write a case statement for something, just put that function in there and see what syntax you might be missing.

It crashes more frequently than I would like. For example, you can create projects, but with our data system, the field changes from time to time. Our data-driven managers will occasionally attempt to update. They speed up everything and change the names of the fields slightly. When you go back in there and try to make changes, the project frequently crashes. When you attempt to make those various changes. And it can take some time to get it right. I guess what I'm working on right now is a project that I completed two years ago and needed to be re-run. It's also crashing because the data fields have changed.

It just gets stuck in a never-ending loop. Then you must control, alt, delete, and return to the program's main menu to exit. That's a little frustrating.

I would like it to give more information rather than just a forever loop that forces you to shut down the system. Give you more error messages without stopping the entire project, or even the entire application. That it displays more error messages rather than terminating the application.

I have been working with SAS Enterprise Guide for 10 years.

We keep it updated, and are using the most recent version.

We are currently transferring some of its data to the cloud, including some of the storage files.

It is used by our entire office as well as my old office. I work for the Department of Education and previously worked for another part of the state, and they both use it. SAS is used by others in the state. It's a well-known program.

I have not contacted technical support recently, regarding this most recent issue.

I'm familiar with KNIME, but it's been a while since I've used it. I took a look at it in the last 12 months, and I like how they combine flows for different purposes.

We had previously used SPSS in a BI query, but we switched to SAS about ten years ago.

They have SAS E Miner. I don't have much experience with it; I used it two years ago, but it includes a statistical practice package.

I did look at the prices a few years ago, and I believe it was approximately $1,000 for a yearly subscription at that time. I knew it was something I wouldn't be able to afford if I wanted to do some consulting. That was one of the reasons I looked into KNIME. There are several alternatives to SAS.

I would rate SAS Enterprise Guide an eight out of ten. They are good, but they could be better.

We use it as a comprehensive data analytics and modeling process within the banking sector. It streamlines our workflow involving multiple steps, from data extraction to modeling, and it is aimed at improving various aspects of banking operations, including customer retention and risk management.

The aspects that are the most crucial are data engineering and predictive analytics tools. 

I find it challenging when I need to use certain functions and predictive modeling techniques in SAS. The procedures and data steps for database analysis take longer, and I've noticed that the current version we are using, lacks support for advanced modeling techniques. We've requested support for these advanced algorithms, but it seems there have been challenges in implementing them. As a result, we are facing difficulties in developing advanced models. Another issue we've encountered is that the community support for SAS is relatively limited compared to open-source environments.

I have been working with it for two years.

Over the past three months, we've been encountering a persistent problem where our sessions are inexplicably closing. This issue is especially troublesome when certain tasks run for extended periods, exceeding one hour or even five hours. The problem appears to be linked to session duration, which is limited to just sixty minutes.

The scalability can be somewhat challenging.

The technical support response time has been consistently slow, and this has been a concern. As vendors for the banking sector, we are responsible for maintaining all the servers, which means extended downtimes are more frequent. When we encounter critical issues, it takes quite some time for the support team to respond, causing additional challenges.

Neutral

We use Python as part of our scheduled tasks, especially for handling big data. In open-source settings, there's a more extensive and active community that helps address discrepancies, code errors, and other issues. When you encounter problems and search on Google in open-source contexts, you often find numerous examples and solutions to common errors, which is immensely helpful compared to our current situation with SAS.

The initial setup process was not overly complex.

The pricing and associated costs are substantial.

Overall, I would rate it six out of ten.

SAS Enterprise Guide is an Oracle tool that you use to query databases. The government health agency I work for only allows me to use SAS. We have about 200 users.

Enterprise Guide is much better at generating reports than many solutions. We often use it to generate reports, and people interpret them how they like. They often probably use Excel spreadsheets or something like that after they get our data.

I have been using SAS Enterprise Guide for about 10 years.

SAS Enterprise Guide seems highly stable, but the problem at my organization is that we're constantly running out of storage space because they don't pay for enough storage.

It's an issue with IT management. They're always telling us to clean up the servers with our reports because they're running out of space. It's only storage. They should just buy some bigger servers and disks. 

We don't have many end users on it at my company. 

SAS support is excellent. 

SAS is much better than Click because Click requires us to restrict data into sets unnecessarily, and it adds an extra layer. SAS support is also better. 

Setting up SAS Enterprise Guide is somewhat messy and complex, but it works for what we do.

SAS Enterprise Guide is probably expensive, but I don't deal with the financial side. Everything is expensive these days, but they're all just tools. 

I rate SAS Enterprise Guide nine out of 10. 

We use SAS Enterprise Guide for ETL and data processing.

My team is not using SAS Enterprise Guide extensively, but I imagine it's being used heavily for processing a lot of workloads in my company which has been an improvement.

We are using SAS Enterprise Guide on a basic level and the Pro SQL and other procedures within it are the most useful right now. Additionally, it has a wide feature set and capabilities

We don't use SAS Enterprise Guide that much here because we haven't explored some of the statistical modeling capabilities. However, I do not think SAS Enterprise Guide provides all the machine learning features that we want. Those would be separate products from SAS, such as SAS Buyers or any of the other solutions, which will give us the capabilities that we are looking for. 

I have been using SAS Enterprise Guide for approximately 10 years.

SAS Enterprise Guide's stability is fantastic.

The scalability of the SAS Enterprise Guide is good.

We have several hundred users using this solution in my organization. We have data analysts, data scientists, developers, and other roles using it.

We do not have plans to increase usage because we only use the solution for a particular purpose.

I have not contacted the support from SAS Enterprise Guide.

We have seen a return on investment from using SAS Enterprise Guide.

SAS Enterprise Guide does what it does quite well, we use it for a particular purpose. We haven't explored some of the other opportunities with a lot of the statistical modeling and other options that it provides, but those would be nice to have.

I would advise others to start with small use cases and then scale up. It will scale very well to many of the functions that you want in data science and data engineering.

I rate SAS Enterprise Guide a seven out of ten.

The reason I wouldn't rate Enterprise Guide as 10 is that it is lacking some features that we are looking for.

We are using it for data cleaning and data lookups.

The data cleaning part is valuable. SAS is a very powerful tool to work with and connect with different sources. We have several tables, and we are looking up tables from one place to another place. We are connecting with different data sources. The data is not coming from one source. There are several sources of data, and we have information coming from different sources. There are some flat files, and there is some information from the data warehouse.

It is expensive.

I have been using this solution for the last 10 years. I just deployed this solution in my new organization, and I have used it in other banks as well.

It depends on the usage of the current organization. Stability depends on the business technology team that owns the on-premise server. It requires updates on the server side. So, you need someone who is an expert and can update the patches or requirements every month or every three or six months. When the renewal happens, you need to update to the new version. You have to update the new patches based on the Windows requirements. So, it depends on the technical capability. I'm not the owner of the server. I'm basically a user, but I know that when the server is down, we cannot write queries and fetch data from the server. It is the application layer that actually fetches the data from database servers.

It is good. I can give them almost 100% marks in terms of scalability. It has all the solutions that I can use for the next five years without having any upgrades.

Every single department in the organization is using this solution. We have almost 100 people.

I didn't interact with them. So far, everything is going fine. If problems happen, it is a normal thing. It is not a big deal for me.

I never used any other software. I just used this one.

It's complex. It's not easy to use. The deployment took six months.

It was done by consultants.

It is expensive. We get a different price based on our corporate rate. So, I'm not sure what the general cost is because we got a special rate for it.

It depends on the users. It depends on how you use it. Sometimes, if you run a lot of queries together at the same time, it'll be difficult. If you're using it in a sequential manner, it'll be much better. So, before starting, you should understand the usage of SAS. It's not like Microsoft Office. It's a little bit complicated or delicate software. So, if any wrong query is executed, the query would keep running, and you might think that it'll not come back.

I would rate it a seven out of ten.

I am using the solution for programming, data manipulation, and query building.

The solution is user-friendly, the resource for the query builder is very useful, and the ability to explore the data is a benefit.

I feel I use maybe a 10th of the potential of the solution. It has a lot of features for reporting and data, with a lot of exploration you can do. There are many research areas that give you logistical information about the data.

There needs to be a community of SAS Enterprise Guide users for assistance. For example, as they do for Python or SQL. 

The interface could be simplified to allow quicker tool access and usage.

I have been using this solution within the last 18 months.

The solution has been stable. However, we have had some clients having connection problems.

The solution is really scalable.

Sometimes you have to rely on support, and that is a bit time-consuming. They take a while to respond to an inquiry. We are left to use the internet for answers.

I would recommend this solution. However, it depends on the use case that they want to use it for. I am not sure of the price of the solution which could play a big role in if it is useful enough to purchase at the price. It is a solid solution in my experience.

I rate SAS Enterprise Guide an eight out of ten.

Mostly accessing medical claims data from mainframe warehouses, plus occasional spreadsheets, etc. Aggregating and scoring according to specified algorithms and identifying medical practitioners who are statistical outliers with respect to certain procedures.

Loading results of these analyses into Microsoft SQL Server and writing queries for access by users without SAS licenses.

Running SAS EG on a networked Windows PC, connected to a SAS Grid on a Unix network, accessing data warehouses in Teradata.

In general, for large complex programs, I found myself wishing I had access to the base SAS environment.

People did not use the EG specific features, just writing long programs in Base SAS, using EG to launch them. 

Also, I could never get the ability to run code in parallel on the SAS Grid. For instance, long running data pulls from multiple databases, when working, were slow when running the entire program sequentially in Base SAS.

Areas where SAS EG does a better job than regular SAS are in the realm of importing and exporting data. For instance, exporting a SAS data set in Unix to an Excel spreadsheet on a PC is a simple task compared to doing the same task with Base SAS.

The usual virtues of drag and drop style interfaces with a flow chart-like depiction of the project and the ability to separate the project into individual flows, i.e., one for the slow data pulls from the databases, a second for data crunching, and a third for the outputting to the PC. The ability to copy the underlying SAS code from a node and modify it and/or reuse it elsewhere, and also the built-in versioning of program code stored in the project, is very useful for something that is run periodically and frequently updated.

The ability to include it as part of the project code housed on either the PC or the UNIX box is handy, although EG doesn't provide the ability to version the code.

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.

Three years.

Management liked it a lot because the license per seat was cheaper than a traditional SAS environment.

Our primary use case for the solution is creating views and filters, and we deploy the solution on-premises.

The query builder feature is the most valuable.

The stability of the solution can be improved. 

We have been using the solution for approximately three years and currently use version 8.3.

The stability is not very reliable.

The solution is scalable. Approximately 50 people are using the solution in our organization.

Our partner provides our technical support.

I rate the solution an eight out of ten.