Microsoft SQL Server 2019 Always-ON Availability Group
HTML-код
- Опубликовано: 25 окт 2024
- How to Setup SQL Server 2019 Always ON AG Group on Windows 2019
Software's Used:
Microsoft SQL Server 2019
Microsoft Windows 2019
VMWare Workstation Pro 17
SSMS - SQL Server Management Studio
Awesome session !!!
In my case, there are 2 main servers (instance1,instance2) that perform FCI configuration, for HA(active-passive) purposes.
I want, add 1 machine (instance3), desire to configure Always-ON Availability Group between server cluster (instance1,instance2) and machine (instance3).
how i do the above case.
Build Failover Cluster Instance first. Then add third node and configure Always-ON AG Group.
You need to exactly follow the steps that you have mentioned in the same order.
Thank you!@@DB2_Oracle
Awesome Video
Hi, can we add any IP on the listener? or you created it before setting up the AG?
We can add any IP for the listener as long as it is in the same subnet.
I did not create any IP before.
Please help! Have success with your tutorial install failover cluster, but when I follow this tut, I cant connect to Db engine from Win19Dc , but when I install sql server, at step add current user, I click and it add auto user administrator, I must remove it, and add manual with user sqlsa! Please help, i dont know where my problem! Do I need open port sql server ?
Its your choice, where you add current user, you must be logged in as ADMINISTRATOR and not SQLSA. And hence its adding ADMINISTRATOR.
You can leave that and add SQLSA. You can have multiple users there.
Or you can create new user at the Active Directory and add that user.
@@DB2_Oracle but, I cant connect to db engine at win19node1 from win19dc, i dont know why! I think win19node1 dont open port
@@DB2_Oracle I have connected success, I have recheck, i was changed port to 1425 follow video! Would you mind if I ask, I currently have a running database with a very large size of around 1TB. Should I use Always-On Availability Group for my data? This is to ensure that if one server fails, there will be another server to take over and there won't be any delay in the connection. I apologize for this question, as the technology infrastructure where I work is still quite weak, and I have to self-study and upgrade. I hope you can help, thank you very much
You can use Always-On AG however I would suggest to use Microsoft SQL Server failover Cluster Technology which will suffice your purpose.
AG has some performance overhead which is not there in Failover Clustering.
@@DB2_Oracle thank bro for your idea, show I want ask, if use Microsoft SQL Server failover Cluster Technology , I must expand size DATA in íSCI ? and online for all NODE ? right ? I dont know it active how, your video dont have detail it, my english so bad :( ! sorry