SQL 2012 Always On Availability Groups

Has anyone configured FIM SYnc, FIM Service and MSF in SQL 2012 Always On Availability groups
I do not believe we can configure the SQL connection string for FIM Sync or FIM Service to include "multisubnetfailover"
TIA
Nigel

I commented on this here:https://social.technet.microsoft.com/Forums/en-US/64f55628-3b5d-4d16-9044-dcbe7053581d/lack-of-support-for-fim-database-mirroring?forum=ilm2
Additional comments:
SQL Server Always On Failover Cluster Instances should be supported just as SQL Clustering is supported.
SQL Server Always On Availability Groups are not supported, just as Database Mirroring in synchronous mode (which is required for automatic failover) is not supported. I can't find authoritative statements of this on the web. But I know this to be the
case.
Ultimately, the reason for lack of support for mirroring (for automatic failover or in synchronous mode) is that the product group has said so (in conferences and webinars). Meaning the product group has not tested it or has and decided that it doesn't
work or adds risk.
Possible underlying reasons:
1) To do automatic failover with mirroring or Availability groups you must edit the connection string. The way FIM builds the connection string out of the components in the registry don't permit this.
2) Running mirroring in synchronous mode slows down performance in two ways: first is the additional traffic to send it to the mirror partner (or replica), second and most important is that synchronous requires that the primary not truly commit the transaction
until it has been committed to the secondary which means transactions take longer. For some products this can result in an unacceptable performance degradation.
Hopefully, MIM will support Availability groups.
David Lundell, Get your copy of FIM Best Practices Volume 1 http://blog.ilmbestpractices.com/2010/08/book-is-here-fim-best-practices-volume.html

Similar Messages

Sql 2012 always on availability group use cases

i have setup the always on availability group between 2 sql servers.
in the primary site, my app is connected to the primary site.
The DB is in an always on group replicated to the secondary site.
so what is the use of the secondary replica for?
If the primary db server goes down, what will happen?
Can apps use the replica db? but its read only
what is the purpose of this?

I agree with David.
JonDoe,
What you are asking is known as "active secondary" in AlwaysOn
http://msdn.microsoft.com/en-us/library/ff878253.aspx
Automatic failover can be configured. Refer
http://msdn.microsoft.com/en-us/library/hh213151.aspx
Be aware of http://support.microsoft.com/kb/2833707
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

Which Edition of Windows is required for using SQL 2012 Always On Availability Groups

I want to use the new feature of having 2 secondary mirror replicas. the first secondary replica will be sync the second one will be async.
Currently I have SQL Enterprise license and Windows 2008 R2 Standard license.
Will I be required to upgrade to Windows Enterprise license to use Always On? (since this feature depends on Windows clustering?)
Can you please confirm if SQL Always On feature can be used on Windows 2008 R2 standard or not?
MSDNStudent Knows not much!

Always On is available with Standard Edition but it supports only 2 nodes.
AlwaysOn is a bigger umbrella which covers two features. AlwaysOn Availability Groups (AG) and AlwaysOn Failover Cluster Instance (FCI).
FCI for 2 node is supported. You can't use AG feature in SQL Server Standard Edition
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

Clustering Pre-reqs for sql 2012 always on availability group

Hello,
I'm currently in the planning stages of building a sql 2012 alwaysON cluster on Windows server 2012. I'm a bit confused with some of the requirements.
Does windows 2012 clustering require a heartbeat network as well a nic that communicates with the domain?
For a 2 node 2012 always on sql cluster which type of cluster should I use? node majority? node majority plus fileshare?
thanks!

I found this information regarding SQL 2014. This could be helpful
"We strongly recommend that you use the same network links for communications between WSFC cluster members and communications
between availability replicas. Using separate network links can cause unexpected behaviors if some of links fail (even intermittently).
For example, for an availability group to support automatic failover, the secondary replica that is the automatic-failover partner must be in the SYNCHRONIZED state. If the network link to this secondary replica fails (even intermittently), the replica enters
the UNSYNCHRONIZED state and cannot begin to resynchronize until the link is restored. If the WSFC cluster requests an automatic failover while the secondary replica is unsynchronized, automatic failover will not occur."
source:http://msdn.microsoft.com/en-us/library/ff878487.aspx#NetworkConnect

SQL 2014 Always On Availability Groups

It appears to be working. I've attached a picture of the role that was created when I was finished configuring WSFC. Is there something that would I can check that would give me a definitive answer?

I am testing SQL 2014 availability groups and I have run into a snag. I setup a win2k8 r2 DC and two windows 2012 R2 servers running SQL 2014 standard. I setup failover clustering for the two SQL servers. In SQL Management Studios I have setup the availability group and everything seems to have been successful. except when the wizard completes I get an error Creating availability group listener resulted in an error.....Error 41009.The AG seems to be working I can connect to the AG in SSMS using the listener name. But in the Availability Group Listener section there is no listener setup. Also the databases also seem to be read only if I connect thru the listener name. The AD computer account seems to be setup correctly. I am just unable to create the listener in SQL. Is there a security permission in SQL that I could have missed. Any...
This topic first appeared in the Spiceworks Community

SQL 2012 Always On Availability Create Key for Dynamics CRM syntax

Hi I am trying to follow this terribly written article to setup CRM to be part of a SQL alwayson availability group.
The part that is pissing me off is the create SQL logins. http://technet.microsoft.com/en-us/library/jj822357.aspx#BKMK_always_updateorg
So many errors with this post causing so much frustration. What is the actual correct Syntax for creating the key?
Obviously you have to use a UNC path to the CRM front end server. SQL doesnt like UNC and I think an earlier guy said it doesnt like double quotes. Here is what I have and it does not like it. Its hard to see but right before end I have two
single quotes to close it. It's complaining about the \\ in the UNC path.
IF NOT EXISTS (SELECT * FROM sys.asymmetric_keys WHERE name = 'MSCRMSqlClrKey') BEGIN EXECUTE ('CREATE ASYMMETRIC KEY MSCRMSqlClrKey FROM EXECUTABLE FILE ='\\CRM2013\C$\Program Files\Microsoft Dynamics CRM\tools\Microsoft.Crm.SqlClr.Helper.dll'')END

I finally got it working not by using the syntax in that article though. First I did the select all from to see if the key existed by itself
SELECT * FROM sys.asymmetric_keys WHERE name = 'MSCRMSqlClrKey'
NO key was there so then I did
CREATE ASYMMETRIC KEY MSCRMSqlClrKey FROM EXECUTABLE FILE ='C:\Program Files\Microsoft Dynamics CRM\tools\Microsoft.Crm.SqlClr.Helper.dll'

How do I remove a node from Always on Availability Group in SQL 2012

Hello I was wondering if anyone could tell me to remove a node from an AOG group in SQL 2012. We currently have a two node Always on availability group and I need to replace one of the servers. My plan is to bring the
new server on to the group then remove the old server and I am having issues finding documentation on this. Could someone explain how to do this or if it is even possible.
Thanks

After the new server is added to the cluster and the AG, remove the old one by first
ALTER AVAILABILITY GROUP [YourAG]
REMOVE REPLICA ON N'OldServer';
Remove a Secondary Replica from an Availability Group
Then evict the old server from the cluster with the cluster administrator or
Remove-ClusterNode OldServer
Remember to verify the quorum configuration after adding the new server and removing the old server.
David
David http://blogs.msdn.com/b/dbrowne/

Always on Availability groups using static SQL Tcp Port

Hi, I have 2 SQL 2012 servers in my DMZ and I have assigned SQL to run on a static TCP Port. I would like to setup Always On availability groups on the servers but I cannot get the failover to work with the static TCP port. It works fine
with dynamic ports.
When the failover is initiated it attempts to connect to the secondary replica with out using the static port, can someone tell me how to setup the availability group using static tcp ports.
Thanks,

When I setup the secondary replica I added the port number, but it doesn't appear to use it for failover. I add the secondary replica w/o errors.
I am not sure how to add the port number to the primary.
Dave
Hi Dave,
Based on your description, could you please post the error message when getting failover to the secondary replica?
In addition, If you use the default port of 1433 for availability group listener VNNs, you will still need to ensure that no other services on the cluster node are using this port; otherwise this would cause a port conflict.
If one of the instances of SQL Server is already listening on TCP port 1433 via the instance listener and there are no other services (including additional instances of SQL Server) on the computer listening on port 1433, this will not cause a port conflict
with the availability group listener. However multiple instances of SQL Server (side-by-side)should not be configured to listen on the same port.
For more details, please review this article:
Availability Group Listeners, Client Connectivity, and Application Failover (SQL Server).
Thanks,
Lydia Zhang

Cannot connect to SQL SERVER with Always on availability group listener name

Hi everyone,
I have setup always an availability group listener for sql server on port 1433, have opened the port in firewall , remote connections are enabled in the sql server, but still I am not able to connect to the sqlserver instance with the help
of the availability group listener name.
I get the following error.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.(provider:
TCP Provider, error: 0 - The wait operation timed out.)"} System.Exception {System.Data.SqlClient.SqlException
Have gone through several blogs for the solution but none of them helped.
Please let me know if anyone has fixed the issue.
Regards,
Divya

Prior to making SS connection, can you establish the connection with a networking tool?
SS connectiviy trouble shooting:
http://technet.microsoft.com/en-us/library/ms378845.aspx
http://stackoverflow.com/questions/5919524/not-able-to-telnet-sql-port-1433-locally-or-remotely
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/227f431a-4274-4d95-b605-67541d78ef03/test-sql-connection-with-telnet?forum=sqldataaccess
Kalman Toth Database & OLAP Architect
Free T-SQL Scripts
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

Some Quick clarification about 2012 and always on Availability groups

Hi guys, just need some clarification about always on.
I've got plenty of experience with normal SQL Clusters, but just need some clarification around always on availability groups.
I presume with AG, you setup a listener and this becomes your point of connection, IE this is what you use in the you connection string for you applications, so can I use this when I am setting up a new application, and will this automatically make the Database
that's created by the APP, Highly available. ? or do you still have to add it to the AG afterwards. ?
I have also read that you can still point to the installed SQL instance, and you don't need to use the AG group listener, but how does this make your DB HA ? how does the failover work.
I also presume you don't need to use any roles under the MSC anymore.
Kind regards
Mark.G

Hi Mark
I presume with AG, you setup a listener and this becomes your point of connection
That's right, the listener is a virtual network name and you can use this to connect to the primary or secondary replica. Your connections will go in against the primary unless you're using
read-only routing.
so can I use this when I am setting up a new application, and will this automatically make the Database that's created by the APP, Highly available
The first thing you'll have to do is set up the availability group (AG). You can then associate a listener to the AG. I know you're familiar with failover clustering but the mechanics of this are much closer to database mirroring. For every database that's
part of the AG you'll have at least one secondary replica, it's possible to automatically failover to this if you're in synchronous mode.
I have also read that you can still point to the installed SQL instance, and you don't need to use the AG group listener, but how does this make your DB HA ? how does the failover work.
Yes you can do, but from an application perspective you should only do this for databases that are not part of an AG. If you connect to the instance directly and you have a failover your app will no be able to connect to the database (on the assumption your
secondary isn't read-only). App connections should always be via the Virtual Network Name.
I also presume you don't need to use any roles under the MSC anymore.
Not sure I understand this? Do you mean will roles be available in cluster manager? Each AG group will have a role but failover is now controlled through the SQL Server rather than the cluster manager.

Setting Up Alerts for Always on Availability Groups Failover

Hi Folks,
In SQL Server 2008R2 we set up alerts for Mirroring failover using WMI Alerts. As Like this.
Now we need to configure similar alerts for Always on Availability Groups(AAG) in SQL Server 2012, but it seems that there is no such WMI Alerts or any standard way to set up the alerts for getting notified for AAG Failover. Click
Here
Should I manually Create a SQL Agent Job using
these DMVs and schedule it at frequent Interval to get notified about any AAG failover or is there any standard way as for mirroring Failover alerts? Any suggestion or help is appreciated.
Pranshul Gupta

Maybe you wanna have a look at this:
http://blogs.msdn.com/b/sqlalwayson/archive/2012/02/13/monitoring-alwayson-health-with-powershell-part-1.aspx
http://blogs.msdn.com/b/sqlalwayson/archive/2012/02/13/monitoring-alwayson-health-with-powershell-part-2.aspx
http://blogs.msdn.com/b/sqlalwayson/archive/2012/02/15/monitoring-alwayson-health-with-powershell-part-3.aspx
http://blogs.msdn.com/b/sqlalwayson/archive/2012/02/15/the-always-on-health-model-part-4.aspx
Bodo Michael Danitz - MCT, MCITP - free consultant - performance specialist - www.sql-server.de

Sql 2012 always on setup

I got a sql 2012 always on setup between 2 standalone servers in 2 different locations.
I do not understand why I need cluster manager managing the 2 nodes.
I have cluster manager but there is no shared disks. there are 2 nodes under cluster manager and one cluster name.
what would be the different between the cluster name here and the availability group listener name in sql 2012? they are both different names

Read those articles
https://www.microsoftvirtualacademy.com/tracks/mission-critical-confidence-using-microsoft-sql-server-2012
http://www.sqlservercentral.com/articles/FCI/92196/
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Backup Sharepoint 2013 Farm with SQL 2012 "Always On" using System Center 2012 R2 Data Protection Manager

Is backing up and Restoring SharePoint 2013 Farm with SQL 2012 "Always On" High Availability now supported using "System Center 2012 R2 Data Protection Manager"?
I cannot find confirmation anywhere.
Regards,
John

Per this thread
http://social.technet.microsoft.com/Forums/en-US/0c047737-4733-4ad5-a24d-3e6e6ff42f70/dpm-2012-sp1-and-sharepoint-2013-on-a-sql-2012-alwayson-ag?forum=dpmsharepointbackup, no it does not look like this is supported.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

How to install SSAS Cluster instance with Always On availability group(Standalone database instance) in same windows cluster servers

We have requirement like to Install the SSAS as Cluster instance where SQL Server Database engine was installed with Always On availability group.Please help me to how configure it
Currently we have following configuration in Current steup.
Node1 and Node2 are in windows cluster
Node1 has SQL Server Database engine Instance1 as Standalone
Node2 has SQL Server Database engine Instance2 as Standalone
Instance1 and Instance2 configured for Always On availability group with Listener.
Now we have to steup SSAS instance with High availibilty. I know we have only option is to install cluster SSAS instance.
Can some one provide information below.
1. How to steup Cluster SSAS instance in this servers.
2. Is this will have any dependancy on exisiting Listner name.
3. Is this affects the availiblity groups, if SSAS instance failed over to another node.
Thanks in Advance
Sriram

You will need to have SSAS installed as a clustered instance with shared storage. Refer to the whitepaper from this MSDN article
How To Cluster SQL Server Analysis Services
Availability Group is in it's own Role/Resource Group. When you create the clustered SSAS, it will create its own Role/Resource Group. This means that it will require its own virtual network name and virtual IP address and will not affect the existing Availability
Group. You can also have it on the existing Availability Group if you want to. However, you need to decide if you want SSAS to failover with the Availability Group or not. Your design choices will depend on that decision.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

Always On Availability Groups

Hello everyone!
I am currently planning to implement SQL Always On Availability Groups.
Mainly i have one sql server so apparently i need to setup a new sql server.
In the wizard there is a page where I need to select Initial data synchronization full or join.
What’s the difference?? Is choosing the full option requires me to provide a Third server to temporarily store my database so my 2 main SQL server can sync for the first time? And if yes can I remove this shared location (Third server) after the database
are synced??
Thank You.

Join option only if the new
secondary databases already exist on each server instance that hosts a secondary replica for the availability group. That is you have manually restore a recent database backup of the primary database using RESTORE WITH NORECOVERY, and then restore each
subsequent log backup using RESTORE WITH NORECOVERY.
Full option
creates a full and log backup of the primary database, create the corresponding secondary databases by restoring these backups on every server instance that is hosting a secondary replica, and join each secondary database to availability group.
When you use full you have to
specify a network share folder in order for the wizard to create backups and secondary replica will access backups to perform restores from this stage. Yes you can remove the share once the all databases are in sync.

SQL 2012 Always On Availability Groups

Similar Messages

Maybe you are looking for