SAS Enterprise Guide Reviews

I am currently using this solution for testing purposes. I am working for a pharmaceutical company in Belgium, and we are building a data warehouse by using SAS Data Integration Studio, and we are using SAS Enterprise Guide to test our development. We are building Enterprise Guide projects by using query builder, filters, and other things. We have also built stored procedures. Sometimes, we also write SAS base code to perform unit tests after development and to do some sanity checks to respond to UAT questions. Overall, we are using the majority of functionalities of SAS Enterprise Guide. 

A client has used SAS Enterprise Guide to build an ETL process that involves extracting and transforming the data and producing reports. These reports are very crucial and useful for their monthly and daily activities. By using SAS Enterprise Guide, they are able to deal with end-to-end processes for their business.

Filter and sort query builder is valuable. The ability to do advanced SAS programming is also a useful feature because we can do anything by using Enterprise Guide. 

It has a lot of functionalities. We can build ETL processes. There are clients who are using SAS Enterprise Guide to build ETL processes. They have a SAS-based program that is scheduled to run at a certain frequency to produce some reports for the business. It is a very useful tool for ETL unit tests and functional tests. You can also do data science projects in SAS Enterprise Guide by using different statistics. During my MBA, we used SAS Enterprise Guide for our statistic course.

To query the data, there are many solutions such as SQL, but these tools are only a part of the integration. They are only useful for querying the data and require knowledge of SQL, so they are not suitable for business users. SAS Enterprise Guide can be very easily used by business users to filter and sort the data and build queries. It is not necessary to have coding skills to use SAS Enterprise Guide. For this reason, it is attractive for businesses.

Our data warehouse is built on the Netezza database. We have SAS BI, and we populate the Netezza database. When we have tables with, for example, a hundred million rows in Netezza, SAS Enterprise Guide doesn't work. It doesn't return any results. It works for around 30 to 40 million rows, but it is not working for anything more than that. This issue is only with the Netezza database. With Oracle, it is quite good. They can improve its performance with the Netezza database.

There should be one unique tool that includes SAS Data Integration Studio and SAS Enterprise Guide for more integration capabilities. With SAS Enterprise Guide, it is not possible to create connections and libraries and build transformations that can be used for other projects. This tool should have all capabilities that SAS Enterprise Guide does not have. Such a tool would be perfect because it will be used by developers and business users at the same time.

In addition to the integration capabilities, they should also provide more deployment capabilities. There should be an option to easily create SAS packages and export them from one environment to another. There could also be a possibility to connect with R and Python. Open-source tools are hot in the market nowadays, and it would be good to extend its capabilities. 

I have been using this solution since 2005. It has been almost 16 years.

It is very stable. 

It is easy to extend for fast data integration functionalities. We have around 1,000 users. They are developers, business analysts, and project managers.

In terms of usage, my clients don't have any plans to expand its usage.

They are responsive and very good. They respond within a day of creating a ticket. 

It is not quite easy to deploy. When we worked on the SAS migration project, the migration to Enterprise Guide was quite difficult. The deployment duration depends on the project. Generally, it would take a few days to solve all the issues.

For the SAS migration project, we worked with the SAS Belgium team. With their help, it was okay, but it should be easier.

In general, SAS has high prices, which is a reason why some clients don't use SAS solutions. The licensing is on a yearly basis.

I would recommend this solution. It is a very good tool for outputs from different domains, such as ETL reporting, data science, etc. It would be good to bring more functionalities similar to Data Integration Studio so that we have one single tool. 

I would rate SAS Enterprise Guide an eight 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 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 use it for programming. When we import data sets or databases, we work with data management and program scripts, etc. We have its basic license.

We work with large data sets that cannot be handled in Excel. SAS gives us the opportunity and the privilege to work with large data sets. It is very easy with SAS, and it saves time. For example, if I want to use the same data with Excel, it would take a whole day, but with SAS, I can do it in two or three hours at the most.

We are able to work on the server, and I can copy a data set and share it with someone in my team. Similarly, if I want some data from them, I can get it. Being able to work on the server and being able to switch from one user to another is a good thing.

It is reliable and powerful, and its community is very wide.

They should provide more information for the errors or logs. Currently, it gives you just the error message without explaining anything.

I have been working with this solution for two years. I use it daily for my work.

It is reliable.

It is scalable. It can handle large data sets. There is no problem with that.

Currently, we have a team of five people. I have a manager and other colleagues. All of us don't have the same role. We all handle data, but we have different diplomas. I work as an actuarial analyst, statistics engineer, and data analyst.

I am not sure if we have a contact for technical support from them, but there is a big community of SAS.

We used the open-source product R, which is not exactly similar. We switched because it was a part of our strategy to use SAS. In terms of time response, R is not very powerful. SAS is more powerful in terms of data management., and someone who is not very experienced with programming can use the UI.

I was not involved in the initial setup. Its maintenance and administration are handled by IT, but they're not very well-trained in this solution. It is a new one for them, and sometimes, we do get stuck because they are not very experienced with this solution and its features.

It is very expensive. We have a basic license, and there are many features that are not available with the basic version.

You must have a basic background in programming, such as SQL programming, to use it easily.

I would rate SAS Enterprise Guide an eight out of ten.

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.

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.