I guess I'm different... perhaps, a lot different. AG is nice and all but, to me, AG has NOTHING to do with DR and vice versa. To me, DR is what happens when all your AG stuff has failed regardless of what and how many forms it may be simultaneously present in your systems and sites you have systems in. To me, DR is when your computers are unable to help you conduct business. And, don't forget, the computers and the data that lives on their disk systems mean absolutely nothing if you can't use them for their intended purpose. That means if you or your customers can't get to them, it's also a disaster.
Heh... I know a whole lot of people are getting ready to argue with me especially when I say having stuff in the cloud (although helpful), is not a adequate DR plan. Before you do, remember the not so distant past when no one could log into O-365... and it happened not once but twice and in a fairly short time span. People say that wasn't a disaster because "it didn't last all that long" but it absolutely was a disaster until people were able to get back in and get back to normal business. Some had all their junk in a system they could no longer log into for hours.
Things like AG are nice because they can help avert what would normally be a disaster but it's NOT DR and if AG is the only "plan" you have for DR, then you're going to find yourself in deep Kimchee sometime, possibly in the not so distant future.
is pronounced "ree-bar
" and is a "Modenism
" for R
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
"If you think its expensive to hire a professional to do the job, wait until you hire an amateur."--Red Adair
"Change is inevitable... change for the better is not."
When you put the right degree of spin on it, the number 3|8
is also a glyph that describes the nature of a DBAs job. 😉
How to post code problems
Create a Tally Function (fnTally)