In this episode, Sean Donahue looks back at the tech stories from 2022. The highs, lows, and everything in between. What story did we miss? Which stories surprised you in 2022? Please leave your comments below.<\/p>

Have a wonderful 2023!<\/p>

<\/oembed><\/p>

\u00a0<\/p>

If you have any questions, feel free to reach out to me on\u00a0Twitter<\/a>\u00a0and if you haven't already done so, make sure you are subscribed to the show wherever you consume podcasts.<\/p>

\u00a0<\/p>","id":41482,"featuredImage":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/attachment\/f38aec9c-1b9f-472b-8bc4-5177f93527b7_thumb.png","label":"Blog","replyCount":0,"views":53,"post":{"id":63100,"author":{"id":7898,"url":"\/members\/aluciani-7898","name":"aluciani","avatar":"https:\/\/uploads-us-west-2.insided.com\/nutanix-us\/icon\/200x200\/77accf89-4f79-48be-81e6-c2ac5507e29b.png","userTitle":"Chevalier","rank":{"isBold":false,"isItalic":false,"isUnderline":false,"name":"Chevalier","color":"#660099"},"userLevel":7},"content":"

In this episode, Sean Donahue looks back at the tech stories from 2022. The highs, lows, and everything in between. What story did we miss? Which stories surprised you in 2022? Please leave your comments below.<\/p>

Have a wonderful 2023!<\/p>

<\/oembed><\/p>

\u00a0<\/p>

If you have any questions, feel free to reach out to me on\u00a0Twitter<\/a>\u00a0and if you haven't already done so, make sure you are subscribed to the show wherever you consume podcasts.<\/p>

\u00a0<\/p>","url":"\/community-blog-154\/nutanix-community-podcast-2022-year-in-review-41482?postid=63100#post63100","creationDate":"2023-01-03T14:40:38+0000","relativeCreationDate":"1 day ago"},"contentType":"article","type":3,"likes":2,"hasCurrentUserLiked":false},"phrases":{"Forum":{"{n} year|{n} years":"{n} year|{n} years","{n} month|{n} months":"{n} month|{n} months","{n} day|{n} days":"{n} day|{n} days","{n} hour|{n} hours":"{n} hour|{n} hours","{n} minute|{n} minutes":"{n} minute|{n} minutes","just":"just now","{plural} ago":"{plural} ago"}}}">

SQL许可 - Nutanix如何处理每个核心问题的成本？

k
徽章 +2
关于SQL许可 - Nutanix如何处理每个核心问题的成本？



与每个CPU的成本有关



Nutanix如何解决SQL许可（每个核心）发行

    \n

    \npertaining to the cost per cpu

    \n

    \nhow does Nutanix solve sql licencing (per core) issue","quoteUsername":"Kevin_Penn","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    该主题已关闭以供评论

    7个答复

    dlink7
    UserLevel 4
    徽章 +19
    确实与使用常规服务器相同。您可以添加nutanix节点，只需存储即可。您也可以拥有多个小型计算簇，但是基础存储群集可以完整，因此您可以有效地使用存储资源。
    k
    徽章 +2
    我的理解是，使用每个核心许可（以前为每个处理器）时，SQL许可您将许可为运行SQL工作负载的访客VM的内核数或VCPU的数量。我不知道您是否仍然要求软件保证能够将VM迁移到集群中的任何节点。
    研究学家
    徽章 +3
    我与我们的许可代表交谈的理解是，您需要SA才能迁移SQL Server。如果您在没有SA的情况下迁移，那么您从技术上讲，您没有许可，而BSA可以为您标记。



    另外，有了SA，您有权能够迁移到另一个集群，但每月只有两次。如果您需要在架子或数据中心之间进行中断，这将非常方便。
    在Twitter上找到我：[b] @whisky_kiloor [/b]在我的博客中：http：//whiskykilo.comi是一个快乐的Nutanix客户和NPP。

    \n

    \nAlso, with SA you're entitled to being able to migrate to another cluster, but only twice a month. This is extremely handy if you need to migrate between racks or datacenters for outages.","quoteUsername":"livearchivist","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    VCDXNZ001
    秩
    UserLevel 3
    徽章 +19
    从根本上讲，使用Nutanix根本不会改变SQL Server的许可。这与您在任何其他虚拟化环境中获得许可SQL Server一样。但是，由于您可能能够获得额外的性能，您可能能够合并更多的SQL Server VM每个物理节点/主机，因此，如果许可完整主机（主机上的所有CPU），则可以有效地减少该节点和/或内核的数量总体上需要获得许可。如果您只有一个SQL Server或其中一些在较大的群集中，那么您可能会通过使用VCPU的许可获得许可。微软在我的经验中具有灵活的许可条款，只要您要支付软件保证费用即可。最好的许可选项将取决于您的要求，并且由于许可是复杂的性质，并且拥有高的美元影响力，从适当的合格许可专家那里获得独立建议是最好的。
    n
    徽章
    我的关注者问题只是为了清楚SQL的最大虚拟化许可模型。MS许可指南指出，要使用Max Virtualization，我们必须具有SW保证，并且还必须在物理服务器中许可所有核心...那么它如何与Nutanix一起使用？



    当我们询问MS许可代表时，他们说，由于虚拟化发生在节点下方，因此节点不算为物理服务器，因此群集确实如此。



    因此，从这种情况下，如果我共享了SQL和SharePoint群集，每个节点具有8个带有24个内核的节点，而SQL将名义上运行4个节点（但可以在任何4个节点上运行），那么我们将必须在所有节点上许可SQL群集中的196个核心..



    根据我的经验，MS对许可证的地狱很灵活，直到获得许可证的时间到来，这似乎总是与年底的数百万美元账单相吻合 - 我们总是假设有人需要圣诞节奖金。...但是您可以看到为什么我们担心这一点...

    \n

    \nWhen we asked the MS licensing rep, they stated that because virtualization happens below the node, the node doesn't count as the physical server, the cluster does.

    \n

    \nSo from that case, If I have shared cluster of SQL and Sharepoint that has 8 nodes with 24 cores each, and SQL will nominally run on 4 of the nodes (but can run on any 4) then we would have to license SQL on all 196 cores in the Cluster..

    \n

    \nIn my experience MS are flexable as hell about licenses until it comes time for License true-up which always seems to coincide with a multi million dollar bill at the end of year - we always assume someone needs a Christmas Bonus.... but you can see why we are concerned about this...","quoteUsername":"neteng","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    西顿
    UserLevel 2
    徽章 +13
    我们也对此主题感兴趣，因为我们在Nutanix上实施SharePoint / SQL Enterprise SA。



    我的印象是我们许可我们许可VM的内核，即如果我们许可SQL 8内核，那么我们可以使用1个SQL Server使用8个内核或x2配置为4等。或者，如果我们在集群中许可了所有内核SQL Server然后我们可以根据需要运行尽可能多的实例。



    获得许可所需的最小核心为4



    我基于此的文档是此页面中链接的PDF文档https://www.microsoft.com/en-us/licensing/learn-more/brief-server-virtual-envorirnments.aspx

    \n

    \nI was under impression that we license the cores of the VM i.e. if we license SQL 8 cores then we can either use either 1 SQL server with 8 cores configured or x2 with 4 each etc. or alternatively if we license all cores in the cluster for SQL server then we can run as many instances as we like.

    \n

    \nThe minimium cores required to be licensed is 4

    \n

    \nthe document I've based this on is a pdf document linked in this page https:\/\/www.microsoft.com\/en-us\/licensing\/learn-more\/brief-server-virtual-environments.aspx<\/a>","quoteUsername":"seaton","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    s
    徽章 +5
    使用“核心”许可，您必须将许可证分配给OSI或硬件 - 允许无限的OSI。



    您不必许可完整的群集（但可能需要），只有您要运行的主机，然后使用“策略”来确保OSI仅在许可的主机上运行。

    \n

    \nYou don't have to license the full cluster (but may want to), just the hosts you want to run it on, and then use a \"policy\" to make sure the OSI only runs on the licensed hosts.","quoteUsername":"sentania","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    条款和条件
    Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
    Functional","cookiepolicy.modal.level2":"Normal
    Functional + analytics","cookiepolicy.modal.level3":"Complete
    Functional + analytics + social media + embedded videos"}}}">
    Baidu