I use the solution for database maintenance.
A user-friendly environment with good flexibility for adding modules or features
Pros and Cons
- "The solution effectively handles storing and maintaining information in databases."
- "The solution requires familiarity with its language so can be tricky."
What is our primary use case?
What is most valuable?
The environment is user friendly and there is good flexibility for adding modules or features.
The solution effectively handles storing and maintaining information in databases.
What needs improvement?
The solution requires familiarity with its language so can be tricky. A simplified language would be appealing to users.
A more user-friendly format for certain modules is desired.
The application and interface can be a bit heavy to install.
For how long have I used the solution?
I have been using the solution for one year.
Buyer's Guide
Microsoft Azure SQL Database
November 2024
Learn what your peers think about Microsoft Azure SQL Database. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.
What do I think about the stability of the solution?
The solution is stable.
What do I think about the scalability of the solution?
The solution is scalable. It takes a bit of knowledge about the process but then is really easy.
How are customer service and support?
I have not needed technical support.
How was the initial setup?
The setup can be a bit of a challenge until you get used to it. Once you have familiarity with it, setup is okay and takes about 30 minutes.
What about the implementation team?
A colleague assisted me with implementation.
What other advice do I have?
I recommending using the solution because it is effective and user friendly.
I rate the solution a nine out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Data Architect at ACPAS Loan Management Software
Affordable, scalable, and stable with valuable Azure Portal
Pros and Cons
- "Azure Portal is most valuable."
- "Service Broker should be added in Azure Cloud. Service Broker is currently available only in the on-premises version."
What is our primary use case?
We are using it for processing financial transactions. We have its latest version.
What is most valuable?
Azure Portal is most valuable.
What needs improvement?
Service Broker should be added in Azure Cloud. Service Broker is currently available only in the on-premises version.
For how long have I used the solution?
I have been using this solution for two years.
What do I think about the stability of the solution?
It is stable.
What do I think about the scalability of the solution?
It is scalable. We have six users and two people in our technical team for its deployment.
How are customer service and technical support?
I haven't used their support. I have only used the online material, and that's complete.
Which solution did I use previously and why did I switch?
We used PostgreSQL, which was on-premises.
What's my experience with pricing, setup cost, and licensing?
It requires a license. As compared to its competitors, such as Oracle, it is affordable and reasonable.
What other advice do I have?
I would recommend this solution to others. I would rate SQL Azure a nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Microsoft Azure SQL Database
November 2024
Learn what your peers think about Microsoft Azure SQL Database. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.
Sr. Technical Architect - Business Intelligence / Data Warehouse at a computer software company with 1,001-5,000 employees
User-friendly, stable, and PolyBase makes it easier to work with
Pros and Cons
- "The most valuable feature is PolyBase."
- "I feel that the price is high and it could be reduced."
What is our primary use case?
We are using SQL Server both on Azure and in a Spark environment, on-premises.
What is most valuable?
The most valuable feature is PolyBase.
The product is very user-friendly.
What needs improvement?
I feel that the price is high and it could be reduced.
For how long have I used the solution?
I have more than 14 years of experience in the Microsoft Data Warehouse platform.
What do I think about the stability of the solution?
SQL Azure is very stable.
What do I think about the scalability of the solution?
This is a very scalable product.
I am the only person in my company who uses it.
How are customer service and technical support?
I have not been in contact with technical support.
How was the initial setup?
The initial setup is straightforward and I don't find it complex.
What other advice do I have?
Overall, I am happy with this product and I recommend it.
I would rate this solution a nine out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
Information Technology Manager at OrchidaSoft
Easy to use with good performance and very stable
Pros and Cons
- "The product is quite stable. The performance is great and it's reliable."
- "It would help if the solution was more secure."
What is our primary use case?
The solution is primarily used as a database.
What is most valuable?
The solution is very easy to use. It's quite user-friendly.
The product is quite stable. The performance is great and it's reliable.
It's very good as an on-premises deployment.
We've found the solution to be scalable and easy to expand.
What needs improvement?
It would help if the solution was more secure. It's an aspect they could work on for future releases.
For how long have I used the solution?
We've been dealing with the solution for many years now. It's been a while.
What do I think about the stability of the solution?
The solution is stable. there are no bugs or glitches. It doesn't crash or freeze. It's reliable.
What do I think about the scalability of the solution?
The solution scales well. If a company needs to expand it, it can do so with relative ease.
How are customer service and technical support?
I've never directly dealt with technical support and therefore cannot speak to how helpful or responsive they are. Typically, if we have a problem, we just Google it and look for the answer online.
How was the initial setup?
We don't install it. We just use it. It is my understanding that in Azure we don't install anything. We go on Amazon or Microsoft and make a machine. There's no installation.
What's my experience with pricing, setup cost, and licensing?
You do need to pay a license fee in order to use the product. I can't speak to the exact price.
Which other solutions did I evaluate?
As we are planning to move to the cloud, we are looking at other options, including PostgreSQL or Microsoft SQL Server. It's my understanding that there is not a big difference between Microsoft SQL on Cloud and the Microsoft SQL Server. We still have lots of experience on Microsoft's SQL Server, and likely our company is still prepared to use Microsoft SQL on Azure, not PostgreSQL. On the other hand, a lot of ERPs nowadays on the market using PostgreSQL. So our developers in the company have experience with this product, PostgreSQL.
What other advice do I have?
We use the product and we offer it to customers as well.
We are planning to move to the cloud in the future.
I'd rate the solution at an eight out of ten. Our company prefers SQL Azure. We enjoy its capabilities. I'd recommend the product.
Until now, we don't yet have full experience with it and just we just apply it in very small scenarios - just for feasibility and to take some feasibility tests. We have yet to start converging our ERP. We're checking if it's good or available and if it will fit in some scenarios.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Consultant at SoftwareONE
Helpful support, scalable, and beneficial turning process
Pros and Cons
- "The backup solution in Azure is great, the firewall settings in SQL are very easy to use and work very well. Additionally, the turning process is very good and has improved the SQL services and queries."
- "SQL Azure could improve by adding more features."
What is our primary use case?
I have used SQL Azure for the backend tier application. If the customer has the flow change application with an application service, they will use the backend. I always suggest using SQL Server and Azure.
What is most valuable?
The backup solution in Azure is great, the firewall settings in SQL are very easy to use and work very well. Additionally, the turning process is very good and has improved the SQL services and queries.
What needs improvement?
SQL Azure could improve by adding more features.
For how long have I used the solution?
I have used SQL Azure within the past 12 months.
What do I think about the stability of the solution?
I have found SQL Azure to be stable.
What do I think about the scalability of the solution?
The scalability of SQL Azure is very good.
How are customer service and support?
The support of SQL Azure is very good.
How was the initial setup?
The implementation of SQL Azure is simple.
What other advice do I have?
I would recommend this solution to others.
I rate SQL Azure a nine out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
An good solution for a small/medium sized business with excellent technical support
Pros and Cons
- "In terms of stability, because Microsoft is the underlying technology, they are much more stable than say Oracle. Since 2014 they did a great job in offering stability, performance and high visibility on the solution, especially in comparison to the other competitors."
- "It's not a feature, but the solution only offers a certain amount of memory and that's limiting. The scalability should be extended to more than two terabytes."
What is our primary use case?
It's a platform that we leverage for multiple uses. There isn't a specific primary use case for the solution.
What needs improvement?
The concurrency between the amount of the transactional replications and the logging needs to be improved. Also, the GUI, the specific management tool itself, needs some improvement as well.
It's not a feature, but the solution only offers a certain amount of memory and that's limiting. The scalability should be extended to more than two terabytes.
For how long have I used the solution?
I've been using the solution for more than ten years.
What do I think about the stability of the solution?
In terms of stability, because Microsoft is the underlying technology, they are much more stable than Oracle, for example. Since 2014 they did a great job in offering stability, performance and high visibility on the solution, especially in comparison to other competitors.
How are customer service and technical support?
Technical support has been excellent.
Which solution did I use previously and why did I switch?
I didn't previously use a different solution.
How was the initial setup?
The initial setup is easy.
What's my experience with pricing, setup cost, and licensing?
I'm not sure what the exact price is, but it's a moderate amount. It's not too expensive.
What other advice do I have?
We use the on-premises version of the solution. I would rate it nine out of ten. I would definitely recommend it to an SMB, a small or medium-sized business.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Data Platform Architect at APN Promise
When we have a problem with a query we can trade information about what indexes we should create on tables
Pros and Cons
- "What is really helpful about the Azure SQL is that when we have a problem with our sound queries, we can trade information about what indexes we should create on tables. It's really helpful for me and also for developers."
- "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."
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.
Owner at AFF Group
It works in the cloud and made our back-end service scalable, but its cost efficiency could be improved.
Valuable Features:
- It works perfectly in the cloud.
- It made our back-end service scalable.
Improvements to My Organization:
In many cases we use Azure as a service platform.
When larger data is collected by continuous business operations and will be processed for further analysis, we use SQL Azure.
Room for Improvement:
- Scalability
- Cost efficiency
- Business continuity
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free Microsoft Azure SQL Database Report and get advice and tips from experienced pros
sharing their opinions.
Updated: November 2024
Product Categories
Database as a Service (DBaaS)Popular Comparisons
Google Cloud SQL
MongoDB Atlas
Oracle Database as a Service
Google Cloud Spanner
Yugabyte Platform
Oracle Exadata Express Cloud Service
IBM Db2 on Cloud
Buyer's Guide
Download our free Microsoft Azure SQL Database Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- When evaluating Database as a Service, what aspect do you think is the most important to look for?
- What would be the best application SQL optimizer over the WAN?
- Which database is the best for session cashing?
- What is the biggest difference between Google BigQuery and Oracle Database as Service?
- Which low-code (no-code) database solution do you prefer?
- Which databases are supported under DBaaS solutions?
- Why is Database as a Service important for companies?