I have installed failover clustering feature on two servers with Windows Server 2012 and then I installed SQL Server 2012 on both of them. I also enabled SQL Server 2012 AlwaysOn feature. Now I can access each node by instance name. I can also connect using failover cluster name. What is the difference between accessing SQL Server by instance name and cluster name?
closed as not a real question by Aaron Bertrand♦, RolandoMySQLDBA, Max Vernon, Jon Seigel, Mark Storey-Smith May 1 '13 at 0:14
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. If this question can be reworded to fit the rules in the help center, please edit the question.
Clustering works very differently in 2012, and using your knowledge from SQL Server 2008 could be confusing you.
Try the following from PowerShell (as admin):
If you see something like:
Then you haven't configured AlwaysOn yet - all you've done is set up an initial cluster.
In this case, connecting to cluster name/IP is meaningless. All it will do is connect you to the server that owns the Windows Failover Cluster, which is arbitrary and completely unrelated to your database configuration.
Once you've correctly configured your SQL Server AlwaysOn Availability groups - basically, additional mini-clusters with their own name and IP address - then the additional names/IP addresses will be meaningful.
For example, you might have three databases configured like this:
At this point, the server you're connecting to becomes extremely important.
You will never want to use applications to directly connect to Server1 or Server2, because which databases are online and which are in recovery will depend on when you last failed over. Instead, all of your applicatons should connect to sqlcluster1 or sqlcluster2 (which have their own IP addresses), and they will automatically reach the database server that currently has that database online.
Additional configuration of your server will be required if you don't have any Availability Groups set up yet.