1

I am interested in using Sql Server 2016's upgraded Always On features.

But my DBA has said that these features work better with Windows Server 2016. He suggested waiting for Windows Server 2016 to release before we start using those features.

The only feature that I am seeing that needs Windows Server 2016 is if you are running across domains. But I would be running on a single domain, so I am not worried about that.

Is there anything else in Sql Server 2016 that wants Windows Server 2016 to work well? Or would I be fine with a Windows Server 2012 R2?

2

Is there anything else in Sql Server 2016 that wants Windows Server 2016 to work well? Or would I be fine with a Windows Server 2012 R2?

There are a slew of new and updated features in Windows Server 2016. Unless any of them are specifically important to you, for example enhancements to storage spaces and CSV storage, I wouldn't specifically call out a need to wait for it.

This will depend, though, on how nice of a system administrator you are. Once Windows Server 2016 comes out, will you build a new system to allow the DBA to migrate?

Maybe you'll want to wait for supportability reasons (granted 2012R2 is still mainstream support)?

There is nothing inside of SQL Server that is really dependent upon Windows 2016 with AlwaysOn. Yes, you have greater flexibility with things like gMSAs, AD-less clusters, etc., but nothing specific inside of Windows that SQL Server hooks into.

Having said all of this, I'd either wait for Windows 2016 to come out or build a 2012R2 cluster for the AlwaysOn Availability Groups and know that we can do a rolling OS upgrade after Windows 2016 comes out. It's double work but you get your cluster now (vs waiting) and can upgrade the same cluster with rolling OS upgrades (so double work).

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.