Virtual Machines (VMs) are available on Microsoft Azure, providing what is built as a low-cost, per-second compute service, available via Windows or Linux.
$0
Per Hour
Azure SQL Database
Score 8.4 out of 10
N/A
Azure SQL Database is Microsoft's relational database as a service (DBaaS).
$0.50
Per Hour
Pricing
Azure Virtual Machines
Azure SQL Database
Editions & Modules
3 Year Reserved - Burstable VMs - B1S
$0.0038
Per Hour
Spot - General Purpose - Av2
$0.005
Per Hour
1 Year Reserved - Burstable VMs - B1S
$0.0059
Per Hour
Pay as You Go - Burstable VMs - B1S
$0.0075
Per Hour
Spot - Compute Optimized - Fsv2
$0.0104
Per Hour
Spot - General Purpose - Dv3
$0.0125
Per Hour
Spot - Memory Optimized - Ev3
$0.016
Per Hour
3 Year Reserved - Compute Optimized - Fsv2
$0.0307
Per Hour
3 Year Reserved - General Purpose - Dv3
$0.0369
Per Hour
3 Year Reserved - Memory Optimized - Ev3
$0.0481
Per Hour
1 Year Reserved - Compute Optimized - Fsv2
$0.05
Per Hour
1 Year Reserved - General Purpose - Dv3
$0.0548
Per Hour
1 Year Reserved - Memory Optimized - Ev3
$0.0753
Per Hour
Pay as You Go - Compute Optimized - Fsv2
$0.0846
Per Hour
Pay as You Go - General Purpose - Dv3
$0.096
Per Hour
Pay as You Go - Memory Optimized - Ev3
$0.126
Per Hour
2 vCORE
$0.5044
Per Hour
6 vCORE
$1.5131
Per Hour
10 vCORE
$2.52
Per Hour
Offerings
Pricing Offerings
Azure Virtual Machines
Azure SQL Database
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Azure Virtual Machines
Azure SQL Database
Considered Both Products
Azure Virtual Machines
No answer on this topic
Azure SQL Database
Verified User
C-Level Executive
Chose Azure SQL Database
Amazon RDS for SQL Server is the best example to compare with Azure SQL Database since both provide a Microsoft SQL Engine to host your databases.
Amazon RDS for SQL is much more compatible with your on-premises databases than Azure SQL, the reason is that Amazon RDS for SQL …
If you want to host a dedicated Windows server on the cloud, and especially if you want to integrate it with your on premises Active Directory, Azure Virtual Machines should be your first choice. Obviously running Linux on Azure works very well too, but given Azure's pricing is not the cheapest, there are other providers out there that have a better cost-benefit ratio for Linux. That said, hosting Windows on Azure can be affordable (especially when compared to other providers) if you plan your licensing, topology, and application architecture correctly.
We have found it's a great alternative for making older legacy applications work with online databases instead of only on-premises databases. We've converted over a dozen applications this way, and it has allowed our clients to have a distributed workforce using their applications without incurring the expense of a complete application rewrite.
When demand is high, we scale the service out, eg During a Football Match.
When a football match is over and the throughput of data from OPTA drops we save by the service scaling back in.
Our App Service Plans along with the Clean C# code are lightening fast giving a good customer experience.
When producing the TV Guide information and a program overruns its scheduled time, a client can instantly be updated to the new programming schedule as our change is instant and its in the right place for all the clients to download and adjust their television guides appropriately to send out to the public giving a 24x7 uptime service that is precise and accurate and resilient to outages due to failover zones around the world.
Maintenance is always an issue, so using a cloud solution saves a lot of trouble.
On premise solutions always suffer from fragmented implementations here and there, where several "dba's" keep track of security and maintenance. With a cloud database it's much easier to keep a central overview.
Security options in SQL database are next level... data masking, hiding sensitive data where always neglected on premise, whereas you'll get this automatically in the cloud.
Pricing can be a concern if you are truly agnostic to which cloud you are building your particular solution in.
The UI, as is the case with any cloud provider, is crowded.
As with any cloud provider, it can be difficult to tune in exactly the right amount of servers for your needs...you might find yourself under/overprovisioning.
One needs to be aware that some T-SQL features are simply not available.
The programmatic access to server, trace flags, hardware from within Azure SQL Database is taken away (for a good reason).
No SQL Agent so your jobs need to be orchestrated differently.
The maximum concurrent logins maybe an unexpected problem.
Sudden disconnects.
The developers and admin must study the capacity and tier usage limits https://docs.microsoft.com/en-us/azure/azure-subscription-service-limits otherwise some errors or even transaction aborts never seen before can occur.
Only one Latin Collation choice.
There is no way to debug T-SQL ( a big drawback in my point of view).
No VM console, weak management interface, changing CPU/memory is not straightforward. On the positive side, basic RDP functionality is good to have. As long as things are working, the ability to host Windows VMs is appreciated.
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.
I give the overall support for Azure Virtual Machines a 7 because I think while the overall support do a great job there are still areas that it could improve on such as efficiency and speed. So while I only give it a 7 and it has some issues it is still better than the overall support at Amazon EC2 Auto Scaling.
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.
Azure Virtual Machines offer unparalleled flexibility in provisioning, managing and upgrading the VM instances, both manually and programmatically. AVM offer very granular billing options and enables high costs optimisations (while still being costly). The other competitors I mentioned are very good at offering dead-cheap VMs. But if you need anything beyond that, especially for big computing, you need Azure Virtual Machines.
We moved away from Oracle and NoSQL because we had been so reliant on them for the last 25 years, the pricing was too much and we were looking for a way to cut the cord. Snowflake is just too up in the air, feels like it is soon to be just another line item to add to your Azure subscription. Azure was just priced right, easy to migrate to and plenty of resources to hire to support/maintain it. Very easy to learn, too.
It's so easy to spin up new instances, that it becomes also to easy to have to many of them to manage. Many teams end up with a couple of hundreds of VMs after a short while, making the whole thing very hard to maneuver
Azure VMs are the next step for us to rely on Onprem servers, and leaving the management of the infrastructure to the professionals
The ease of use, is also important when our main focus is to deliver new applications and integrations fast, and not having to worry about infrastructure. We sell bottles, not CPUs