Tag Info

New answers tagged

2

Native functionality, no. AlwaysOn Availability Groups have the containment of database. Server objects (Agent jobs, logins, alerts, etc.) just simply don't play a HADR role with availability groups. Whenever you run into the need to ensure that server-level objects exist on all replicas, or that they only execute on [particular_replica] then you will ...


0

If the secondary is up and running, when the log block is flushed to disk (either because it is full or a commit), the record gets pushed to the log writer on the primary and to the log scanner (log reader) process on the primary simultaneously. Then the log scanner communicates with the secondary and the secondary then pulls the transaction from the log ...


1

There is no 'cache'. Is just log. The primary log is the messaging framework. Primary writes into the log file, and secondaries receive a copy. When connected the secondaries receive the log immediately and the primary is free to reuse the log. When disconnected the primary is forbidden from truncating the log and must append to it. When reconnected the ...


1

The secondary databases are just "clones" of the primary, so you cannot enable it on just one node. The way to do it is actually to enable encryption on the primary, then it will replicate by itself if all is well (if you copied the certificate on the secondary nodes). However, you should really look into MSDN and practice in a virtual lab before doing ...


0

There are several steps to configuring a server to accept ReadOnly traffic. The following link walks you through it, http://msdn.microsoft.com/en-us/library/hh710054.aspx ,but basically you need to configure each server in the AG and then set up the routing for each. Here's the T-SQL involved: ALTER AVAILABILITY GROUP [AG1] MODIFY REPLICA ON ...


2

Listen to your adviser. By restoring a backup, you are essentially replacing the database schema and data. You will need to turn synchronization off, remove the DB from HA and perform the restore on the primary and replica, leaving the replica version in a restoring state by using WITH NORECOVERY. Once your backup is in place, put the DB back into HA and ...


2

Your proposed setup looks okay to me; as long as both nodes are in the same domain, that should work fine. What you need to resolve is the ability for each server to get to the other on the configured ports. It sounds like 5023 is being blocked by a firewall rule of some kind, or that you haven't used the same port consistently throughout the configuration ...


0

you cannot install 2 SQL Server instances to the same WSFC node and have one instance host a replica for on Availability Group and the other instance host a replica for a different Availability Group. Instead, you would have a single SQL Server Instance on the WSFC node that would participate in both of the Availability Groups. Possible solution Node1 ...



Top 50 recent answers are included