The solution was fine to deploy.

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

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

The initial setup process was not overly complex.

The initial setup was simple. Once you understand the concept of their scale, how they join, and the logic behind the whole thing. If you know how to join tables this shouldn't be difficult. It's not complex. The tables are complex, but the underlying principles are not complex.

We had a three-day introductory course only. It doesn't tell you every unique case. There are a lot of things, but you can figure it out. I think you start doing it right away, but then you can go to YouTube and see someone use it as well.

I've got a first degree in mathematics, so I understand this kind of concept easily. That is my background. Still, I need to know how this works. We figured it out from YouTube and friends. Now I understand the product well.

When I joined this company, they did not have SAS at that time. They did not know what SAS was. They only had Tableau. I told them to let me try that with that. I taught myself Tableau and could use it because I knew that the concepts are the same. The logic is the same. Boolean algebra is the same. Just like that, I started using it. Within two hours, I started using Tableau.

Now I have SAS also, so I am using both now.

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.

The initial setup is a bit complex. For the guest access setup, that is something that we do ourselves. But when it comes to the server installation, that is where we require support from SAS. When it comes to the server installation, the configuration is usually done by SAS themselves. The setup is something that is certainly too complex for business users or people who do not have a technical background. It is usually good to involve SAS even if you are going to an upgrade. It can just make things go more smoothly and keep from wasting time with unnecessary issues.  

We just have one guy for the maintenance of the system. If there is a problem, then he can rely on support. There is only one guy because the product is pretty stable.  

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.

I think initial setup is quite straightforward but if you compare it to say, Access, then  it's more complicated to use than other, more traditional tools.

The initial setup was not complex. It took only two days.