liveBook · Manning

Service tier

As explained in Microsoft Azure in Action

A service tier is a selectable database performance level that determines available capacity and related service characteristics.

A service tier is a selectable Azure SQL Database performance level: in plain English, it answers “how much compute power do you need?” Higher tiers provide more capacity but cost more. section 10.3.1 section 10.5.1

Choose a tier with these practical trade-offs in mind:

  • Start with Basic for experiments or nonproduction examples when modest capacity is enough. section 10.3.1
  • Expect higher tiers to increase spending as performance requirements rise. section 10.3.1
  • Keep replicated databases at the same or a compatible performance level so a secondary can handle failover load. section 10.5.1

Creating a Basic database

The Azure CLI selects the tier through the service-objective parameter: az sql db create --resource-group BanningRG --server BanningBooksServer --name BanningBooksDB --service-objective Basic. The same Basic objective can be specified when creating a geo-replica.

How Microsoft Azure in Action covers it

How deep it goes
Defines tiers as compute or DTU-based performance levels, but does not detail the complete tier catalog.
Examples
Uses Basic for database creation and geo-replication, alongside performance, scaling, and cost comparisons.
What it assumes
Assumes familiarity with Azure SQL servers, databases, replicas, and basic Azure CLI command structure.
What you can do after
Operate Azure SQL databases by selecting a service objective and matching replica performance.
How it connects
Connects service tiers with Azure SQL Database, geo-replication, failover, DTUs, compute, and cost.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microsoft Azure in Action. The section links point to the parts of the book it draws on.