Couchbase Capella vs Microsoft Azure SQL Database comparison

"The way the nodes are managed is interesting."

"The initial setup was straightforward."

"We primarily and generally use it only for DB purposes. When it comes to the Azure part, we can easily provision, scale up, and scale down the generator machine. This kind of flexibility is the USP of SQL Azure. Its interface and ease of use are also valuable. It is very easy to use and integrate with multiple databases. If I need to pull in or import some data from my on-premises database, the ease with which you can connect and pull the data, not only from SQL Server but also from other flavors of MySQL or even Oracle, is very good."

"Azure Portal is most valuable."

"Coding does not require much effort."

"SQL Server's ability to automate data processing and validation through virtual agents and integration with other Microsoft applications like Power Virtual Agents and Azure SQL has dramatically improved efficiency."

"We have used SQL for a long time. Azure SQL has helped teams across the organization to use SQL's full potential. I can't say what the cost savings were precisely, but I believe it has reduced the total cost of ownership."

"The scalability and simple management of the infrastructure are the most valuable features."

"The most valuable feature from the infra point of view is you don't have to keep any on-prem infrastructure, it is available all the time whenever you want to access it."

"My impression is that this solution is quite stable."

"The product could be improved by including a log section for tracking activities, enhancing database integration, and providing more transparency regarding pricing and monitoring activities."

"Rebalancing could be improved."

"I think this product can improve its integrations with business intelligence software. The integrations are always cumbersome due to the approvals, passwords, et cetera."

"I would like to the solutions scalability to be improved."

"There isn't any new improvement that I can think of at the moment. We have different deployment choices, such as running SQL on an Azure VM or deploying SQL-managed instances. The managed instance is a significant improvement over running SQL in an Azure VM."

"I was using a user list for connecting a program in OTF for getting information. The connection in SQL Azure can improve by being easier because at the moment I have to use private certificates for user authentication. I had to do additional configuration to have the connections."

"The product's pricing needs improvement."

"The preset configuration switches we can select on SQL Azure should be made more liberal to work on."

"SQL Azure could improve by adding more features."

"Integration needs to be improved for this solution."

"It is quite expensive. I would definitely recommend not using the pay-as-you-go model because this will just mean all your money will go to Microsoft. So, really make sure to control resource usage as much as possible."

"There is a license required to use the solution and it cost $30 to do the installation."

"SQL Azure's licensing cost is expensive."

"The pricing is actually complicated, and that is probably one downside of it. In some respects, although we can plan for the costs on a month-by-month basis, we are finding it hard to project our costings for it. Fundamentally, Microsoft is offering two pricing models, and it is challenging to understand the differences between the two. We're basically on the DTU model at the moment. That may change in the future as the size grows, but it is one of those things that we'll end up monitoring as we progress. At the moment, to get a reasonable response, generally, the price is a little high for us, but it is one of those things for which we know that we can do improvements on our code. So, it is not just the service that's the problem; it is some of the things that we need to do as well."

"I would rate the pricing a seven out of ten."

"Offers options for paying the license on a yearly or a monthly basis."

"The license is based on the number of users."

"When you go with SQL Azure Database, you can create a small database, which is around $4 to $5 per month for development purposes."