Right. Server Datacenter. Knew that. Habit to type Enterprise. The rest is stuff I'm trying to figure out, since I haven't played around much with real SQL Server since the 2000 edition, and not even much with Express since then.
We are planning a 2-node cluster, so it sounds like Windows Server 2016 Standard and SQL Server 2016 (2017?) Standard will do exactly what we want. We do have restrictions in our EA regarding the number of licenses for SQL Server (2), and we also want to reduce the clutter of old versions of SQL Standard and SQL Express scattered amongst our servers. I intend to deploy on our VMware cluster (vSphere 6.0 Standard, 6 nodes, backed by a Nimble SAN), unless testing indicates it's a bad fit. Kurt On Thu, Aug 17, 2017 at 8:53 AM, Michael B. Smith <mich...@smithcons.com> wrote: > I think y’all are confusing yourselves. Words mean things. > > > > For the purposes of this discussion, there is no such thing as “Windows > Server Enterprise”. > > > > The editions are Windows Server Standard and Windows Server Datacenter. > Since Windows Server 2012, both Standard and Datacenter include Windows > Failover Clustering (WFC). (So does Nano Server in Windows Server 2016, but > I digress.) > > > > There ARE features that a SQL installation may want to use, such as SOFS > (Scale-Out File Servers), that may require Windows Server Datacenter; but > WFC itself does not require Datacenter. > > > > SQL Server also comes in two editions, for the purposes of this discussion. > They are Standard and Enterprise. > > > > SQL Server Standard supports WFC for EXACTLY two nodes (this is also called > SQL Server Always On Failover Clustering). No more nodes than two. SQL > Server Standard does NOT support Always On Availability Groups. > > > > SQL Server Enterprise supports WFC for the operating system maximum number > of nodes. SQL Server Enterprise supports Always On Availability Groups. > > > > Define the deployment plan FIRST, then you can determine the necessary > software. Alternately, the licenses you have may restrict your deployment > plan. > > > > Regards, > > Michael B. > > > > From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] > On Behalf Of D R > Sent: Thursday, August 17, 2017 11:00 AM > > > To: ntsysadm@lists.myitforum.com > Subject: Re: [NTSysADM] A new task for me - setting up a SQL Server cluster > on vSphere 6.0 > > > > According to the Techs and Sales people in my org, it seems that they did. > > > > They are telling me that every SQL Clustering needs Enterprise on 2016, or > it's a 'no go'. > > > > Daniel > > > > On Thu, Aug 17, 2017 at 9:22 AM, Micheal Espinola Jr > <michealespin...@gmail.com> wrote: > > As best as I can recall, it was listed as a requirement in the last SQL > clustering requirements doc I read on Microsoft's website. I thought it was > up-to-date, but perhaps I am mistaken? > > > > > > On Aug 17, 2017 6:55 AM, "Melvin Backus" <melvin.bac...@byers.com> wrote: > > Windows clustering doesn’t require Enterprise any more. It moved to std with > 2012. We run both LB and FO clusters on 2012 std. Please don’t tell me they > went back with 2016. L > > > > -- > There are 10 kinds of people in the world... > those who understand binary and those who don't. > > > > From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] > On Behalf Of Micheal Espinola Jr > Sent: Wednesday, August 16, 2017 9:24 PM > To: ntsysadm@lists.myitforum.com > Subject: Re: [NTSysADM] A new task for me - setting up a SQL Server cluster > on vSphere 6.0 > > > > The minimum requirement would be Windows. > > > -- > Espi > > > > > > On Wed, Aug 16, 2017 at 6:07 PM, Kurt Buff <kurt.b...@gmail.com> wrote: > > Windows or SQL or both? > > > On Wed, Aug 16, 2017 at 5:27 PM, D R <drod...@gmail.com> wrote: >> Well, for 1, I think you're going to need Enterprise Edition for your >> server >> clustering. >> >> >> On Wed, Aug 16, 2017 at 6:04 PM, Kurt Buff <kurt.b...@gmail.com> wrote: >>> >>> Does anyone have a good reference on setting up a 2-node cluster like >>> this? >>> >>> I'll be putting up SQL Server 2016 on Server 2016 Standard. >>> >>> I've found a starting place: >>> >>> >>> https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2147661 >>> >>> This is going to be a replacement for all of the little SQLServer >>> Standard/Express/WID implementations we have scattered about. >>> >>> But - does anyone have preferred documentation for implementation? Any >>> preferred configurations, and perhaps reasons why? Any nasty little >>> gotchas to avoid? >>> >>> Thanks, >>> >>> Kurt >>> >>> >> >> >> >> -- >> Daniel Rodriguez >> drod...@gmail.com > > > > > > > > > > -- > > Daniel Rodriguez > drod...@gmail.com
