While configuring AlwaysOn availability group for one of my clients, there were various errors. I planned to write blog on all errors which I encountered. Here is an earlier blog. After we bypassed all errors in “Select Databases” screen, we came to “Specify Replicas” screen. We added both server names and as soon as we hit next, we got below message. Let us learn about how to fix AlwaysOn Wizard Error.
SQL SERVER – Error – Auto Close is Enabled. Only Databases with Auto Close Disabled can be Added to an Availability Group
As a part of my consulting job, I do work with clients who wanted to deploy AlwaysOn availability group. Sometimes there are some simple errors which are encountered, but new DBAs are not aware of such things. In this blog we would talk about one of such error.
SQL SERVER – Adding New Database to AlwaysOn Replica is Slow
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 – 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 – AlwaysOn Join Error – Msg 1408, Level 16 – The Remote Copy of Database “SQLAUTH” is Not Recovered Far Enough to Enable Database Mirroring or to Join it to the Availability Group
I do provide consultancy services for deployments, including AlwaysOn availability group deployments. AlwaysOn Join Error.
SQL SERVER – FIX: Msg 35250, Level 16, State 7 – The Connection to the Primary Replica is Not Active. The Command Cannot be Processed
Along with my performance consulting, I also assist many clients in fixing some quick issue. You can refer for various consulting services which I provide. This blog is an outcome of one such engagement where the client has deployed standalone SQL Server on two machines, created windows cluster between them and wanted to then use AlwaysOn availability group feature. This blog is about Primary Replica not being active.