Video

This one www.udemy.com/course/sqlserverhadrdeepdive However, just because you can follow a video tutorial doesn't mean you'll be able to implement it properly. Building a SQL Server failover clustered instance requires properly configuring every layer in the stack - servers, VMs (if you're running virtual machines), storage, networking, Active Directory, DNS, failover clustering, and SQL Server. One misconfiguration is all it takes to cause an extended outage.

Wolfpac with Sphinx, for those who still remember the codenames 🙂 The principles and concepts remain the same...despite all the hype of whatever is new in the industry

This happens 🙂 czcams.com/video/BSS4G087UeM/video.html I used this example to demonstrate the effects of tlogs growing and getting full until it can no longer do so. The application may throw an error that doesn't explicitly tell you it's a SQL Server problem.

@@EdwinMSarmiento what can be done to reduce the size of it in this case?

@@AnandNarine Monitor and take precautionary measures to make sure the tlog files do not grow to a size that fills up the disk. That really is all there is to it.

The link should be on the description learnsqlserverhadr.com/clusterprepchecklist

> Can SQL cluster work on a workgroup environment instead of an Active Directory environment? If you're referring to a SQL Server failover clustered instances, it's not supported. Only SQL Server Always On Availability Groups work with workgroup clusters as of SQL Server 2022. Here's a video on how to install and configure a Windows Server Failover Cluster without Active Directory czcams.com/video/jDvqP1372Lo/video.html

@@EdwinMSarmiento Thank you very much for the reply.

I do not recommend the node drain feature for SQL Server. It wasn't designed with SQL Server in mind. It's for Hyper-V workloads

Have a look at this czcams.com/video/DmH81mGGZwg/video.html

@@EdwinMSarmiento can you make a video on how to configure the on always on high availability and it failover. What is the different between the normal HA and the always on HA, thanks.

@@jeffreyooi1971 Are you referring to this? czcams.com/video/A8lSl8nO1r4/video.html

@@EdwinMSarmiento is it the same configuration or setting apply to SQL server 2022 too as the video is 12 years ago, thanks.

@@jeffreyooi1971 There have been a lot of configuration changes since SQL Server 2012. And these subtle changes can cause a major outage if not done properly. I'll release an updated video on installing and configuring SQL Server Always On Availability Groups

> why use dns and not edit a hosts file Scalability. When you have more than 2 nodes to manage, you have to think of how you can do more with less.

Thanks

My responses below: 1) Why do you need to run Always On Availability Groups on Docker containers? 2) Yes 3) Same as #1, why do you need it to be on Docker containers? 4) Same as #1, why do you need it to be on Docker containers?

@@EdwinMSarmiento it should be the cheapest way to have HA is terms of resource. containers are easy, but unless you are using shared storage to start up a new host you will have data loss. Plus, I just wanted to know if it's possible. With AG the data should stay synced, that way you don't have to worry about the container if one goes down, just auto start a new one & sync the data.

@@fbifido2 What are your HA goals? RPO? RTO? It is possible to do what you want. But without having a clear HA goal - RPO/RTO/SLA + the apps connecting to the DB - what's the point? Start with defining the goal as clearly as you possibly can

Check your email 🙂

This is typically a side effect of not being clear on the goal and not understanding the capabilities and limitations of the technology. There are more disadvantages over advantages of having a synchronous replica on a DR site. At the end of the day, they're all irrelevant unless the goal is well defined.

Have a look at the Database Mirroring articles here: www.mssqltips.com/sql-server-tip-category/64/database-mirroring/

In large organizations, there are different specialized teams (silos) that deal with specific areas of the infrastructure - sysadmins/server admins take care of the server/OS, network admins take care of anything related to the network, and DBAs take care of database-specific tasks. So, when deploying a complex solution like SQL Server Always On Availability Groups, there will be multiple teams working together to deploy it in production. However, not every team knows how all the pieces of the solution fit together.

You need to understand why organizations implement Active Directory in the first place. They want a centralized directory service to allow connecting users with network services. Security is just one aspect of Active Directory. So, when companies decide they don't want to use Active Directory, they must have a valid reason for doing so.

Glad you liked it!

You're very welcome

I reached out to StreamYard and asked about it. It's more than just a mic issue as I'm using a high-end mic system.

Having the tempdb in the local drive is just an option. Most people still store the tempdb on shared storage for failover clustered instance deployments.

This requires more than a simple response on a comment. There are so many things going on in a multi-subnet cluster configuration to identify what exactly is preventing this

The Windows NLB cluster is in itself the load balancer. It serves both purposes - load balancing and high availability. It's unlike the typical network load balanced appliance where it only provides load balancing.