The first test of AlwaysOn in SQL Server 2012 is successful, but after testing to swing back again to your primary replica, you find out that automatic failover works only the first time. How come? Carla Abanes explains.
2014-08-28
7,981 reads
You have a new project that requires a primary database server in one building and secondary database server in another building to be configured as a Failover Cluster. What are the important points to consider for this scenario?
2014-06-25
3,008 reads
We have a SQL Failover Cluster Instance in our primary data center, and want to implement a second two node Failover Cluster Instance in our secondary data center. A new two node cluster located in our secondary data center was setup, but I could not create a new High Availability Group between the two failover cluster instances. What went wrong?
2014-03-07
3,721 reads
SQL Server 2012 AlwaysOn provides flexible design choices for selecting an appropriate high availability and disaster recovery solution for your application. This article looks at the common design patterns.
2013-12-11
5,345 reads
With SQL Server 2012 AlwaysOn Availability Groups, you can configure read-only routing and to automatically redirect the read-only workloads to a secondary replica after a failover. Can this be done using Windows PowerShell?
2013-04-17
2,105 reads
So I am using this new technology called Availability Groups that was introduced in SQL Server 2012. I have heard I can offload my backups to a secondary replica, but I am not sure how that works or how to configure those backups. Are there any limitations? Check out this tip to learn more.
2013-02-25
2,277 reads
SQL Server 2012 AlwaysOn Availability Groups provide a high-availability and disaster-recovery solution for you SQL Server 2012 environments. Replication has been around in SQL Server for quite some time and allows you to scale out your environment. Warwick Rudd explains how to join these technologies together.
2013-02-12
2,480 reads
SQL Server 2012 AlwaysOn Availability Groups provides a unified high availability and disaster recovery (HADR) solution that improves upon legacy functionality previously found across disparate features. Prior to SQL Server 2012, several customers used database mirroring to provide local high availability within a data center, and log shipping for disaster recovery across a remote data center. With SQL Server 2012, this common design pattern can be replaced with an architecture that uses availability groups for both high availability and disaster recovery. This paper details the key topology requirements of this specific design pattern, including quorum configuration considerations, steps required to build the environment, and a workflow that shows how to handle a disaster recovery event in the new topology.
2012-08-31
2,399 reads
This article discusses and demonstrates AlwaysOn Availability groups in SQL Server 2012, a new feature for high availability.
2012-08-28
9,937 reads
If you are trouble-shooting an AlwaysOn Availability Group topology, a study of the wait statistics will give a pointer to many of the causes of problems. Although several wait types are documented, there is nothing like practical experiment to familiarize yourself with new wait stats, and Joe Sack demonstrates a way of testing the sort of waits generated by an availability group under various circumstances.
2012-06-12
2,331 reads
By HeyMo0sh
As a DevOps professional, I’ve seen firsthand how cloud costs can quickly spiral out...
By Steve Jones
AI is everywhere. It’s in the news, it’s being added to every product, management...
By Vinay Thakur
RAG — Retrieval Augmented Generation. we have covered so far — embeddings, vectors, vector...
Hi, ssms is free here. I can think of other reasons to do this...
I've written some documentation on using different Markdown types of files on GitHub. It's...
Comments posted to this topic are about the item Not Just an Upgrade
I am doing development work on a database and want to keep a backup so I can reset my database. I make some changes and want to restore over top of my changes. When I run this code, what happens?
USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO USE DNRTest GO CREATE TABLE MyTest(myid INT) GO USE master RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACESee possible answers