Managed instances in azure sql database offer only


Managed Instances
in Azure SQL Database offer only the vCore-based
purchasing model.
DTU and eDTU
The performance of SQL Database is based on DTU.
According to Microsoft, a DTU is a unit of measure of the resources that are
guaranteed to be available to a single Azure SQL Database at a specific
performance level within a single database tier. A DTU combines CPU,
memory, data I/O, and transaction I/O.
 Databases can be placed into an
elastic pool
on a SQL Database server
that shares a pool of resources among those databases. The shared pool of
resources are measured by
elastic Database transition units
(eDTU)
.
 The advantages of an elastic pool are:
o They are scaled automatically.
o They provide predictable costs.
 They are widely used for
varying
and
unpredictable usage patterns
.
Determining DTUs for Workloads

If you are planning to move your on-premises Databases to Azure SQL
Database, Azure provides a DTU Calculator to find the approximate DTUs
required for setting up the database.

For an existing Azure Database, you can use SQL Data query performance
insight . This Query performance insight provides a deeper insight into the
resource consumption (DTU's) of Database, the top queries by
CPU/Duration/Execution count, which can potentially be tuned for improved
performance.
1. To create a MySQL Database with given charset and collation rules
az mysql db create --resource-group testgroup --server-name testsvr --name
testdb --charset {valid_charset} --collation {valid_collation}
2. To delete a DB:
az mysql db delete -g testgroup -s testsvr -n testdb
3. List all DB in a server:

4. To show an existing Db:
az mysql db show -g testgroup -s testsvr -n testdb
You can find more useful commands at Azure CLI docs.
How do you distribute your content to the users who are far away from the
Availability zone without latency? Check that out.
CDN Workflow
You have seen what CDN is and how to set it up. But how does it work? Let's
find out.
1. A user (John) requests a file (file1) using a URL,
<endpointname>.azureedge.net.
2. DNS routes the request to the POP location, which is geographically closest
to the user.
3. Now, consider that the edge servers does not have the requested file in their
cache memory, then it requests the needed file from the
origin
.