New answers tagged

1

In order for SQL Server services to start as part of a Windows Failover Clustering Service, quorum needs to be attained by at least one node in the cluster. If a two-node cluster has one node down, that node cannot contribute to the quorum, so some other method is necessary for the node that is up to attain quorum. Quorum is essentially a set of votes to ...


1

It's really not THAT different to Service Pack patching whereby you'll need to do passive nodes first, then give cluster resource group ownership to one of the upgraded nodes, in order to finally upgrade the active node. Map out your upgrade sequence first and test it if you have the luxury of a dev environment. In place upgrades are supported and the ...


3

Short answer In a distributed system, you can't be prevented from simultaneous withdrawals. If you want to prevent simultaneous transactions then don't use a distributed system. Clarification By "distributed system", I mean a system where two or more different components can act without waiting for confirmation from the rest of the system. Two-phase ...


0

Try to run Repair on Passive node once that come clean try to failover to passive node, once failover test complete successful then try to apply SP3. Also make sure you have SQL Server service account is LOCAL ADMIN on both NODE.


2

vMotion and clustering aren't alternatives for one another. vMotion moves the same "machine" (albeit virtual) from one physical host to another. This provides some sort of resilience to hardware failure (unless it's the shared SAN bombing out) but you can't fail over to another host if you would like to create a maintenance window with minimal downtime for ...


-3

creat three replica set with different port number and then try


0

In my personal experience, Scale Arc support has been notoriously bad and their software seems to be pretty unreliable. Our Database connection to our Load balancer fails for no legitimate reason. For instance, we've had our database connection fail, which affects all of the services we have running on our webservers. When we reach out to Scale Arc ...


1

A workaround for this problem: Uninstalled everything, ran setup with /ACTION=PrepareFailoverCluster on both nodes first (which allows you to choose the binary locations), and then ran it again with /ACTION=CompleteFailoverCluster on one of the nodes. It takes three runs of the installer instead of two, but it solves the issue. The only limitation is that ...


2

It appears to be a bug/feature. It was discussed previously on SQL Server Central http://www.sqlservercentral.com/Forums/Topic1578488-2799-1.aspx where Ed Vassie said: Put it another way... On an ADDNODE install you cannot specify the location for the SQL binaries, they always go to the system drive. Ed Vassie is a reliable source as the original ...


1

If Production site SQL DB Servers are down, will Windows Server Failover Cluster be Online or Offline ? If you have a setup that relies on a quorum disc, this must be available - ergo offline. This is a non recommended setup. Whoever set it up did not bother to validate it makes sense. Geographically dispersed clusters are a proven technology (start ...


1

There is no reason to move the cluster core resources. They are NOT part of the availability group and function entirely on their own. There is no need to even have these on the same server as any of your AG resources. The core cluster group provides the administrative point for the cluster which is completely independent from any other resources on the ...



Top 50 recent answers are included