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.

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 don't have many end users on it at my company. 

The solution is really scalable.

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.

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.

The scalability can be somewhat challenging.

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

Right now, I don't know. I feel that before we build anything, we need to validate the data. Validating the data can be very tough and tedious. For instance, the other day I took one year and six months of data from a hospital and I'm now importing it one month at a time. It's very tedious. They needed data for their whole warehouse.

Then it would be very useful to have a lot of people working on it. It could take off nicely. First, you need to know that the data is correct, though. Right now, we don't know that the data is correct. It is very important to clean the data and ensure that your work is providing data which is really what you're trying to measure. That itself takes some time.

I import data each month and check that the number matches. I check that the net amount is correct. It all takes time. I know it's true if somebody else gets the same answer. Importing is where the issue is, though. That is where I'm having trouble because sometimes I find there's only partial importation.

I insert an extended table in the columns and rows with good formatting so that it doesn't miss anything. I think that that works well.

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.

There are many more business users in our organization, but there are only about seven people who really use Enterprise Guide as technical people. We do not see much of a problem with scalability for either group of users.  

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.

Due to the subscription mechanism, everyone in the company can use it so it's very good in terms of scalability.

No.