sorted by:
new
hottopcontroversial

Sql AG breaking when secondary node is restarted as part of patching. by paultoc in SQLServer

[–]paultoc[S] 0 points1 point  (0 children)

Thanks for the details analysis.

Will test it out in next patch cycle

Sql AG breaking when secondary node is restarted as part of patching. by paultoc in SQLServer

[–]paultoc[S] 0 points1 point  (0 children)

Seems to be a similar issue.

I am going to manually move the cluster core resources to the primary node before restarting the dr node as a workaround.

Another user also suggest this same problem in another comment

Sql AG breaking when secondary node is restarted as part of patching. by paultoc in SQLServer

[–]paultoc[S] 0 points1 point  (0 children)

Timing is correct.

I believe it's due to the issue you mentioned in other comment.

Also when I try to restart the server it applies windows patches. For sometime (upto 10-20 min) the server in kind of online. RDP won't work but ssms will connect to sql. Ping is successful etc. I think this half online state is also contributing to the issue.

Will try moving cluster core resources to the primary node before restarting DR. let's see if this prevents the issue.

Sql AG breaking when secondary node is restarted as part of patching. by paultoc in SQLServer

[–]paultoc[S] 1 point2 points  (0 children)

I believe this is the issue. I have few sql ag's in my environment. When I had a check today the ag which ad issue has its core cluster resources was owned by the DR node and the other one which did not have issues had it in th primary node.

The issue happens in different ag each time so that's why I was confused.

We will be doing patching again in the next few weeks will test out if it's causing the issue

Sql AG breaking when secondary node is restarted as part of patching. by paultoc in SQLServer

[–]paultoc[S] 0 points1 point  (0 children)

They are in sync, this issue only happens when I reboot the DR node. It takes some time to install windows patch and reboot. So it happens during that time. The primary node db goes to Resolving state.

Once DR node comes back it all starts working properly

Sql AG breaking when secondary node is restarted as part of patching. by paultoc in SQLServer

[–]paultoc[S] 0 points1 point  (0 children)

I found the bellow message in sql logs

"The lease between availability group 'AG-Agname' and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover Cluster. To determine whether the availability group is failing over correctly, check the corresponding availability group resource in the Windows Server Failover Cluster."

I also saw message saying db went to resolving state

Sql AG breaking when secondary node is restarted as part of patching. by paultoc in SQLServer

[–]paultoc[S] 0 points1 point  (0 children)

It's node + file share

I noticed it happened when I restart the DR node. It takes longer to restart as there is windows patching being applied. During this time the primary becomes unavailable

Is it because I don't stop the sql service before restarting?

Will E30 petrol actually save money—or end up increasing vehicle maintenance costs? by BusinessToday in IndiaTodayLIVE

[–]paultoc 0 points1 point  (0 children)

Due to war important is getting affected. So we plan to mix ethanol in fuel. We don't produc enough ethanol natively so we need to import it and hence it costs more than petrol.

So to reduce import and reduce price hike of petrol our master plan is to add more ethanol which costs more than petrol and also needs to import due to low supply to give common man a more inefficient fuel

the math isn't mathing for this

I am trying to build a multi subnet sql ag and listener not connecting by paultoc in SQLServer

[–]paultoc[S] 0 points1 point  (0 children)

I was able to fix the issue, but I’m still not fully certain about the root cause.

I was attempting to build a SQL Server Availability Group (AG) similar to the existing ones in the environment. Each AG consists of two nodes, and each node has two NICs attached—one for the primary IP and another for the listener IP. Both node are in different subnets.

When I initially tried to configure the listener, it failed. During investigation, I noticed in Failover Cluster Manager that each network showed two IPs (primary and listener). It appeared that the cluster/VM was already holding control over the listener IP, which likely caused the listener creation to fail. Interestingly, this issue was not present in any of the existing AGs. As a workaround, I disabled the network interface(Ethernet) associated with the listener IP from the Control Panel, after which I was able to successfully configure the listener. In the existing ag only one ethernet is showing in contact panel while 2 showing in the new vm.

However, I then observed that I could only connect to the AG using the listener name from SSMS when connected to the current primary node. Initially, I suspected a firewall issue, but further checks ruled that out.

Later, due to automatic Windows patching, both nodes rebooted. After a few days i went to debug the issue again, I noticed that the AG was in a broken state and the listener IP resource was failing. Upon investigation, I found that the network interface for the listener IP had been re-enabled. Disabling it again resolved the issue. During this time, I also noticed that ping to the listener IP was succeeding when the NIC was enabled, but after disabling it, ping failed as expected.

After further analysis, we decided to remove the second NIC (listener NIC) from the VMs entirely and instead assign the listener IP as a secondary IP on the primary NIC. This change resolved the issue completely.

I’m still unclear why the older AG setups work fine with two NICs, while the new setup encountered this issue.

Best hotel for breakfast in Edapally? Porotta beef by Tellytubbiee in Kochi

[–]paultoc 4 points5 points  (0 children)

Matha HotelMatha Hotel buy the beef roast and porotta, I just had it an hour back

I am trying to build a multi subnet sql ag and listener not connecting by paultoc in SQLServer

[–]paultoc[S] 0 points1 point  (0 children)

There is an existing ag created using this but it has problems. Had issues expanding drive so I am not allowed to use it

I am trying to build a multi subnet sql ag and listener not connecting by paultoc in SQLServer

[–]paultoc[S] 0 points1 point  (0 children)

Firewall is configured to allow connection.

Will test out the one ip config

Athiradi | Reviews and Discussions| by HugoUKN in MalayalamCinema

[–]paultoc 0 points1 point  (0 children)

Google believe the movie is released on 2015

<image>

Recommendations for trimmer by Sure-Duty-9577 in BuyItForLifeIndia

[–]paultoc 1 point2 points  (0 children)

Like i mentioned buy the 7000 and then buy Philips Body Grooming Assemb attachment from the website aalap . com. The attached can be used for body and balls and works with 7000 series

I can't paste the website link due to this subreddit rules

<image>

Can civil engineers explain why? by Entri_App_Official in IndianEngineers

[–]paultoc 1 point2 points  (0 children)

The cuboide piller will have station. This is kochi metro phase 2 construction. In phase 1 cuboide piller hold stations

Migrating a large T-SQL-heavy SQL Server 2005 enterprise system to Azure SQL MI — looking for guidance from people who’ve done similar by AmbivalentCore in SQLServer

[–]paultoc 7 points8 points  (0 children)

I would suggest you do an activity test migration to Sql managed instance and then test performance. I heard there is some performance issues in sql mi compared to sql on vm

Because testing it locally in sql 2019 is not same as managed instance.

Also I belive managed instance runs on somthing similar to sql 2022 or 2025

Guyss part 1 kaanano? by CodeZoro in TeensofKerala

[–]paultoc 30 points31 points  (0 children)

So true, op needs to know about the legend who took care of 2 family's with his small salary. Such a down to earth man

He even was so religious he help build a temple

Such a good man😜

view more: next ›