New answers tagged availability-groups
You can setup 2 different availability groups and add databases accordingly, so that way you can manage it separately.
In terms of wanting to get input from other people about their experiences, I can share about our use of Log Shipping in our Production environment. We use native Log Shipping and perform DR tests once a quarter for our critical systems. This involves failing over to the Secondary, pointing the application(s) at it, and testing that everything works as ...
connect your Named SQL Instance 2 listener like below "listener name\static port" or "listener name\Namedinstance" then Instance 2 will point your named instance database.
It looks like the answer is Server 2012 R2. 2012 R2 only includes the file share when there are an even number of nodes. So if DR goes offline then the file share will be included in the quorum until such time that DR comes back online. It also looks like from testing that if you gracefully shutdown connections on secondary's then the primary stays up. So ...
When you create a mirror of the database the "trustworthy" flag is set to false by default. And you need to sync the SID of the dbo on each side (I don't understand how this works for the SA user. Need to study more. To resolve the issue I failed the database over to the secondary node. Set Trustworthy to True. After that I attempted to run the Procedure ...
Top 50 recent answers are included