Questions tagged [windows-server-2019]

The tag has no usage guidance.

Filter by
Sorted by
Tagged with
-2
votes
0answers
12 views

Upgrading Windows Server OS Failover Cluster and SQL Server Always On high availability [duplicate]

What are best practices steps when the Windows Server 2016 failover cluster machine hosting SQL Server 2014 Always On Haigh Availability (2 nodes and shared folder witness) and I need to upgrade ...
0
votes
0answers
12 views

SQL Server HA Design (FCI) - Windows Storage Replication - Test-SRTopology - Physical Memory Error - AWS EC2

I'm trying to set up AlwaysOn Failover Cluster Instance (Not Availability Groups) on 2 VMs(each on different AWS Availability Zone) in AWS-EC2 instances. To make this happen, I've to set up Windows ...
0
votes
2answers
34 views

Windows Server 2019 and SQL Server Backups issue?

I have an issue with SQL Server that is really driving me nuts so I wanted to ask if anyone has any suggestions. I have a program that does a daily backup of the SQL Server database. This has worked ...
0
votes
0answers
15 views

Windows Server 2019 non-owner node cannot see Cluster Name or IP

I am trying to build a SQL Server AlwaysOn Availability Group with 2 nodes in Azure. I have created 2 SQL Server VMs and Managed to create a Cluster with both Nodes as members of that cluster.  I ...
0
votes
1answer
139 views

SQL Server 2019 Always On using Distributed Network Name

We're running a couple SQL servers in Azure that are set up with an Always On availability group and Windows Failover Clustering. The servers are Windows 2019 and we're running SQL Server 2019. When ...
1
vote
0answers
49 views

Keep 2 instances of SQL Server synced [closed]

We want to set up a second instance/server of SQL Server such that both instances will be kept in sync. The reason is we need to separate some users and processes out to a separate server for business ...
2
votes
0answers
123 views

SQL Browser Service Stops After One Minute

I am encountering an issue with the SQL Browser service where the service will start, run for around 60-90 seconds and then stop. No error is logged, the event logs show three informational entries: ...