Amazon Keyspaces vs. Azure SQL Database

Your upcoming app can be built faster on a fully managed SQL database and can be moved into Azure with a few to no application code changes. Flexible and responsive server less computing and Hyperscale storage can cope with your changing requirements and one of the main benefits is the reduction in costs, which is noticeable.

Incentivized

• Scalability is #1: if it used to be an almost no-win endeavour to try to modernize your server or migrate to other hardware, with Azure SQL Database it becomes a press of a button.
• All the tools simply work after you are on Azure SQL Database.
• The applications do not need changes in order to start using Azure SQL Database.
• Hybrid Cloud scenarios will work.
• Clustering and failover - already there.
• You can start monitoring the use and extract performance insights in a new way in Azure.

Incentivized

• A little slow on processing complex or large Views. We use a lot of Views to feed our BI system, and the processing time could see some improvement, IMHO.
• Additional monitoring components would be nice too, automating some built in performance measurement tools would be a nice feature.
• Price can always be improved as well. It’s not bad, but room for improvement.

Incentivized

This is best solution as a DBA one could expect from a service provider and as a cloud service, it removes all your hassles.

Incentivized

The interfaces are intuitive once you are familiar with all the functions. The ability to use different tools to interact with the platform, such as directly via a browser or code editors such as VS Code or Visual Studio is a great option and allows for integrating withn the project and other testing and developing tools.

Incentivized

We give the support a high rating simply because every time we've had issues or questions, representatives were in contact with us quickly. Without fail, our issues/questions were handled in a timely matter. That kind of response is integral when client data integrity and availability is in question. There is also a wealth of documentation for resolving issues on your own.

Incentivized

I selected Azure SQL because it integrates nicely with the technology stacks we currently maintain. The pricing is right, and clients are happy with that. Scaling is easy. Most of our clients don't want to maintain a full-blown database server, and they don't need one. For them, Azure SQL is the right size.

Incentivized

• Positive: very easy implementation!
• Positive: finally a good (easy) implementation of data masking, something we always neglected on premise.
• Positive: no maintenance!! No "server is down" messages on your phone at 3 'o clock in the morning.
• Negative: Too expensive to use for all other scenario's than a few very important applications.

Incentivized