First, let me clarify, the words in the subject of this blog are the exact words used by my client and whatever you do and say but “customer is always right!”. Here is the complete story where we faced issue related to AlwaysOn Replica.
SQL SERVER – AlwaysOn Availability Group Listener – This TCP Port is Already in Use
While doing a preparation of a demo, I encountered below error while creating the listener of the AlwaysOn availability group. I was trying this from Management Studio.
SQL SERVER – Unable to Get Listener Properties Using PowerShell – An Error Occurred Opening Resource
I was engaged with a client for an AlwaysOn project and they had some follow-up questions. I took some time to find the answers and encountered an interesting error. I am sharing them here so that others can get benefited. They informed me that they are not able to see and modify listener properties. Let us learn about this error related to opening resource.
SQL SERVER – FIX: The Log for Database Cannot be Shrunk Until All Secondaries Have Moved Past the Point Where the Log was Added
While preparing for a demo for a client I was hit with an interesting error in AlwaysOn Availability Group backup and restore scenario. In my lab setup, I had four nodes SQLAUTH1 to SQLAUTH4 and I have always on high availability turned on SQL Server 2016. I played and did several operations with database and found that I have bloated the transaction log file to 100 GB. And now I need to shrink the transaction log on SQLAUTH1. As soon as I did that, I was welcomed with below message about database cannot be shrunk until all secondaries have moved past the point.
SQL SERVER – Caution: Adding Node in AlwaysOn Availability Group
It is interesting to see that in the past few days I have seen a similar pattern of an issue hit by three clients. All of them contacted me for a short engagement for the same issue. As you might know, every single day I keep two slots available for On Demand (50 minutes) so here is one of their emails. Let us learn about adding node in the AlwaysOn availability group.
SQL SERVER – FIX: Msg 35250 – The Connection to the Primary Replica is Not Active. The Command Cannot be Processed
Earlier I wrote a blog on same error message which you can read from below link. SQL SERVER – FIX: Msg 35250, Level 16, State 7 – The Connection to the Primary Replica is Not Active. The Command Cannot be Processed
SQL SERVER – Can I Delete Always On Availability Groups Initial Sync Folder?
This was one of an interesting question which I heard from one of my clients who deployed AlwaysOn availability groups. I was not able to find much documentation and clarity so did some research and found an answer. This can also be an interview question as well.