Netherlands: Software

Introductie van Micorosoft SQL Server 2016

Issue link: http://hub-nl.insight.com/i/692679

Contents of this Issue

Navigation

Page 184 of 212

172 C H A P T E R 8 | Improved Azure SQL Database Shard elasticity This feature dynamically adjusts the allocated resources to accommodate the current workload, whether horizontal scaling of many shards or vertical scaling of individual shards is necessary. When your application no longer needs the additional resources, the database shrinks back to its normal state. Split-Merge service The Split-Merge service makes it easier to split and merge data across shards. You use it to manage scale-out and scale-in by adding and removing databases from your set of databases (known as your shard set) and redistributing the data afterward. A typical scenario is a single database supporting multiple tenants with widely varying workloads that begin to overwhelm the available resources. You can use Split-Merge to redistribute the data into new or less utilized shards when demand is higher, or you can merge the data again when it is possible to reduce the size of the shard set when demand is lower. This service includes shard map management and data-dependent routing. Managing performance levels in elastic database pools As we described earlier in this chapter, SQL Database performance is measured in DTUs. Choosing the appropriate service tier and performance level for a multitenant environment with widely varying performance requirements can be a challenge and costly if you overprovision a SQL Database. To address this challenge, you can use an elastic database pool to share a pool of DTUs across multiple SQL Databases. That way, each database gets the necessary resources on demand. To configure an elastic database pool in the Azure Management Portal, navigate to the server blade and click the New Pool button at the top of the blade. In the Elastic Database Pool blade, assign a name, select a pricing tier (Basic, Standard, or Premium, similar to service tiers for SQL Database), and click Configure Pool to open a new blade in which you click the Add Database button to display a list of databases that you can add to the pool. The Configure Pool blade allows you to specify the maximum eDTUs (the DTUs for an elastic pool) and maximum storage capacity for the pool. Once you add a database to the pool, its resource usage adjusts dynamically to demand and supports bursting so that you no longer need to manage the performance level of that database individually. You can monitor and manage the elastic database pool settings in the Azure Management Portal by navigating to the server blade and clicking the name of the elastic database pool. The elastic database pool's blade displays summary charts and metrics. In addition, you can view and adjust the elastic database pool's settings by clicking the Configure Pool button in the elastic database pool blade to open the Configure Performance blade, shown in Figure 8-8.

Articles in this issue

Archives of this issue

view archives of Netherlands: Software - Introductie van Micorosoft SQL Server 2016