1
00:00:01,340 --> 00:00:08,060
Okay, so let's sign in. Click Connect. We do this in an HTML5 way,

2
00:00:08,060 --> 00:00:12,450
although I understand that Bastion is gradually embracing

3
00:00:12,450 --> 00:00:15,550
client apps. I'm going to have to allow pop‑ups here for

4
00:00:15,550 --> 00:00:18,240
this to work. Try that again.

5
00:00:18,240 --> 00:00:19,400
Now that were signed in,

6
00:00:19,400 --> 00:00:23,550
this is obviously running a downlevel version of Windows Server,

7
00:00:23,550 --> 00:00:26,340
Windows Server 2012 R2, I believe.

8
00:00:26,340 --> 00:00:30,320
Let's open up SQL Server Management Studio, and we can see that my

9
00:00:30,320 --> 00:00:34,820
user database here is showing as synchronized. Whoops! I don't want

10
00:00:34,820 --> 00:00:39,570
updates right now. And then under Always On High Availability, we have

11
00:00:39,570 --> 00:00:43,060
our ‑‑‑ It looks like I'm actually connected to the secondary

12
00:00:43,060 --> 00:00:47,400
instance, but what I mainly wanted to show here is the Always On

13
00:00:47,400 --> 00:00:49,440
listener that we created,

14
00:00:49,440 --> 00:00:54,280
well, we didn't create, but I created. And if we look at its properties here,

15
00:00:54,280 --> 00:00:57,940
you'll notice again we have a mapping that I created manually

16
00:00:57,940 --> 00:01:06,210
to 10.0.1.9 and TCP 1433. That's it. We have to remember that

17
00:01:06,210 --> 00:01:08,350
AZ‑801 is not a SQL Server exam,

18
00:01:08,350 --> 00:01:12,270
so I've gone beyond what you can expect to see coverage of on

19
00:01:12,270 --> 00:01:16,740
this on the exam. But because this subject of floating IP and

20
00:01:16,740 --> 00:01:26,000
load balancing SQL Server does, in fact, tend to recur on quite a few of the Azure exams, I think this demo is pretty worth your while.