As I understand it sql 2012\2014 supports two basic AlwaysOn architectures:
1) Always on Availability Group
2) Always on Fail-over Cluster Instance
Around my place ALL production DBs are expected to be restored ASAP after a disaster so I don't see how option 1), where the unit of failover is a DB or DB(s), is that useful. We would need to create jobs, logins, etc (i.e. things outside of the database) all under the watchful eye of the IS Managers and a clock. During that time period production would be down. It seems that option 2) is the most likely way for us to "quickly" recover a full, working copy. of production before the failure. Do you agree?
TIA,
edm2
P.S. In fact, option 1 seems like a nuisance to me as it, possibly, requires Administrative overhead whenever a new DB is created. (Hope I don't forget to include a DB in an availability group that I wanted to be in there.)