SQL Server Always On Availability Groups 101

00:00 Start
00:24 Paul Hunter: My company decided to move to AZURE. The person in charge of moving the SQL Server decided to put up an AG (I voiced my concerns over management of an AG). Now I am going to be in charge of managing an AG. Do you have any advice on how to quickly learn to manage an AG?
30:14 Bandhu: What's the max number of DB's you would not exceed for a single AG?
33:59 Dopinder: What is the top issue you see with clients running SQL Server AG?
35:29 Bandhu: Is there a good way to determine which databases a given app connects to (for the purpose of designing AG's)?

[anuragkumar-dmer]

Loved this version. Just talking about 1 topic at a time ❤

[utenatenjou]

I'm an old dog, and I do agree about trust-ability of shared storage solution (with disk layer replication).
What I afraid with shared-nothing topology (each has it own disk) is the old wisdom of "shared nothing = replicate everything".
Documentation mostly focus on fail-over event, but recovering primary side back is lacking, the re-sync, re-electing master node. I hope, I'd reach my retirement before I have to deal with it, thanks for the content, I do enjoy it.

[Bill_N_ATX]

I 100% agree with the biggest issue with Always On is the availability of good, or actually any, management and troubleshooting tools. All it has out of the box is a simple dashboard that tells you little. Instead it requires you know a bunch of queries and have the ability to understand and respond to the queries and what to do with the information. Not easy.

[PauliPorkka]

I havent had the pleasure(?) To work with sql servers for couple of years, transitioned to other stuff, but I still enjoy listening your videos. Just because how you explain things, thanks Brent.

[wensday]

Informative, interesting and entertaining as always, thanks Brent 🙂

[nofreenamestoreg]

Just a side node, moving from shared storage was not due to expensive replication of the storage. It was due to VMs and having a nightmare with things like iSCSI. Having attached storage directly to a VM means you cannot use snapshots "properly", full VM backup/restore or great features like vMontion. To use the best features of virtualization, you need to have only VMDK-s :D Please, feel free to correct me, if I am wrong.

[rebornfenix]

3:04 I thought the painting was Ron Perlman riffing on his role in Sons of Anarchy

[marcscirri]

It sounds like if you want your system to stay on during deployments, shared storage is out of the question. Are there any 3rd party solutions that offer what Always-On Availability Groups offers but with less management headaches?

[FlaggedStar]

26:35 Brent often talks about SAN, e.g. SAN backups and SAN replication. What's the AWS equivalent?