SQL 2012 Always On

I want to place a quorum and was wondering what is the best practice.  Also what are the ramifications if we do not install a quorum.

Can 2 quorums be installed one at each site?

Also what are the advantages of choosing 'Advanced' option when installing SQL 2012, and why should we use it.

Also our infrastructure consists of 4 instances in 2 sites - GEO Cluster,  each instance has it's own storage device.
2 instances in each site.    
We want to use ALWAYS ON.

Any recommendations.

I also noticed that for always on to work  the same drive letters have to be for each node, but when you do that it says cannot use those driver letters they are taken when configuring say the 2nd node.

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

I am not sure what you mean when you say "I want to place a quorum". Always On works on Windows Failover cluster that has to be setup an all nodes(servers) that will participate in the Always On. I don't remember to have to be worried of any quorum. That happens within the cluster itself and is part of it.

The sequence is:

1. Create the fail over cluster adding all the servers that need to participate.
2. Install SQL server and setup the always on from configuration manager.
3. Add a listener that will actually be the entry point and pointer to servers from any app
4. Create the availability group that will be part of AO
5. Add the nodes to the AG
6. Backup and restore the database from primary on the secondary nodes.

That is about it. If you have 4 instances on 2 location then I would suggest to make one primary on one node and the fail over secondary on the same location, you can setup these two to be in synchronous mode. The nodes from the other location you can add them in asynchronous mode. This will save you sync-ing performance.

The advantage in synchronous mode is that the 2 main nodes will be always in sync but it can add some lag to any transaction, depending on your network and amount of transactions. The asynchronous mode will have a bit of delay in terms of sync-ing but will never interfere with the principal. Having synchronous mode over 2 different location is not recommendation especially if they are on different geographical locations.
techgeniousAuthor Commented:
I was advised that we have to use a 'quorum' as a referee.
I would like to know what is best practice for placing the quorum in a Geo Cluster Site.

We have two sites in different states & a main headquarters.

Are you saying we do not need a quorum?
To be honest I didn't set up any quorum when i set up the always on and it was working without problems. It was test environment. Anyway, maybe this will help:


There is areference to a video inthere of how you do it.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
techgeniousAuthor Commented:
I solved the rest.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.