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

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. 

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

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.

SAS Enterprise Guide's stability is fantastic.

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 stability is not very reliable.

The stability is quite good. However, I found out that we don't have a direct connection to the database. The company I'm working at now doesn't have a data warehouse. Data needs to be exported into Excel and then re-imported into SAS EG. That is going to be a little tricky because we really want all the rules to be imported. That's an issue. I don't know how deep the problem is, but there's a software limitation in importing so many Excel files and then joining them to the database. In Daman, where I worked earlier, we had direct connectivity to the database, besides the fact that we had a data warehouse.

It is very stable. 

We have not yet had any stability issues with the product. First of all, it is working well. Secondly, on the hardware side, we thought that we need to have more resources, so we did a capacity planning exercise involving SAS. They gave us some recommendations to improve our environment moving forward. We are installing a new setup on new hardware based on those recommendations. This should maintain our current level of stability and maybe enhance performance.

I feel that SAS has a good foundation. It has not given us a lot of problems when it comes to performance. We were being proactive. It works really well in combination with Teradata, but there is a lot of room for performance optimization with both tools.  

Using both platforms — and by that I mean featuring both SAS and Teradata — we do get our data out. In telco, the data volumes are huge, but even though that is the case we do not usually get stuck or experience stability issues.  

There are a lot of ways to get the performance optimization you need from products, get the work done, and delegate your time. It takes evaluation and revisions to accomplish those goals.  

It is reliable.

I think it is quite stable. In some circumstances, such as suddenly losing internet connection, it might return an error and you need to restart the whole program in order to make it work. 
Sometimes some data can be lot but overall I think that the stability is good.

No.