New answers tagged

0

Here are the details of that error code (19): ERROR_WRITE_PROTECT 19 (0x13) The media is write protected. You need to consult the cluster log (use Get-ClusterLog to get that) for additional details about what writes failed within the cluster operation being performed. Check that out and update your question with any errors you see. That being said, ...


0

My question is, what goes in the connection string for the client application, the ip for the SQLCluster or the ip for the SQL resource? The SQL Resource should have an associated Virtual Network Name (or Client Access Name). This resource has an associated IP address that moves between nodes during failover. This is what your connection strings should ...


0

My question is, what goes in the connection string for the client application, the ip for the SQLCluster or the ip for the SQL resource? You should always refer to the Client Access Name or the IP Addresses you see on the SQL Server role properties. Also, when I manually failover from Node1 to node2, using the the roles pane, the owner node changes and the ...


1

I finally managed to figure it out. I think information is missing, hard to find and no described in much detail. So for me I was a bit in the dark when figuring this out. Also, I think I had some tunnel vision at the start thinking that storage replica works in a certain way. MS has a different way of configuring it and the way it works/ you are supposed to ...


0

So unfortunate news for you is it sounds like this closed source application uses a potentially deprecated feature of SQL Server if it's using SAVE TRANSACTION, and was not designed to run for a database that's part of an Availability Group (or any kind of clustering for that matter). Even more unfortunate is your only three options are: Thoroughly verify ...


Top 50 recent answers are included