Excellent effort Br. Muhammad for the step by step details to configure High Availability feature on SQL2019. There is some audio disturbance that started towards the end.
you all probably dont give a shit but does anyone know a way to get back into an instagram account?? I was dumb forgot my password. I appreciate any help you can offer me!
@Crosby Malcolm Thanks so much for your reply. I found the site through google and im trying it out atm. Takes a while so I will reply here later with my results.
The shared folder that is created. What exactly is that used for? Can it be created on any of the SQL nodes? But is that node goes down, what would be the impact?
Hey Muhammad, nice video! Quick question, why does the database on the secondary replica stay in restoring mode? I noticed that happened in your example and the same thing happened to me as well
@@shehzadarshad2000 I will go through it. I did realize that I had to change something in the AG wizard and it reset my database to manual failover and asynchronous so I believe it restored with norecovery. I was able to get it working though. Thank you
While trying to configure always on, cluster type drop down showing only two options 1.External 2.None. The windows failover cluster is not showing in the list. Why it is coming like , can u help to solve the issue.
Inglés I am very grateful for the video, but despite doing absolutely and to the millimeter everything you do in the video, there is something wrong with me, let me explain. I create the availability group with the wizard and when I get to the end, it does it for you, but it doesn't do the Join 'test1' to availability gorup 'SQLGA' on 'Node2' check, but it does it for me and it stays like this, waiting and waiting... (I indicate that the ports are enabled and that from the management studio, I see from both nodes, to the other node. Also, since the wizard does not end, in the replicas tab, node 1 is with the replication symbol and node 2 is with a red X. Any help?
When adding replica, I am getting "Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement."
Brother, thanks for an explanation but I've followed all your steps but when creating AAG it shows the connection to the primary replica is not active. the command cannot be processed error 35250, do you have any solution
@@sayedsabirhasan Walykoumalsalam, I was disabling the firwall, you know what was the issue? I mad a cluster for VM and physical PC, so, since they are on the same subnet and firwall disabled on both nodes but unable to telnet 1433 from physical to VM, I provisioned new VM insted of physical and it works fine.
Very bad decision to change SQL Server service logon account from Services Control Manager, you need to do it from SQL Server Configuration Manager for SQL Server to assign required privileges for this account to work properly
Required to setup a SCCM Always available group DB. Watched this and completed in no time. Great.
That was an epic tutorial. Imagine i tried it using Windows Server 2022 and SQLServer 2022 and was successful.
Very nice۔۔۔informative ۔❤❤❤
Thanks very informative...one question, Is the listener HA ?
Great teacher my mentor. ❤
Excellent MR Muhammad, thank you
Ur welcome
Short-Simple and awesome... Keep it up!!!
Please upload some videos about replication and log shipping and how interview questions will be ask on these topics
Excellent effort Br. Muhammad for the step by step details to configure High Availability feature on SQL2019.
There is some audio disturbance that started towards the end.
you all probably dont give a shit but does anyone know a way to get back into an instagram account??
I was dumb forgot my password. I appreciate any help you can offer me!
@Ryan Esteban instablaster =)
@Crosby Malcolm Thanks so much for your reply. I found the site through google and im trying it out atm.
Takes a while so I will reply here later with my results.
@Crosby Malcolm It worked and I actually got access to my account again. I am so happy!
Thanks so much you saved my ass :D
@Ryan Esteban glad I could help xD
in the video Active Dir what's the purpose of the folder that you put the SQl servers in...
Vishuna u can deploy GPO or cyber security control on that folder.
is Doman must for Always on ? or can Always on be configured without domain ?
Hey man, nice basic video. Please in the future; Take care of security as well. You are granting computer objects full control on OU.
Sure bro appreciated for the advice
appreciate bro, very well. but here you are using donain admin account , in production is it good practice
جزاك الله خير
Excellent Muhammad !! Thanks alot
Ur welcome
@@shehzadarshad2000 Notice that if you setup using Sql Standard you are able to select 1 DB per AG-group
Enterprise more than 1DB per ag group
The shared folder that is created. What exactly is that used for? Can it be created on any of the SQL nodes? But is that node goes down, what would be the impact?
shared folder is acting like quorum disk , as a best practice it always be other than cluster node. It helps in voting.
Thanks for the help. Can the shared folder be removed after the availability group is set up or must it remain to continue the syncing functionality?
Killhha did you ever get an answer to your question?
Fantastic video! Thank you
Thanks bro Ur welcome
Hey Muhammad, nice video! Quick question, why does the database on the secondary replica stay in restoring mode? I noticed that happened in your example and the same thing happened to me as well
ruclips.net/video/c9E0cpY2k1I/видео.html
Kindly go through the next video I have pasted the link mostly the issue is with sql agent service double check if it is running
@@shehzadarshad2000 I will go through it. I did realize that I had to change something in the AG wizard and it reset my database to manual failover and asynchronous so I believe it restored with norecovery. I was able to get it working though. Thank you
Please do video about what is features will be add 2000 to 2019 versions
which ip we have added in connection string on web. conf file
While trying to configure always on, cluster type drop down showing only two options 1.External 2.None. The windows failover cluster is not showing in the list. Why it is coming like , can u help to solve the issue.
Hi Jagadeesh did you install the windows failover feature kindly install it first and then try hopefully it will resolve the issue
Inglés
I am very grateful for the video, but despite doing absolutely and to the millimeter everything you do in the video, there is something wrong with me, let me explain.
I create the availability group with the wizard and when I get to the end, it does it for you, but it doesn't do the Join 'test1' to availability gorup 'SQLGA' on 'Node2' check, but it does it for me and it stays like this, waiting and waiting... (I indicate that the ports are enabled and that from the management studio, I see from both nodes, to the other node.
Also, since the wizard does not end, in the replicas tab, node 1 is with the replication symbol and node 2 is with a red X.
Any help?
So these are some ways of HA in sql [Failover Cluster, Availability Groups, transactional replication] am I right?
why do you need to grant connect SQL explicitly to domain account where it is already sys admin ?
So nice sir this is really helpful
Ur welcome bro
Excellent Video !
Thanks
Just to Clarify I am pointing My SQL Clients to the ag-listener and not the WSQLCL Windows Cluster Name or IP? Or can I do both?
Yes u have to point the clients to the listener u can use name or ip any.
sUPER!
When adding replica, I am getting "Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement."
Thanks for the demo and info, have a great day
upload some work on managed instance with Microsoft Azure please
you can not set an domain admin in a windows service
Thanks my brother, but is this Active/passive or not?
Yes it is
Like. Thanks
Your welcome
Brother, thanks for an explanation but I've followed all your steps but when creating AAG it shows the connection to the primary replica is not active. the command cannot be processed error 35250, do you have any solution
Assalamu alaikum brother. Did you configure windows firewall? I mean did you create inbound fire wall rule on sindows?
@@sayedsabirhasan Walykoumalsalam, I was disabling the firwall, you know what was the issue? I mad a cluster for VM and physical PC, so, since they are on the same subnet and firwall disabled on both nodes but unable to telnet 1433 from physical to VM, I provisioned new VM insted of physical and it works fine.
@@alcolenol In that case I cannot guess anything else. Usually in production, the most common blocker is the firewall as we cannot turn it off.
Is the primary sql always writing to the secondary?
Yes
@@shehzadarshad2000 Thank you very much!
Very bad decision to change SQL Server service logon account from Services Control Manager, you need to do it from SQL Server Configuration Manager for SQL Server to assign required privileges for this account to work properly