Someone ought to hire whoever wrote that article - it's very nice. Kurt
On Thu, Aug 17, 2017 at 1:27 PM, Webster <webs...@carlwebster.com> wrote: > http://carlwebster.com/implementing-microsoft-sql- > server-2016-standard-basic-availability-groups-use- > citrix-xenapp-xendesktop-7-9/ > > > > Someone wrote on article on that very topic. > > > > Thanks > > > > > > Carl Webster > > Citrix Technology Professional | iGel Tech Community Insider | Parallels > VIPP > > http://www.CarlWebster.com > <http://t.sidekickopen01.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJN7t5XYgdV8QRW2zWLDn4XrdjzW7fK3rs56dwxZf67wwsR02?t=http%3A%2F%2Fwww.carlwebster.com%2F&si=6012126861197312&pi=4311b7b1-332d-4242-8585-36954b184dc7> > > The Accidental Citrix Admin > > > > *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists. > myitforum.com] *On Behalf Of *Kurt Buff > *Sent:* Thursday, August 17, 2017 3:18 PM > *To:* ntsysadm <ntsysadm@lists.myitforum.com> > > *Subject:* Re: [NTSysADM] A new task for me - setting up a SQL Server > cluster on vSphere 6.0 > > > > The link you provided is helpful - thanks. > > According to our EA summary, I have an effective quantity of 4 x SQL > Server Standard Core 2016 licenses, with an unresolved quantity of 20 and > an SA quantity of 16, though I'm not entirely sure what all that means. > > Kurt > > > > On Thu, Aug 17, 2017 at 11:17 AM, Nathan Shelby <ntshe...@gmail.com> > wrote: > > "Server Standard does NOT support Always On Availability Groups" > > Sort of? As of SQL 2016, It supports Basic Availability Groups which are > AGs with limitations, they are managed the same way as a standard AG. They > don't scale particularly well but they avoid the pitfalls of a WSFC SQL > implementation where you wait for the resource to come back up with a node > failure. (differences here: https://docs.microsoft.com/en- > us/sql/database-engine/availability-groups/windows/ > basic-availability-groups-always-on-availability-groups). > > Another thing that Kurt should be aware of is the licensing model for SQL > 2016 Virtual Machines. With the consolidation mentioned are you planning to > license the cluster as SQL Server Standard Core (depending on size this may > make the most sense) or SQL Server Standard and SQL Client CALs? If you're > running SQL Standard Core a VM requires running a minimum of 4 core > licenses (2x 2 core packs, which is how SQL Core licensing is sold). I > assume with a 6 node cluster you'll be covering the license with Software > Assurance to take advantage of License Mobility so you can move the VM > between hosts more than once per 90 day period. > > > > > Nathan Shelby > ntshe...@gmail.com > 425-205-9047 <(425)%20205-9047> > > > > On Thu, Aug 17, 2017 at 10:52 AM, Michael B. Smith <mich...@smithcons.com> > wrote: > > Yes, it will work. > > I cannot say anything whatsoever about VMware. I'm a Hyper-V guy. > > -----Original Message----- > From: listsad...@lists.myitforum.com [mailto:listsadmin@lists. > myitforum.com] On Behalf Of Kurt Buff > Sent: Thursday, August 17, 2017 1:18 PM > To: ntsysadm > > Subject: Re: [NTSysADM] A new task for me - setting up a SQL Server > cluster on vSphere 6.0 > > 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_U > >>> S&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 > > > > >
