How can we configure three node active active sql cluster for 5 instance in sql server 2012
↧
3node active active sql cluster
↧
SSISDB in Availability Group: Issue when adding second SSISDB of Windows Server FailOver Cluster in Availability Group
Context
I have followings:
- 2 Windows Server FailOver Cluster with 2 SQL Server 2016 instances in each one (DEV and PROD)
- 1 Availability Group AGDEV that contains DEV databases of the 2 DEV instances
- 1 Availability Group AGPROD that contains PROD databases of the 2 PROD instances
Unsolved issue
DEV SSISDB has been added in the AGDEV Availability Group and this ended up successfully
I attempted to add PROD SSISDB in AGPROD and this ended up with following error (when executing “Enable Always On Support”):
Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.
I found a workaround describing how to manually add second instance of SSISDB in Availability Group (https://www.sqlservermigrations.com/2018/08/adding-an-integration-services-catalog-to-always-on-availability-groups-subquery-error/)
I did the failover while PROD SSISDB package was running. As results, SSISDB packages are no more running (I have a database with status “In recovery”)
Question
Is there any native SQL 2016 means to set multiple SSISDB in the same Windows Server Failover Cluster? If no, is this feature implemented in SQL 2017 or planned in future releases?
Thanks in advance,
Abenico
↧
↧
Firewall Port for Distributed Availability Group in Microsoft SQL Server 2017
Hi,
Please help to get the information related to firewall port require for Distributed Availability Group for Microsoft SQL Server 2017.
I have site with DC and DR.
Regards
Param
↧
Can the nodes of a fail-over cluster instance reside on two geographically separated windows hosts. If yes, what are the challenges
Can the nodes of a fail-over cluster instance reside on two geographically separated windows hosts. If yes, what are the challenges.
The requirement is to make use of just standard edition. So, always on availability groups is not an option.
Please suggest.
↧
DR drill for Always-On
Suppose I have 3 nodes always on
Primary node1 : Sync
Secondary node2 : Sync
Secondary node3: Async
For DR drill (Not actual DR) , manual failover to node3 . And read-write on node 3 and read-only on node 1/2
So this will affecting the production as this is read-only. !!!!!
Any method to achieve both node1 / 2 and node3 are read-write ??? Need reconfiguration of the AG ?
↧
↧
SQL Server 2012 AG configuring without domain
If I deploy Windows Server 2016 and install SQL Server 2012 on that servers, can I configure AlwaysOn Availability Group for workgroup cluster environment?
↧
Cluster resource not moving to secondary node
Hi ,
we have SQL AlwaysON availability group configured for set of dbs. Its a 2 node cluster. When we did the manual failover of dbs it perfectly works fine, I can see in cluster failover mgmt that resource moved to another node which is on Azure .
We wanted to test real DR scenario, where in source DB server was brought down intentionally . This somewhat confuses the cluster and it was failing to come online on another node.
Also tried forcefully bringing secondary dbs to online status, none of the commands were working.
Alter database with recovery
Alter database set partner OFF
None of them worked.
Can someone help me here ? Am I missing something ? Isnt the cluster supposed to work by simply moving resources to secondary node??
Regards
Thahif
↧
SQL Server 2016/2017 Standard AlwaysOn and DR
Hi,
Is it possible to configure AlwaysOn Failover Cluster and Disaster Recovery using SQL Server 2016/2017 Standard Edition?
Angelo
↧
Re-configuring network hardware in SQL Cluster and High Availability Cluster
Hello All,
This is a backup/cluster/SQL resource question. My expertise is in general server administration and backups. I understand enough about SQL to give the appearance I know what I'm talking about, so please excuse any incorrect terminology.
Currently, our agent based backup software calls to the SQL Cluster IP (or AGL IP, if enabled) to initiate the backup stream. This means that all backup traffic traverses the 1Gbps NIC on the current-active node. This works - but it's slow and
impacts prod. We acquired 10Gbps NICs and installed them to the physical cluster nodes. The plan was to leave Prod traffic on the 1Gbps NIC, and then force backup traffic over the 10Gbps NIC.
Due to limitations of the backups software, there is no way to force the backups to use those 10Gbps NICs - because they're not associated with the Cluster IP - which is how the backup software initiates the stream.
General setup of our SQL Environments:
Standard Cluster (no AGL) - 2 physical nodes; Win2012R2; SQL2014; Cluster IP and node IPs(1Gbps NIC) are on the same subnet
AGL Clusters - comprised of a standard cluster (cluster IP) and a SQL node at offsite DR location (10Gbps WAN) AGL IP resides in same subnet as Cluster IP and cluster node IPs.
*note - If these were stand-alone SQL servers, this wouldn't be an issue for the backup software. The clustering is what creates the issue.
After some internal discussion and discussions with the Backup Vendor, we're looking to simply take the IP from the 1Gbps NIC and assign it to the 10Gpbs Fiber NIC - Then disable the 1Gbps NIC. The result will be all prod and backup traffic using the
10Gbps connection. Of course, we'd do this in a controlled manner - stopping SQL services and applying to passive nodes, etc.
The questions/concerns: Is this a supported "upgrade?" What kind of trouble should I expect if I do this? Will SQL balk at this change?
Apologies if I've left this vague - I tried to keep it simple and to the point. Thank you for reading.
↧
↧
FCI in Primary and Always-on in DR
May I know what license is required for the following HA/DR design ? Standard or Enterprise ?
↧
Multiple Instances and AlwaysOn Availability Groups
Hello every one,
In my scenario, I have two servers in each of them two SQL server instances
(Server 1: Instance 1 and Instance 2, Server 2: Instance 1 and Instance 2)
I created an always on groups between the instances like this:
- Instance 1 from Server 1 with Instance 1 from server 2 : AlwaysOn Group 1
- Instance 2 from Server 1 with Instance 2 from server 2 : AlwaysOn Group 2
and I have create a two listeners Listener 1 for : AlwaysOn Group 1, and Listener 2 for : AlwaysOn Group 2
the problem is when I try to connect with the Listener 1, it connects me to the AlwaysOn Group 1,
but when I'm trying the Listener 2 it also connects me to AlwaysOn Group 1 not to the alwayson group 2
I did not understand what's wrong with this.
Thank's for help me
Have a good day.
↧
In-Place Upgrade of SQL cluster always on 2016
Hi all,
I have a AlwaysOn 2016 MSSQL Two node cluster on Windows 2012 R2 Operative System.
I need upgrade the nodes to Windows 2019 Server (In-Place). No upgrade required for SQL. Only OS.
In-Place upgrade of only Operative system is a supported scenario?
Best Regards.
↧
SQL Server Cloud Witness Configuration
I'm trying to configure SQL Server cloud witness but the option is disable in the Quorum Witness wizard. SQL Server version is 2014 SP3. Why is the "Configure a cloud witness" option disabled? What can be done to enable that option? Please help!!
Thanks!!
↧
↧
Different ways of doing the same this as Always On AG but for SQL STANDARD Edition
Hi guys im writing right now because im in the brink of staring a new proyect in my company wich consist in to create a non dissaster architecture for the database that we are using in my company...
The architecture will consist in do a "mirror" server with a virtual machine that will be paired with a asyncronous server that only will "copyng" the info of the mirrored server...
Making it simpler:
Server 1 (the one we use) <=> Server 2 (The same in a Virtual Machine) <= Server 3 (Pshysically in a different place only "copyng" the data of Server 2 and is a physical Server too).
The thing is that we are wanting to make some kind of way that if the 1st Server went down the next one available could have all the data up and running with all the information that has the 1st one and so the 3rd is making a back up of the 1st or 2nd Server so if the VM or the principal server fails we have in another place a server that has all the data of our principal database. This could be possible or we are doing some fuzzy things in here?
I was reading that this could be possible if i use AlwaysOn Availability Groups features to do this but the problem is that in my company we use Sql Server 2012 Standard Edition and we cant afford an Enterprice Edition License.
My question is if its has a way to do the architecture that i present in this topic with the tools that provide Sql Server Standard Edition.
I hope you can help me to solve this issue because im really new in this kind of things...
Thank you very my in advance.
PD: Sorry for my English im not a Native English user.
↧
RPO/RTO in a AlwaysOn cluster
Hi. Am I correct that decision whether to host end user's application database on a AlwaysOn cluster is largely driven by user's Recovery Point Objective (RPO) and Recovery Time Objective (RTO)? Consider a typical three node cluster with 2 x HA nodes
and 1 x DR node? When we discuss RPO with user, that is the ability to recover to the last Full and/or tran log backup, correct? When we discuss RTO is that the time it takes to failover to secondary HA node (i.e., near real time), or is it time
to recover to DR node (which by definition would be longer and experience data loss)? Thanks for helping me grasp the distinctions.
↧
SQL Server 2014 SP3 Cloud Witness Configuration
I'm trying to configure SQL Server cloud witness but the option is disable in the Quorum Witness wizard. SQL Server version is 2014 SP3 running on Windows 2016 Server VMs. Why is the "Configure a cloud witness" option disabled? What can be done to enable that option? Please help!!
Thanks!
↧
3node active active sql cluster
How can we configure three node active active sql cluster for 5 instance in sql server 2012
↧
↧
Recommended way of running DBCC commands in a 24/7 highly available performance sensitive DB with Always on AG?
Hi All,
What would be the recommended way of running a DBCC command in a highly performance sensitive 24/7 Always on AG environment?
I believe physical_only will not help us (as it is a highly performance sensitive application)
Archtecture:
2 Nodes with synchronous replica in primary DC and 1 Node with A-sync replica in secondary DC.
SQL Server 2016 (SP2)
Windows Server 2016
Regards, Ashif Shaikh
↧
Host Name changes in alwayson
Hi Team,
We have a requirement host name changes from windows side for the configured servers for sql alwayson.
Can I have some inputs-how this can be achieved ,as nodes are part of cluster,cosider 2 node with sql server 2016.
Regards, S_NO "_"
↧
Download SQl Server tablediff.exe
When I checked C:\Program Files\Microsoft SQL Server\90\COM\, I am not able to find
Tablediff.exe
Can you please let me know from where I can copy this utility to COM SUBDIRECTORY?
As far as my understanding is this is only installed if Replication components are installed, and they are not installed on non cluster servers, in the future they may not even be installed on cluster servers.
So I want to know how I can install this toll when it is not available in C: drive
Any help regarding this will be appreciated.
Thanks
↧