Netherlands: Software

Introductie van Micorosoft SQL Server 2016

Issue link:

Contents of this Issue


Page 174 of 212

162 C H A P T E R 8 | Improved Azure SQL Database Note For deeper insight into your SQL Database performance, you can analyze dynamic management views (DMVs), Extended Events, or Query Performance Insight. Information about using these tools is available in "Azure SQL Database performance guidance for single databases" at Protecting data with high availability and disaster recovery SQL Database provides full-scale high availability and disaster recovery options that can support a variety of business needs. Regardless of service tier, every SQL Database is automatically protected with high availability in the event of hardware failure. When you create your SQL Database, you have at least three replicas of your database at any point in time, with one replica as a primary replica and the other two as secondary replicas. If the hardware hosting the primary replica fails, Azure automatically promotes one of the secondary replicas to primary and builds an additional secondary replica if necessary. For the Premium service tier, active geo-replication adds an additional layer of protection. Much like the Always On Availability Groups feature in on-premises SQL Server, active geo- replication supports up to four copies of your SQL Database on servers in separate Azure regions for the highest level of availability. Note Because these secondary copies are also readable and compatible with load balancing for read-only workloads, you can also use this feature as a scale-out option for your SQL Database. Whereas building an infrastructure to support a multisite on-premises SQL Server infrastructure can be a time-consuming proposition that requires extensive network configuration and multiple installations, configuring geo-replication for SQL Database takes minutes. If your database is in the Premium service tier, you have the option to configure multiple databases. In just a few minutes and a few clicks, you can configure multiple readable secondary copies of your database in multiple Azure regions. To do this, browse to your SQL Database, click the All Settings link in the database blade, and then click Geo-Replication in the Settings blade. In the Geo-Replication blade, select a target region. You can use any region for a Premium database, but you must use the recommended region for a Standard database. In the Create Secondary blade, you specify whether the secondary type is readable or nonreadable for a Premium database. A Standard database secondary can only be configured as nonreadable. You can optionally add a secondary database to an elastic database pool on this blade. When you click Create to add the secondary, the process to seed the secondary begins and its status is shown in the Geo-Replication blade, as shown in Figure 8-2.

Articles in this issue

Links on this page

Archives of this issue

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