Updating mysql database
Pricing Azure SQL database is difficult because various database service tier options such as database transaction units (DTU’s), max database size, disaster recovery options, and backup retention days are used to determine pricing instead of hardware (CPU/RAM/HD).
Generally I recommend starting out with a low service tier and scaling as your needs increase as it only takes a few minutes to scale with no downtime (see Change the service tier and performance level (pricing tier) of a SQL database). To help, there is a Azure SQL Database DTU Calculator.
More info: Understanding Windows Azure Storage Billing – Bandwidth, Transactions, and Capacity Understand your bill for Microsoft Azure Azure SQL Database – How to choose the right service tier James is a big data and data warehousing solution architect at Microsoft.
Note this pricing is per database, so if you have many databases on each on-prem SQL server you will have to price each one.
But there are many “built-in” features of SQL database, such as high availability and disaster recovery, that you don’t have to build or manage in the cloud, thus saving you costs and administration time. You don’t pay for storage (but there is a database size limit for each tier).
A very simple example would be users (students) and course enrollments: ‘user’ table: This database is not efficient.
It’s fine for this example, but a student can only be enrolled on zero or one course.