Тёмный

Why my Always on Availability Groups is not getting failed over despite of no errors part-2 

vamsy chiranjeevi
Подписаться 4,3 тыс.
Просмотров 1,5 тыс.
50% 1

Опубликовано:

 

20 авг 2023

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 5   
@smempire5027
@smempire5027 10 месяцев назад
hi dear How do I know if SQL Server needs more memory?
@sqlserver6395
@sqlserver6395 10 месяцев назад
I have same similar kind of issue when we want to failover to secondary replica in ag that is manual failover . we received an error with wsfc 5016 with sql server 41018 error . we are unable to failover.
@vamsychiranjeevi9619
@vamsychiranjeevi9619 10 месяцев назад
Thanks for sharing bro.
@user-cx7ig4di4e
@user-cx7ig4di4e 10 месяцев назад
Hi Vamsi, Apart from jobs, how specific applications let's say some readable applications can connect to secondary replicas to increase performance? How they identify the secondary node to connect and perform the task Can you please tell me
@vamsychiranjeevi9619
@vamsychiranjeevi9619 10 месяцев назад
You need to use Read only routing. once we configure then reporting workloads can be diverted with the help of Application Intent=Readonly. But we need to have license to make use of secondary replicas for reporting.
Далее
Gale Now VS Then Edit🥵 #brawlstars #shorts
00:15
Просмотров 747 тыс.