How to Troubleshoot Different scenarios in Always on Availability Groups

Поделиться
HTML-код
  • Опубликовано: 25 окт 2024

Комментарии • 26

  • @olaoluwaadeosun2942
    @olaoluwaadeosun2942 8 месяцев назад

    Big thumbs up Vamsy, your videos are thorough and effective,
    Cheers

  • @shaiknasreen9436
    @shaiknasreen9436 Год назад +2

    Learning many things from your videos thanks for sharing :)

  • @user-ui2nt8dl1k
    @user-ui2nt8dl1k 2 месяца назад

    Very informative and very useful troubleshooting scenarios.
    also please replicate following issue and try to troubleshoot this scenarios. (due to its nature of the error this has multiple scenarios in itsetlf)
    Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement.
    This could be because the pre-login handshake failed or the server was unable to respond back in time.
    The duration spent while attempting to connect to this server was - [Pre-Login] initialization=0; handshake=14999; (Microsoft SQL Server, Error: -2)

  • @yasaswinianjana9228
    @yasaswinianjana9228 Месяц назад +1

    Simply Superb:)

  • @shrinivascap4198
    @shrinivascap4198 2 года назад

    Learn more from this video
    .good job bro

  • @Jayadhev
    @Jayadhev 2 года назад +2

    Excelent explanation👏

  • @jayapalreddy5120
    @jayapalreddy5120 5 месяцев назад

    Thank u Vamshi

  • @2k6abhi
    @2k6abhi Год назад

    Hi.. Our SQL always on setup (win 2019) with quorum disk is switching frequently (2-4 times a week) automatically. Network looks all OK.. ping responses are all OK at the time of switching. All 3 servers are in local network. Not able to get to the root cause. any help?

  • @rajpriyanshu9317
    @rajpriyanshu9317 Год назад

    Hi,
    I am facing a issue on AOAG. we have 3 nodes server and 2 are in synchronous commit and another is in asynchronous commit mode in the weekend the 3rd node (Asynchronous) is terminated from primary replica for few seconds and after that it will get connected automatically it's on AWS EC2 instances i am not able to find the solution could you please help me out for this issue?

  • @masthanbabusql7328
    @masthanbabusql7328 2 года назад

    Are starting any online classes vamsi ?

  • @mukulanand7627
    @mukulanand7627 Год назад

    Hi sir, Good evening, By when your new online batch will start?

    • @vamsychiranjeevi9619
      @vamsychiranjeevi9619  Год назад

      Hello, Thanks for your interest. Can you ping me on my WhatsApp +91-9739093905?

  • @vinayak717
    @vinayak717 3 месяца назад

    If my AG is Asynchronous commit & fail over mode is manual and if my both Server is restarted what happens to AG is my AG will be healthy after restart

    • @vamsychiranjeevi9619
      @vamsychiranjeevi9619  3 месяца назад

      if it is graceful restart then the databases will need to go through crash recovery for primary and secondary replicas. Post that the databases will come online on primary and on secondary if not we need to resume them

  • @hosang9685
    @hosang9685 Год назад

    hi sir, i've configure sql server 2109 always on on window server 2022 it's work smoothly but when i turn on window firewall all database not synchronize i try to allow many port but it's still got issue, please kindly help guide thanks

  • @skjibon6561
    @skjibon6561 8 месяцев назад

    Sir, What about all job when it's failover

    • @vamsychiranjeevi9619
      @vamsychiranjeevi9619  8 месяцев назад +1

      I took a class on how to take care of the jobs when it gets failed over

    • @skjibon6561
      @skjibon6561 8 месяцев назад

      Please upload this video, is there any scripts when it’s failover primary jobs will be enabled and secondary jobs will be disable