>> Welcome back.
Hope you joined us in the first Azure SQL scenario challenge,
where we showed Bob something he hadn't seen before
and let him take a stop at a solution on the fly.
I think he did okay, but we encourage
you to participate and we have
another scenario which is equally
interesting and also one that Bob has not seen yet.
So let's see how that goes.
So this next scenario is about a mission critical app
and the hashtag for this one is azuresqlcritical1.
Just a reminder, if you didn't watch the last video,
we're doing a challenge here.
So basically, we encourage you to get on Twitter, get on LinkedIn,
get on the comments and let us
know what your proposed solution is,
whether it's with an image or some text or
some ideas and really you
can also critique whatever Bob comes up with.
Now granted, Bob hasn't seen this before and in the last video,
I gave him a hint, so I'm going to go
ahead and put that hint up there.
So Bob hopefully this gives you an idea of the situation,
maybe some of the highlighted things that I think are important.
>> Yeah, Anna. Thanks. Definitely I needed the hint
because I was trying to speed read as you were bringing this up.
Mission critical is my jam,
so I should be able to nail this, I think actually.
>> All right.
>> So I have this 99.995
availability and I was the one that did
the video on our SLAs for that,
which I believe you're only going to be able to
get that with availability zones.
You guys remember zone redundancy
as something we presented in this thing.
I remember it stuck in my head because I presented that slide.
So I know this one,
I need zone redundancy with availability zones,
I need to find regions that support that.
First of all, that's important, not all regions
support that, so I need to find that.
I believe business critical for Azure Database
is the one that you might pick to meet that need.
So I would probably do that.
Now, it's hard to say what
other redundancy and resilience they need for their goals here,
it's not really called out.
Probably, I might do an auto failover group,
like a geo-replication or auto-failover group,
but the key is this data sovereignty statement.
Now that I see that and just knowing
about the Azure ecosystem in regions,
I've got to make sure I pick whatever
my solution is that meet my sovereignty goals.
So if sovereignty requirements are in Europe,
I can only be doing,
let's say I'm doing auto-failover group for example,
I got to make sure that's within Europe or within
the data sovereignty requirements of my Azure regions at the US.
That's something that sticks out to me,
so I think I need business critical,
I need availability zones but I got to find
regions that meet that sovereignty needs.
So that can be looked up,
somebody could go maybe sketch
out a solution based on a sovereignty example.
That be fun if somebody would pick a sovereignty example and say,
"Hey, I did it."
So the second part is about
DBAs performing their job and protecting data.
So this is a separation of duties thing.
I can just see, the DBAs not see sensitive data.
Now, dynamic data masking could do that
because I have control over
who the DBA is and what permissions I give them.
So I could use dynamic data masking for
that one stored in specific columns.
Yeah, I would probably pick that one, so then I would be,
maybe my sys admin or Uber DBA and I would give other DBAs,
I wouldn't give them access to dynamic data masking rules.
So I would only see it,
so I'd probably do that.
Then the troubleshooting one is interesting.
DBAs need to troubleshoot performance for the portal.
Well, everybody has a portal subscription,
so I don't see any problem there,
they would just get access to the portal.
Then in SSMS, they just have access already,
so that's no big deal.
Creating new database users who must be mapped to 80 principles.
So when we talked about deployment,
even though you can do a contained database in MI,
just like a SQL Server,
the Azure SQL model already gives you this containment idea,
the way you can map to an Azure Directory login.
So I would pick
an Azure Database solution overall with business critical,
with availability zones, with dynamic data masking,
and then I would just used this
contained user authentication methods.
Something could have been that one up, how did I do?
>> Yeah, I think it was pretty good.
Again for just seeing this,
I think you called out a lot of the important things.
There are a few more things and
maybe a few things that someone might choose to do differently.
So again, if you're watching this,
we encourage you to get on Twitter, LinkedIn,
in the comments, let us know what you think,
let us know what you think Bob did right,
and let us know what you think
maybe Bob could have done a little bit differently.
We hope this is as fun for you guys as it
is for us and stay tuned for the next video.