SQL Server Availability Groups

Hello,
If we want to use SQL availability groups and have the secondary used only for reporting purposes and not DR, do we still need to use the Windows clustering?
Thanks,
m

Take a look into replication or database snapshots if AG does not fit you,
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

Similar Messages

SCOM 2012 R2 Management Servers and SQL Server Availability Groups

My team is in the middle of rolling out a brand new install of System Center Operations Manager 2012 R2.
I have set up a SQL Server Availability group that is spread across multiple subnets and installed the initial management server per
here.
As I have gone through attaching new management servers, I have noticed disturbing behavior. When the AG fails over to another node, the management servers will lose connectivity unless I either recycle the service or it fails back to the original
node. This is not a security issue as I have set up permissions. It says it cannot connect to the database anymore at all.
Has anyone else seen this behavior? Is there a setting I am missing somewhere?
Thanks for your help.
Dale

Hi Dale,
What about ApplicationIntent\Readonly?
http://msdn.microsoft.com/en-us/library/hh205662(v=vs.110).aspx
Still thinking about DNS, may be this could be for your case:
http://www.sqlservercentral.com/Forums/Topic1449216-2799-1.aspx
Natalya

SQL AlwaysOn Availability Group modifies preferred owner node on move/failover

I have a two node Windows Server 2012 R2 failover cluster with two SQL Server 2012 Enterprise AlwaysOn Availability groups configured. Within the cluster I have configured a preference order on which node a AlwaysOn Availability Group should run.
Get-ClusterGroup -Name "AlwaysOn1" | Set-ClusterOwnerNode -Owners "node1","node2";
Get-ClusterGroup -Name "AlwaysOn2" | Set-ClusterOwnerNode -Owners "node2","node1";
After configuring the preference and retrieving the preference order it is configured as it should be. When I do a failover the preference order is adjusted to first the node it currently runs on and second the other node instead of leaving the preference
order as it was. It doesn't matter if I use the PowerShell "Move-ClusterGroup" or the "ALTER AVAILABILITY GROUP [AlwaysOn1] FAILOVER" T-SQL command. From the cluster log it is shown that the preference is modified after the resource
has been moved.
INFO [GUM] Node 2: executing request locally, gumId:15859, my action: /rcm/gum/SetGroupPreferredOwners, # of updates: 1
INFO [RCM] rcm::RcmGum::SetGroupPreferredOwners(AlwaysOn1,<vector len='2'>
The default groups within the cluster "Available Storage" and "Cluster Group" keep their preference setting when configured (only configured for testing to verify it has to do with the SQL Server Availability Group resource type).
The Windows Server 2012 R2 servers are updated using the latest Windows Updates and SQL 2012 has build number 11.0.5556.
For other cluster groups which I have configured in the past like file, Hyper-V (used for affinity to get VM's which have a lot of traffic between them within the same virtual switch to reduce latency and additional hops. it would be nice if vNext will have
a affinity option for cluster groups besides the anti-affinity within the current version)
I would like to know if someone could explain why the SQL Server Availability Group resource always modifies the group preference. I might understand this with a three node cluster where the first two are running in Synchronous commit mode and the third
one in Asynchronous commit mode.
Thanks in advance,
Dennis van den Akker

Hi Dennis van den Akker,
Do not use the Failover Cluster Manager to manipulate availability groups, for example:
Do not add or remove resources in the clustered service (resource group) for the availability group.
Do not change any availability group properties, such as the possible owners and preferred owners. These properties are set automatically by the availability group.
Do not use the Failover Cluster Manager to move availability groups to different nodes or to fail over availability groups. The Failover Cluster Manager is not aware of the synchronization status of the availability replicas, and doing so can lead to extended
downtime. You must use Transact-SQL or SQL Server Management Studio.
The related KB:
Failover Clustering and AlwaysOn Availability Groups (SQL Server)
https://msdn.microsoft.com/en-us/library/ff929171.aspx
The similar thread:
SQL Server Clustering 2008 (Multi Node)
https://social.msdn.microsoft.com/Forums/sqlserver/zh-CN/c35fe863-3fed-4a6e-830b-b79aa032c198/sql-server-clustering-2008-multi-node?forum=sqldisasterrecovery
Best Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Multi Site SQL High Availability group

Hi,
We have our primary Data Centre where we have 2 MS SQL 2012 Enterprise Servers and 2 SharePoint 2013 Enterprise servers.
We have SQL High Availability group implemented on our primary Site (Site A)
Site A has subnet of 192.168.0.0.
We recently added a new DR Site (Site B). Site B we have MS SQL 2012 Enterprise Servers. Site B have a subnet of
172.1.1.0
Both sites are connected via a VPN Tunnel. MS SQL 2012 Enterprise Server on Site B has been added in have SQL High Availability
group of Site A.
SQL High Availability group have 2 IPs 192.168.0.32 and 172.1.1.32. SQL Listener have 2 IPs 192.168.0.33 and 172.1.1.33
We want to make sure that if Site A completely down then Site B work as an active Site. But when Site A down we are unable
to ping High Availability group and Site B is unable to work as active site. SQL and SharePoint services are completely down.
Site A has AD(Primary Domain Controller) and Site B has ADC(Additional Domain Controller).
Site A has witness server.
We are using Server 2012 Data Centre
Please suggest.
Farooq

SharePoint is not the same as any other applications. The DR site has to be a completely different farm from your production. This means that the SharePoint_AdminContent and config databases on both farms are different and should not be included in the Availability
Group (they do not support asynchronous Availability Group.) Only content databases and other SharePoint databases supported in an Availability Group should be included as per this
TechNet article. Have a look at this
blog post for your networking configuration.
The reason your Windows cluster service goes down in the DR data center when the when your primary data center goes down is because the cluster has no majority votes. You have 4 available votes in your cluster - 3 in the primary data center in the form of
the 2 Availability Group replicas and the witness server and 1 in the DR data center. If the Windows cluster does not have majority of votes, it automatically shuts down the cluster. This is by design. That is why when this situation happens, you need to force
the cluster to start without a quorum as described in
this article (Windows Server 2012 R2 introduced the concept of dynamic witness and dynamic quorum to address this concern.) By default, the IP address of the Availability Group listener name will be registered on all of the DNS servers if the cluster is
running Windows Server 2012 and higher (this is the RegisterAllProvidersIP property that Samir mentioned.) However, you need to flush the DNS cache on the SharePoint web and application servers and point them to the correct IP address on the DR server after
failover. This is because the default TTL value of the Availability Group listener name is 20 minutes.
It is important to define your DR strategies and objectives when designing the architecture to make sure that the solution will meet your goals. This will also help you automate some of the processes in the DR data center when failover or a disaster occurs.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

Powershell for to list SQL Server Windows Groups

Hi All:
I m planning to write a script, to pull SQL Server Windows Groups members list by using powershell.
By using dsa.msc i can view the members of a particular SQL widows groups., the same i want to do using powershell., is there any way to do this. I want to run this from remote machine.
Please let me know how can we do this and per-requist... Already installed PowerShell 3.0 and loaded the recommended modules on it.
Thanks,
Satish Kumar.
Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

Hi,
I was able to run the command on the other machines with no problem. Have you tried right-clicking, Run As Administrator?
According http://blogs.technet.com/b/heyscriptingguy/archive/2011/08/29/use-active-directory-cmdlets-with-powershell-to-find-users.aspx
“This warning message: “WARNING: Error initializing default drive: 'Unable to find a default server with Active Directory Web Services running.'” is generated because I have several domain controllers, and not all of them have
the
Active Directory Management Gateway Service installed. Depending on which domain controller authenticated my workstation, the warning appears. The solution is to install the Active Directory Management Gateway Service
on all of the non-Windows Server 2008 R2 domain controllers. The other solution is to ignore the warning and specify the
server parameter each time when using one of the cmdlets (but that will mean the PSDrive will be unavailable).”
In addition, this issue is more related to PowerShell, for quick and accurate answers to your questions, it is recommended that you initial a new thread in our PowerShell forum for dedicated help.
http://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverpowershell
Thanks.
Tracy Cai
TechNet Community Support

2012 SQL AlwaysOn Availability Group - JDBC re-connection not happening in case of Multisubnet failover

Hi There,
Having some problem with MultiSubNet AG failover re-connection using SQL JDBC driver 4. Details given below.
SETUP:
We have a three node 2012 Windows Server Cluster, on top it we have 2012 SQL Sever AlwaysOn Availability Group.
Two nodes are in one subnet and other in a different subnet to make this as a multisubnet AlwaysOn AG.
An AG Listener is configured with a DNS name and two VIP assigned (For two subnet) to it. We were able to failover from one subnet to other using the SQL Studio successfully.
NEED:
We have a java application which will be connected to AG Listener name. In case of failover, automatic re-connection to DB/AG Listener name should happen.
For this we use "sqljdbc4.jar" and added
'multiSubnetFailover=true' in our connection string. The connection String is given below.
cURL="jdbc:sqlserver://testsqlag:1433;databaseName=SalesDB;multiSubnetFailover=true;loginTimeout=200;applicationName=MyApp";
THE PROBLEM:
In case of AG failover, driver is not trying to re-connect to the AG Listener name. Not sure how to make it work.
Is this supported in SQL Server 2012 ?
Thanks,
Krishna.

Hi Sean,
Thanks for your answer.
I looked at the link earlier, but it was not very clear that, whether the mssql jdbc driver will automatically re-connect to AG Listener name in case of failure of Primary replica which will result in Multisubnet failover. Pasted the confusing statements
from the link
http://msdn.microsoft.com/en-us/library/gg558121(v=sql.110).aspx.
Also, because a connection can fail because of an availability group failover, you should implement connection retry logic, retrying a failed connection until it reconnects.
Connecting With MultiSubnetFailover :
During a multi-subnet failover, the client will attempt connections in parallel. During a subnet failover, the Microsoft JDBC Driver for SQL Server will aggressively retry the TCP connection.
Thanks,
Krishna.

How to change SQL Server security groups name after server rename?

A Windows 2003 server has been renamed from LAMDAMIRROR1A to LAMDAMIRROR2A and the following
sql has been run in SQL Server 2008 R2 on the server :
exec sp_dropserver 'LAMDAMIRROR1A'
exec sp_addserver 'LAMDAMIRROR2A','local'
However, although everything appears ok, the 5 Windows 2003 Groups (automatically created by
the SQL 2008 R2 Install) still contain 'LAMDAMIRROR1A' in their name. Does this matter ? Can the Windows Groups be just renamed (right click , rename) or will this cause problems ?
The Windows Groups are :
SQLServer2005SQLBrowserUser$LAMDAMIRROR1A
SQLServerDTSUser$LAMDAMIRROR1A
SQLServerMSSQLServerADHelperUser$LAMDAMIRROR1A
SQLServerMSSQLUser$LAMDAMIRROR1A
SQLServerSQLAgentUser$LAMDAMIRROR1A
There are also Registry entries containing the old 'LAMDAMIRROR1A' name. Does this matter ?
Should this be changed ?
eg.
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\100\Machines\OriginalMachineName.
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Services\Report Server\GroupPrefix.
My Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\printers\Microsoft XPS
DocumentWriter\DsSpooler\serverName.
etc

Hi,
If you have executed the sp_dropserver and sp_addserver in SQL Server 2008 R2, we need to verify if you renamed the SQL Server instance successfully. You can select information from @@SERVERNAME or sys.servers to verify if the renaming operation is completely
successful in SQL Server Management Studio (SSMS). If yes, whether you change the registry entries containing the old 'LAMDAMIRROR1A' name or not, there’s no impact on SQL Server Services. For more details, please review this article:
How to: Rename a Computer that Hosts a Stand-Alone Instance of SQL Server.
In addition, if you must rename the windows groups, you can just right-click the group in Computer Management/System Tools/Local Users and Groups/Groups and rename it, or you can create new groups with new names, for more details, please review this article:
Manage Local Groups. If there are some issues regards the Windows, you can post the question in the Windows Server forums at
http://social.technet.microsoft.com/Forums/windowsserver/en-US/home?category=windowsserver . It is appropriate and more experts will assist you.
Thanks
Lydia Zhang

Backup Maintenance Plan on SQL AlwaysOn Availability Group Secondary Read-Only node

I have 3 node SQL 2012 AlwaysOn Availability nodes with the 3rd node as Read-Only.
The backup job within SQL Maintenance plan is failing with the following error:
Failed:(-1073548784) Executing the query "declare @backupSetId as int
select @backupSetId =..." failed with the following error: "Cannot open backup device 'C:\\SQLDBName_backup_2014_06_08_170156_9292095.bak'. Operating system error 2(The system cannot find the file specified.).
VERIFY DATABASE is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
I have verified the SQL AlwaysOn Backup preference to be "Prefer Secondary"
Is there any special steps/settings I need to do to setup and run the backups using maintenance plan in SQL AlwaysOn?

Hi,
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Thanks.
Tracy Cai
TechNet Community Support

SQL Server AlwaysOn Failover threshold and Lease Timeout

Hi experts,
I found each time when I were building/restoring another log shipping(standby) server. It would cause ERR [RES] SQL Server Availability Group: [hadrag] Failure detected, diagnostics heartbeat is lost(in cluster log) and A connection timeout has occurred on a previously established connection to availability replica 'DL980-4' with id(in errorlog). I google and find a document (http://download.microsoft.com/download/0/F/B/0FBFAA46-2BFD-478F-8E56-7BF3C672DF9D/Troubleshooting%20SQL%20Server%20AlwaysOn.pdf ) indicated that “This may be a performance issue”. I run restore database and AlwaysOn synchronizing on the same 10GbE link at the same time.
Should I increase
leaseTimeout from 20000 to 100000 and
HealthCheckTimeout from 30000 to 300000?
Does it work to prevent unnecessary failover.
Please refer to
(http://blogs.msdn.com/b/psssql/archive/2012/09/07/how-it-works-sql-server-alwayson-lease-timeout.aspx )
parag
10-18-2013 3:19 AM
Hi Denzil
we seem to see lease expires very frequently when the server is under very high cpu pressure .. our failure condition level is 1
is it possible to prevent this situation . the problem is when lease expires,all the current connections seem to be dropped . wondering if there is a way to prevent this ..
Also is it possible to affitinize the always on health check process to a particular core
Thanks for your help!

Hi Dennis
Should I increase
leaseTimeout from 20000 to 100000 and
HealthCheckTimeout from 30000 to 300000?
Does it work to prevent unnecessary failover.
1. you can increase the timeout parameter, but when the fail-over time slight delay will be there (its a work around solution)
2. You may require to check the Network connections. (Cluster Heartbeat & public network)
3. Have you update the latest patches of OS & DB?
4. If possible raise the ticket to Microsoft. they may give some update for Cluster resource update based on your issue
Regards
Sriram

SQL 2014 Linked Servers with Availability Groups

Good afternoon All. Hope your well. We have SQL 2014 Availability group setup over multiple Subnets.
So basically Instance A(In Primary DC), and Instance B (Secondary Replica, in secondary DC), with AG1 (Availability Group)
When I connect to the instance Directly (using SQL management Studio), and attempt to create a linked Server to another SQL 2014 instance (Instance D, Both use the same Service Account), I am able to successfully connect, and run query on the Linked Server.
However when I connect to the Availability group, I attempt to open the linked server (to Instance D) and receive the following error:
Login Failed for User 'NT Authority\Anonymous Logon'
This above only happens when I connect to the AG1, and not the instances directly. I have given the Service account permissions to Read and Write its own SPNs (Using ADSI Edit). Researching this people have stated to add the Availability Group Name as an
SPN to the Service account;
Setspn -A MSSQLSVC\AG1.mydomain:1433 mydomain\ServiceAccount
However, Im a little unsure at this stage, should the port in the above command reflect what the AG1 endpoint ports are? As I have done that (as well as trying port 1433), and unfortunately the error still happens. Your assistance would be appreciated,
kind regards,

Hi Nsaneone,
>> Setspn -A MSSQLSVC\AG1.mydomain:1433 mydomain\ServiceAccount
>>However, Im a little unsure at this stage, should the port in the above command reflect what the AG1 endpoint ports are?
The port in the above command should reflect the port which the availability group listener is listening on, but not the endpoint port.
>> Login Failed for User 'NT Authority\Anonymous Logon'
According to the error message, it always occurs when the Kerberos authentication fails in SQL Server, there are proposals for you troubleshooting the issue.
1. Make sure that your service accounts have “Trust this user for delegation to any service (Kerberos only)” enabled in Active Directory.
2. Make sure that SPN’s are registered successfully for all SQL Server instances.
3. The server must be using TCP/IP or named pipes network connectivity.
For more details about the error, please review the following links.
http://mssqlwiki.com/tag/login-failed-for-user-nt-authority-anonymous/
http://blogs.msdn.com/b/karthick_pk/archive/2009/01/23/kerberos-authentication-in-sqlserver.aspx
Thanks,
Lydia Zhang

Alwayson Availability groups for a WSFC hosting mutliple SQL FCI's

Hello,
I have a question regarding SQL server FCI's and alwayson availability groups.
Today I have a customer running a 2 node WSFC hosting 9 different SQL FCI's.
Plan is to introduce on this setup SQL alwayson availability groups one per SQL FCI.
Per SQL FCI, running on the 2 node WSFC, we are planning to introduce a dedicated
alwayson availability group with 2 replicas. On replica as primary linked with the
FCI and one replica as secondary on 1 extra node added to the WSFC.
Question i have is, is this a supported configuration?
Thanks in advance
Regards
Raf

This is a supported scenario. However, make sure that no FCI node will run a SQL Server instance acting as a replica. This means you cannot install a standalone instance on one of the FCI nodes and make it an AG replica. You also cannot configure another
FCI in the same WSFC to be a secondary replica in an AG. If you intend to configure AG per SQL Server FCI, you need to add another node in the WSFC and install a SQL Server instance on that node. This can be a SQL Server FCI (which means you need to add two
more nodes instead of just one) or a standalone instance. Also, having an FCI in an AG configuration means that you lose the ability to do automatic failover on the AG-level. This is because the FCI takes care of automatic failover on the instance-level.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

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 Server 2012 Migration

We are planning to migrate our existing environment to SQL 2012.
Existing Environment:
SERVER1
OS: Windows Server 2003 Standard Edition
SQL Server 2005 Standard Edition
2 Node Active/Passive Clustering With Transactional Replication
Number of Databases -> 2 (80 gb each).
Now how to migrate above environment to SQL 2012 on Windows 2012?
After migrating how to implement Log-shipping in above enronmnment.

log shipping doesn't support automatic failover. It requires a manually effort to fix in such cases.
You need to share the log file location as a clustered resource which is part of the SQL Server cluster group so that its availble to secondary database.
Because of this problem its always recommended to use cluster with database mirroring. Refer the below article
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/c55e1bbd-5b6f-4961-8e69-3de9ef4fb75f/use-db-mirroring-or-log-shipping?forum=sqldisasterrecovery#1bb9926e-1b39-47ad-9fe9-351d0fbaaf9f
But this is not the case with replication, The replication will fail during the failover and start it's operation once its back online.
Refer the below articles for more information
http://technet.microsoft.com/en-us/library/ms151799.aspx
http://www.mssqltips.com/sqlservertip/2337/sql-server-2008-high-availability-options/
Since you are moving to SQL 2012, try to work on alwaysOn High availability groups.
http://technet.microsoft.com/en-us/library/ff877884.aspx
-Prashanth

Not able to download CTP4 or CTP3 on sql server 2012

Because of download link not working of ctp4 or 3 , i am unable to download and getting error of compatibility of reporting service edition with sharepoint.
Please help me to download !!

Hi MohitJainMJ,
Many software products use a variation of this process and often have multiple public milestone releases (Alpha, Beta, Release Candidate, Final) with the product quality increasing with each milestone until the release criteria is met. The variation within
the SQL Server product group is:
A deeper engagement with the right partners earlier in the planning and stabilization phases to get the requirements, design, and quality right
Grouping the features into multiple "sets" that have a correct logical sequence as well as balance the effort across all the component teams to finish the "set" around the same time
Each "set" is called a Community Technology Preview (some use Customer Technology Preview)
The release criteria for the CTP are the same as final release (some corner case bugs may be deferred to a later CTP)
A CTP (Community Technology Preview) just like a "Release Candidate" quality release with the ability to change the design and improve the test suite. As Olaf said, as soon as the RTM is available, all CTP download are removed.
The following blog about Community Technology Preview (CTP) is for your reference:
http://blogs.msdn.com/b/sqlphp/archive/2010/06/14/what-is-a-community-technology-preview-ctp.aspx
If there are any other questions, please feel free to ask.
Regards,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Finally! T-SQL Reference for SQL 2014 available for download!

With a mere delay of four month since the release, it is now possible to download the T-SQL Reference for SQL 2014 for your local copy of Books Online. Due to some reorganisations of the reference material on MSDN, the language reference was misisng from
the initial download.
To get the reference, you need to use Manage Help Settings, which you find the SQL 2014 program group. Select the option "Install content from online". Once all information has been loaded, scroll down to the SQL Server 2014 group and you will
SQL Server Language Reference with an Add option, which you should select.
Now, SQL 2014 uses Help Viewer 1.0, which is very poor, and versions 2.0 and 2.1 which ships with VS 2012/2013 is much more pleasant to use. Thanks to SQL Server MVP Simon Sabin, you can get the SQL 2014 into Help Viewer 2.x in this way. Go to
https://helpviewerredirector.codeplex.com/
save the file to a directory. Open a command prompt in that directory and run "HelpViewerRedirector download". Then in Help View, go to manage settings, and select install content from disk. Browse to the folder and select the files you want to see
in Help Viewer 2.1.
Erland Sommarskog, SQL Server MVP, [email protected]

To get the reference, you need to use Manage Help Settings, which you find the SQL 2014 program group. Select the option "Install content from online". Once all information has been loaded, scroll down to the SQL Server 2014 group and you will
SQL Server Language Reference with an Add option, which you should select.
If you need more detailed instructions on this part, see the comment from Microsoft added today (2014-08-01) to
http://connect.microsoft.com/SQLServer/feedback/details/859047/t-sql-reference-and-xquery-reference-missing-from-downloadable-version-of-bol-2014
Erland Sommarskog, SQL Server MVP, [email protected]

SQL Server Availability Groups

Similar Messages

Maybe you are looking for