>> We've seen the availability architectures
for all of our service tiers,
but there's a few more things to consider,
such as Azure SQL Zone redundancy and the SLA that we provide.
Now, if we start with zone redundant configuration,
what you're seeing on the right is
the business critical architecture but setup for zone redundancy.
Now, today, this is only available
in business critical service tier and it's also free.
To enable it, it's really just a toggle of a button in the portal.
Let's take a look at what's different between
this and just what you saw
before for the business critical architecture.
What you're seeing on the right is you see three AZs,
AZ 1, AZ 2, and AZ 3.
AZ 1, that stands for an availability zones.
What this basically means is in a region,
there are multiple availability zones.
Think of it as a different campus in a same region or
different building in the same region so you're able to
separate your replicas from disaster recovery standpoint.
If something goes out in one datacenter,
you're not left without anything because
your replicas are spread across these three availability zones.
Now you might be wondering, "Okay,
what do I have to set up to do this?"
Because you see Azure Traffic Manager.
But the great news is similar to a gateway,
Azure Traffic Manager is actually going to
be the one that points you to the different zones.
Then the gateway, in order to get
that information to do the redirect proxy connection,
very similar to how you saw in business critical before.
Zone redundancy is a great way to get
that extra level of availability.
But one thing to consider is that if you have
really latency-sensitive OLTP applications,
you might want to make sure this is a good fit for you
because that sync to a secondary still less occur.
>> That was part of our availability story for Azure SQL.
Anna just show you how to go further with zone redundancy,
is a service level agreement.
This is actually a contract we have with you as you
sign up for subscription for Azure SQL deployments.
We make guarantees for the availability of your deployments.
If we violate these agreements,
there's actually Azure Service credits
involved back to your subscription,
your billing as part of the series,
so we have a big incentive to make sure
that we keep you highly available.
You can see here on the left-hand side in service tiers
various different SLAs thought of in terms of nines.
You probably heard this term before about nines or half nines.
You can see here, depending if you picked on
general purpose or business critical or even Hyperscale options,
the different nines of uptime that we guarantee their SLAs.
If you've seen this before in the industry, for example,
a four nine scenario results into little under
an hour total of downtime throughout a calendar year.
But notice here that if you go further like with
Anna talked about was zones and business critical,
we can give you four-and-a-half nines,
which is almost like
about 28 minutes or so of downtime an entire year.
That's an amazing story and industry
leading here for Azure SQL in the space.
Now, the right-hand side, we talked about continuity.
We're the only database vendor out there actually giving
SLAs on recovery point objectives,
on getting your data from any data-loss scenario,
and recovery time objectives for the time it
takes to get back in business critical,
gives you these different SLAs of RPO and RTO.
We showed you built an availability for the different tiers.
If you want go further for availability,
Anna talked about zone redundancy with
availability zones in the business critical space,
and we also talked about
the different service level agreements we give
you from perspective of either four nines, four-and-a-half nines,
and even RPO and RTO objectives,
another great story about
the built-in availability capabilities of Azure SQL.
We'll see you in the next video.