May 16, 2013 at 10:10 am
I am planning for the update from SQL Server 2008 R2 to SQL Server 2012. I've read some accounts of differences between running Always On and WSFC on the older version of the OS vs. the newer.
NB: I *am* trying to get a comment on this directly from Microsoft, but they're not being responsive so far. I am alo taking a Microsoft training course that purports to cover HA, but the references are superficial re this question.
The concerns revolve around updates to the database(s) on the servers in an Always On Availability Group.
Are there substantial differences between the steps to patch SQL Server 2012 running on multiple machines supporting multiple DB's when it's running on Server 2008 vs. Server 2012?
Our primary enterprise application, which would *definitely* be in an Availability Group, gets 4 business critical updates a year. Two of those are often taken under operating season pressures such that I don't want to add complexity that could be avoided. Are there substantial differences between the steps required to install and promulgate a new DB version under different versions of the server OS?
Note that, in all cases, the Availability Group will host at least two databases, but that only one of them will require major updates.
Does anyone have enough hands on experience with AlWays On and WSFC to venture ideas? Any suggestions on where (official Microsoft?) sites/blogs/????) I might try for an authoritative answer?
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply