Couchbase Capella vs Microsoft Azure SQL Database comparison

"The way the nodes are managed is interesting."

"The initial setup was straightforward."

"The most valuable features of SQL Azure are its reliability and quick scalability."

"The Power Virtual Agents help us go through documents and load data into SQL."

"Overall, Azure SQL has been great. The ease of deployment and scalability are significant reasons we push our larger clients to Azure. We could throw the kitchen sink at the thing if we wanted."

"I like that Microsoft Azure SQL Database is almost identical to an on-premise SQL Server except for a few things, like how you edit rows and some jobs that you can't run."

"Azure SQL Database has significantly reduced our total cost of ownership by eliminating the need for managing physical infrastructure, including data warehouses and data centers."

"They have good documentation. It's concentrated information."

"It's the type of product that doesn't need much technical support assistance as it works seamlessly."

"The initial setup was straightforward. We did not migrate from an existing system but implemented it from scratch and did not require Microsoft support. We were building Power Platform apps using SharePoint databases and Excel. And after that, we realized that we had to integrate it with SQL. It wasn't too hard, and our partners have people with experience."

"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."

"There are some limitations for cross-database queries and features. The migration of data from older systems should be easier. For deployment, there are too many options, which sometimes makes it difficult to figure out the best option. There is not enough information to help you to find the best option for deployment. There should be more documentation about this."

"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."

"One of the nice features in Microsoft SQL Server is the SQL Server CLR, which we sometimes need to use to protect our procedures using C# or CLR. This is not available in the SQL Azure database."

"I would like to see more compatibility with SSMS and more backward compatibility with regular on-prem SQL."

"One area for improvement could be expanding the search queries using vectors or AI inside the database. After seeing its potential in a workshop, I realized the usefulness of more advanced search queries with AI."

"The customer support is hard to reach, with Microsoft’s technical support being difficult to get in touch with."

"Although the solution integrates well into Azure’s ecosystem, it has limited capability and is incompatible with many third-party applications or tools."

"I feel that the price is high and it could be reduced."

"It requires a license. As compared to its competitors, such as Oracle, it is affordable and reasonable."

"The solution is moderately expensive."

"It only has a subscription-based license."

"SQL Azure is an expensive solution."

"It's reasonably priced and when you compare it with other products in the cloud environment, it's cheaper."

"The cost is around $2,000 per month."

"In terms of the cost, SQL Azure is a pay-per-use solution, particularly because it's a cloud subscription, so you pay as much as you use it."

"I have an annual spend number, and it is in the hundred thousand dollar range. There are no additional costs to the standard licensing fees. Even though you have to look at the cost numbers of what you're going to be charged on a monthly basis, what you have to also remember is that your application may need a lot of rewriting and things like that. You get charged not just for the monthly costs but also for the transactions that occur. If your access to the data layer is not so efficient, your costs will go up because you're pulling far more data than you potentially need. These are hidden costs that nobody ever considers. If your application is not written very efficiently, you may actually increase your costs over on-prem versus cloud."