{"id":14780,"date":"2020-08-01T10:50:06","date_gmt":"2020-08-01T10:50:06","guid":{"rendered":"https:\/\/www.testpreptraining.com\/tutorial\/?page_id=14780"},"modified":"2022-04-04T10:08:45","modified_gmt":"2022-04-04T10:08:45","slug":"service-tiers-in-the-dtu-based-purchase-model-for-sizing","status":"publish","type":"page","link":"https:\/\/www.testpreptraining.ai\/tutorial\/service-tiers-in-the-dtu-based-purchase-model-for-sizing\/","title":{"rendered":"Service tiers in the DTU-based purchase model for Sizing"},"content":{"rendered":"\n

Go back to AZ-304 Tutorials<\/a><\/p>\n\n\n\n

AZ-304: Microsoft Azure Architect Design is retired.\u00a0AZ-305<\/a>\u00a0replacement is available.<\/strong><\/h3>\n\n\n\n

In this, we’ll understand and learn about the service tiers in the DTU purchase model by a range of computing sizes with a fixed amount of included storage, the retention period for backups, and price. You will know that all service tiers in the DTU-based purchase model provide the flexibility of changing compute sizes with minimal downtime.<\/p>\n\n\n\n

Comparing the DTU-based service tiers<\/strong><\/h4>\n\n\n\n

Choosing a service tier depends on business continuity, storage, and performance requirements.<\/p>\n\n\n\n

\"DTU
Image Source: Microsoft<\/figcaption><\/figure><\/div>\n\n\n\n

Single database DTU and storage limits<\/strong><\/h4>\n\n\n\n

Compute sizes are Database Transaction Units for single databases and elastic Database Transaction Units for elastic pools. <\/p>\n\n\n\n

\"Single
Image Source: Microsoft<\/figcaption><\/figure><\/div>\n\n\n\n

Elastic pool eDTU, storage, and pooled database limits<\/strong><\/h4>\n\n\n\n
\"Elastic
Image Source: Microsoft<\/figcaption><\/figure><\/div>\n\n\n\n

DTU Benchmark<\/strong><\/h3>\n\n\n\n

Physical characteristics (CPU, memory, IO) are in association with each DTU measure calibration is using a benchmark that simulates real-world database workload.<\/p>\n\n\n\n

\"AZ-304<\/a><\/figure><\/div>\n\n\n\n

Correlating benchmark results to real world database performance<\/strong><\/h4>\n\n\n\n

You should understand that all benchmarks are representative and indicative only. However, the transaction rates achieved with the benchmark application will not be the same as those that might be achieved with other applications. The benchmark comprises a collection of different transaction types running against a schema containing a range of tables and data types. But, the goal of the benchmark is to provide a reasonable guide for the relative performance of a database while scaling up or down between compute sizes. <\/p>\n\n\n\n

Schema<\/strong><\/h4>\n\n\n\n

The schema provides variety and complexity for supporting a broad range of operations. However, the benchmark runs against a database of six tables in which these tables fall into three categories such as fixed-size, scaling, and growing. And, there are two fixed-size tables, three scaling tables, and one growing table. In which, the Fixed-size tables have a constant number of rows, scaling tables have a cardinality that is proportional to database performance. Lastly, the growing table is sized like a scaling table on initial load. But, the cardinality changes in the course of running the benchmark as rows are inserted and deleted.<\/p>\n\n\n\n

Further, the schema includes a mix of data types, including integer, numeric, character, and date\/time including primary and secondary keys, but not any foreign keys.<\/p>\n\n\n\n

Transactions<\/strong><\/h4>\n\n\n\n

There are nine transactions in workloads that are designed for highlighting a particular set of system characteristics in the database engine and system hardware.<\/p>\n\n\n\n

\"Transactions\"
Image Source: Microsoft<\/figcaption><\/figure><\/div>\n\n\n\n

Users and pacing<\/strong><\/h4>\n\n\n\n

The benchmark workload refers to a tool that submits transactions across a set of connections for simulating the behavior of a number of concurrent users. However, all of the connections and transaction generation is through machines. So, for simplicity, we refer to these connections as \u201cusers.\u201d And, each user operates independently of all other users, all users perform the same cycle of steps shown below:<\/p>\n\n\n\n