New answers tagged availability-groups
Hi I got solution to this problem. What I did is go to SQL Server configuration manager and go to Instance1 of DR site and remove port 1433 from IPAll. Restart both the instance at DR and now it will point correctly. Please try and let me know. Khaled Bakhtiar.
No, auditing only reflects the one server that is running the audits. If you want to centralize audit results from multiple servers, you'll need to combine that data yourself. Keep in mind that if someone really wanted to circumvent this, they'd simply add another replica on any server they want, do the querying they need, and then destroy the replica. An ...
These errors mean you had a connection timeout. The subsequent messages are a result of that. In a multi-subnet environment, each AG will have an IP address in each subnet and be registered in DNS. The DNS server returns multiple IP addresses when queried. Only one will be online. SQL tries all the ip address, serially, until connection is established. ...
The fastest way would be to create a cluster an join your current stand alone server to the cluster as a new node. Set the database to full recovery model, take a full backup and a transaction log backup and restore them to the instance on the other node with norecovery. If you have a good full backup (most recent), it would be possible to set the recovery ...
Does this mean I will need to do a full backup on primary if a restore of the transaction log is required? NO -- You can add t-log backups to a restore of a COPY_ONLY backup
The first graph of that link doesn't show the data latency between two servers. Instead it shows : SQL Server:Database Replica --> Transaction Delay (GREEN COLOR) / SQL Server:Database Replica --> Mirrored Write Transactions/sec (RED COLOR) And then it says that if you want to get the data latency between two servers, you have to divide both values, but ...
Top 50 recent answers are included