The following table summarizes distinctions between the serverless compute tier and the provisioned compute tier: Multiple databases with intermittent, unpredictable usage patterns that can be consolidated into elastic pools for better price-performance optimization.Databases that cannot tolerate performance trade-offs resulting from more frequent memory trimming or delays in resuming from a paused state.Single databases with more regular, predictable usage patterns and higher average compute utilization over time.Scenarios well suited for provisioned compute New single databases without usage history where compute sizing is difficult or not possible to estimate prior to deployment in SQL Database.Single databases in the provisioned compute tier that are frequently rescaled and customers who prefer to delegate compute rescaling to the service.Single databases with intermittent, unpredictable usage patterns interspersed with periods of inactivity, and lower average compute utilization over time.Scenarios well suited for serverless compute In contrast, the provisioned compute tier is price-performance optimized for single databases or multiple databases in elastic pools with higher average usage that cannot afford any delay in compute warm-up. Serverless is price-performance optimized for single databases with intermittent, unpredictable usage patterns that can afford some delay in compute warm-up after idle usage periods. The storage cost is determined in the same way as in the provisioned compute tier.įor more cost details, see Billing.When the database is paused, the compute cost is zero and only storage costs are incurred.When compute usage is below the min limits configured, the compute cost is based on the min vCores and min memory configured.When compute usage is between the min and max limits configured, the compute cost is based on vCore and memory used.The cost for a serverless database is the summation of the compute cost and storage cost.Alternatively, automatic pausing can be disabled. The database is automatically resumed when the next login or other activity occurs.
The auto-pause delay is a configurable parameter that defines the period of time the database must be inactive before it is automatically paused.Memory and IO limits are proportional to the vCore range specified. The minimum vCores and maximum vCores are configurable parameters that define the range of compute capacity available for the database.The configuration of these parameters shapes the database performance experience and compute cost.
The serverless compute tier for single databases in Azure SQL Database is parameterized by a compute autoscaling range and an auto-pause delay. The serverless compute tier also automatically pauses databases during inactive periods when only storage is billed and automatically resumes databases when activity returns. Serverless is a compute tier for single databases in Azure SQL Database that automatically scales compute based on workload demand and bills for the amount of compute used per second.
0 kommentar(er)
