Hello,
Typically how long will the SQL Instance be unavailable during a failover event occuring in active/passive environment.
My guess was 15 seconds, am I correct? During that time, if a Job is running , will the Job fail ?
Thanks,
Veena Srinivas
Hello,
Typically how long will the SQL Instance be unavailable during a failover event occuring in active/passive environment.
My guess was 15 seconds, am I correct? During that time, if a Job is running , will the Job fail ?
Thanks,
Veena Srinivas
hi all
we have two servers that are setup with sql server 2016 clustering (high availability)
i have very big log file size , so how the best way to shrink or reduce my log fie to reducing the size for total database file
Hi
I'm trying to move sccm databasde from stand alone server to always on availability group.
I'm sure that all SQL Configurations are done successfully. But I face the following error
Kindly advice
Thanks and regards
I have some query on the dynamic voting. I am having 4 nodes cluster, windows 2016 and sql 2016. with a fsw.
there are two sites, PROD and DR, each site has two nodes, (nodeA, nodeB)Prod (nodeC,NodeD)DR
It's a samesubnet multisite stretched cluster
FSW is owned at Prod,SQl server resource is currently own in nodeA, And Preferred site set to Prod.
Now I want to examine the Dynamic vote of each node under the following case
1. nodeC in DR site down
2. nodeB in Prod is down
3. both nodeC and nodeD is down
4. nodeA is down
5. Both nodeA and NodeB is down
Any one have an idea of the results dynamic vote ?
Hi All I have some questions on clustering . Here is the setting
1. SQL server 2016, windows server 2016
2. 4 nodes clusters + fileshare witness
3. Siteareness is enabled , and preferred site configured to node 1 and node 2, node 3 and node 4 are secondary site
The questions
1. will there be impact on the preferred node order when configured siteareness ?
2. and also node ID impact on the node voting ?
3. For the behavior or dynamic voting, I did a test: If I reboot any node on secondary site (for example node 4), active node on node 1, I checked the dynamic voting of node 4 become zero, and another node in primary site also become 0. So the question is, HOW cluster choosing WHICH node in a site to lower down it's dynamic voting ??
4. cross-site network failure question, what's the outcome of the following
- Crosssite link down, FSW on backup site, and sql instance owned currently at preferred site
- Crosssite link down, FSW on preferred site , and sql instance owned currently at preferred site
- Crosssite link down, FSW on backup site, and sql instance owned currently at backup site
- Crosssite link down, FSW on preferred site , and sql instance owned currently at backup site
We do have SQL Server 2016 with couple of databases configured with AlwaysOn with 2 secondary replicas. We would like to add another replica in SQL 2017 and test it with that once everything looks good, we will start using SQL 2017 and decommission the SQL2016. In case of issues, we will go back to SQL2016.
Is this supported? SQL 2016 always on with SQL2017 as a secondary replica.
I remember seeing in couple of places mentioning it is possible, some places it says not possible, sql version has to be same. So got confused.
Thanks
Hello All,
I've been doing some research on availability groups in SQL, however have come up with some questions that I cannot find answers to in the documentation.
>>>>>CONFIGURATION SETUP<<<<<<
I have a 4 node sql server setup with WSFC. No shared storage, using Cloud witness as quorum. Two nodes exist in Azure (subnet A) and two nodes exist on prem (subnet b). Subnets communicate via VPN between azure and on prem and all nodes can communicate with each other. Cluster is up and healthy. (AZSQLCLUST NetBIOS name 10.20.0.254)
In azure I have AdventureWorks configured on NODE1 in azure. I setup an Availability Group (ADWKAG1) to create a secondary synchronous replica of AdventureWorks on the NODE2 in Azure. The future intent here is to setup an Asynch copy of this database to the on prem nodes (they are there for forced failback only).
I've setup a listener (ADWKAG1-ls), it is configured to use the same IP as the cluster name 10.20.0.254.
>>>>>QUESTION<<<<<<<
If I build another availability group setting up a new Database (AdventureWorks2) on NODE 2 in Azure, with a Synchronous replica to NODE 1 in azure. Do I need another Availability Group listener or can I use the listener that I've created already?
I know each AG needs a listener, but it doesn't say whether that listener needs to be unique or not.
Thanks for the help
r/
john
Good Morning Experts,
I have created 3 AGs. For 1 AG , I have created listener. Can i use the same listener for the remaining AGs.
Kiran
Hi Everyone,
I would like to know how the SQL AlwaysOn licensing work for the below scenario.
Scenario 1:
I set up two node cluster and created a two SQL Instances with one AG each.
Node A and Node B ( Each node has 2 physical CPUs )
SQL 1 and SQL 2
If I run SQL 1 on Node A and SQL 2 on Node B. Do I need to pay the license for both the servers/4 CPUs?
Scenario 2:
Set up Two node cluster and created one SQL instance with two availability groups.
Node A and Node B ( Each node has 2 physical CPUs )
SQL 1 with AG1 and AG2
Now If I run AG1 on Node A and AG2 on Node B. Do I need to pay the license both the nodes/4 CPUs?
Thanks.
Hi,
During a failover of SQL primary to the Secondary replica. Should there be no downtime at all?
When we failover to the SQL secondary, users were experiencing slight outage to the website.
Just wondering is this normal?
Thank s
Hi,
In the progress of tidying up the default domain policy, noticed that there are these 3 policies under Public Key Policies/Trusted Root Certification Authorities, when generate GPO report:
But, when Edit the Default Domain policy (tried it on Windows 7 PC, Windows Server 2012), there is no polices listed under Public Key Policies/Trusted Root Certification Authorities In fact there is no policies (none) listed in this section. Question: How can we edit these x3 policies? thank you |
Humayun
Hi!
I've just built a 2 node Azure 2016 HA always on cluster and its all working except for 1 thing. I can connect via ssms to both instances using the instance names, but the listener name (AG-TmProd) does not connect...
Im not sure what I've missed.. Any ideas?
Thanks,
Zoe
Hello,
We have created a SQL Server Multi-Subnet Clustering AG.
The problem is as follows:
We are able to have a db as primary on the subnet that was in place before this.
When we failover to the server on the 2nd subnet the failover fails.
We are unable to make a DB primary on the server of the 2nd subnet.
The databases are synchronized with no problem with the current configuration.
The error in the cluster manager is:
Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.
Any idea is greatly appreciated.
Thank you.
I have Windows 2016 Datacenter edition and SQL Server 2017 web edition
Please advise Can I use AlwaysON on this editions or not?
I am getting below error, I searched on Google a lot, however, I did not get any relevant solution on it.
Hi,
Existing situation:
setting on SQL instance data and logfiles on the same drive but different folders
data and logfiles in these folders
AG setup
New situation should be the data and logfiles folders on different drives and setting saved.
Is this possible and if so what are the steps to be taken?
I found that this is working via backup and restore and then relocate the files as needed. Hope the above can be done and is quicker.
kr
Marco