SQL Azure Review

When we have a problem with a query we can trade information about what indexes we should create on tables


What is most valuable?

What is really helpful about the Azure SQL is that when we have a problem with a query, we can trade information about what indexes we should create on tables. It's really helpful for admin and for developers.

What needs improvement?

I need something which is in one place so I can automate the Azure data factory, but it's a different tool. It's not easy and in one place, so I can't switch to the other tool and do something there, automate everything there in the on-prem infrastructure, and then have everything in the agent. I can just pick one packet and use it. However, I want to be able to click it and run it. 

We could definitely use something which can automate the work. For example, I know there are a lot of tips like what indexes you should use, or what security features you should look at with your current SQL server. The acquired performance is assured, so some more statistics about acquired performance would be really valuable for the developer and also the administrators who use it. That would be really valuable, but we also need something which automates the work in particular SQL agents. I'm disappointed that it is not in the simple plan and I have to buy a higher plan.

For how long have I used the solution?

I've been using the solution for two years.

What do I think about the stability of the solution?

I didn't notice any problems with the performance of this product. It's pretty stable. Computing is working as it should, so it's really good. It's stable, and the performance is really very good. That's what I really like about Azure SQL.

What do I think about the scalability of the solution?

It's very scalable. That's why we like cloud solutions. You just add on every time you need some more performance pages. I just change the plan and it works.

How are customer service and technical support?

To be honest I have never had a problem that called for technical support. I never had a chance to contact support because it works without any problems. It's the same thing with clients because we work very closely with our customers. Every time they have some problems we get a call from them and can solve the problem for them.

How was the initial setup?

The initial implementation is straightforward. There are a few click-throughs and you have ready to use infrastructure. It usually takes five to ten minutes. Even less.

What other advice do I have?

We use a few different versions. It depends on the project. We use the S-1, 2, and 3, depending on the customer's requirements.

If we compare, for example, the cloud infrastructure and on-prem infrastructure, there are lots of good things about cloud infrastructure because we can scale the product so that every single time when we need more performance, more computing, more storage we can just reach to the higher plan, and we can use it. There is obviously cost reduction because although we still need an on-prem trader for SQL parts, it's not hard like it was in SQL brand because we also had to care about the infrastructure too. Right now, we are concentrating on the software which is good and saves us money. 

I would rate this solution nine out of ten because it offers a lot, including statistics and other things which are very hard to get from Azure. However, you have to specify what you actually would like to monitor, which is not straightforward.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
Add a Comment
Guest
Sign Up with Email