>> In this video, we're going to take a look at failover times
and comparing them between general purpose and business critical.
We've got a lot of stuff going on here,
I just want to take a moment and explain what you're looking at.
On the left side of the screen,
you're seeing things related to a general-purpose database and on
the right side of the screen you're seeing things
related to a business critical database.
You'll see I've got a PowerShell notebook for each in
Azure Data Studio and I also have
the PowerShell command line open.
What I'm going to do is I'm going to kick off
a workload and the workload is here.
Bob taught me how to use OStress in ARM,
using it left and right and three times on a screen.
What we're doing is, we're selecting account from a table,
just trying to see, can we connect to this database?
When we initiate a failover,
we'll be able to log,
are we able to connect to a database?
I'm just running this once on one thread but 50,000 times,
so this will run for a while and this is my general purpose.
Over here, I'm doing the same exact thing,
except it's running on a business critical database,
you'll see here at the end and I'm
putting it to a business critical folder,
left is general purpose,
right is business critical.
I've configured all these variables to be
set up and what we're going to do is we're going
to invoke a failover for our general-purpose database,
and we're also going to invoke
a failover for our business critical database.
This is like we're trying to force a failover to
see how long it takes for us to recover.
Anytime you don't see this 847 coming,
that means we're disconnected.
What I'm going to do is I'm going to kick off each of these at
approximately the same time and we'll
be able to monitor what happens.
Let me just kick it off, what you can see is,
for now I can still connect,
but then there will be a brief time.
You can see the business critical database,
I was not able to connect much sooner
and then hopefully in a matter of
seconds you can see that business critical,
I'm already back and running just a matter of seconds whereas
general purpose is still doing that failover process.
Again, this is because they
are always on availability group that you see,
and business critical allows you to failover very quickly,
because it's just a matter
of changing the points you have to one of
your secondaries and then in
the back-end spinning up another secondary.
We can see the general purpose one still takes less than,
I think probably less than 20 seconds,
but you-all witness how quickly
that business critical failover occurred.
These notebooks are available to you,
we'll share references on how to get access to them.
Definitely, try it out and see what it's like for you.
One other thing I wanted to call out is just that we
cannot invoke a failover again within a 30 minute period.
Basically, I'm only doing this on the general purpose database,
but what we're going to get is essentially a failure saying, "Hey,
you are not able to failover in this time".
What we see here is long running operation failed,
and like I said,
it's just because 30 minutes must pass
between forced database failovers.
In this demo, you saw
how fast failovers are in general purpose and business critical,
but you also saw how much faster,
and with that comes
a higher availability that you get
with the business critical service tier.
See you in the next video.
>> Anna, that was awesome.
I still think that's a pretty cool demo of it.