ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Verifying MS SQL Server 2017 Licensing

    IT Discussion
    licensing sql server sql server 2017 microsoft microsoft licensing
    6
    37
    4.7k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • K
      Kelly
      last edited by

      Those are list prices, but Microsoft always incentivizes the channel by making their MSRP much higher than it needs to be.

      D S 2 Replies Last reply Reply Quote 1
      • D
        DustinB3403 @Kelly
        last edited by

        @kelly said in Verifying MS SQL Server 2017 Licensing:

        Those are list prices, but Microsoft always incentivizes the channel by making their MSRP much higher than it needs to be.

        Just like with Health Insurance. . .

        1 Reply Last reply Reply Quote 0
        • D
          DustinB3403
          last edited by

          Very fitting.

          Youtube Video

          1 Reply Last reply Reply Quote 0
          • S
            scottalanmiller @Kelly
            last edited by

            @kelly said in Verifying MS SQL Server 2017 Licensing:

            Those are list prices, but Microsoft always incentivizes the channel by making their MSRP much higher than it needs to be.

            yes, which is weird, because it scares customers away.

            1 Reply Last reply Reply Quote 0
            • J
              JaredBusch
              last edited by JaredBusch

              @scottalanmiller Standard - per core pricing for 8 cores would be 4 x 2 core packs that cost $3,717 each.

              For a total MSRP of $14,868.

              That is if SQL Server requires you to license all physical cores or not. I never looked. I assume it does, but I cannot say it does.

              J 1 Reply Last reply Reply Quote 0
              • J
                JaredBusch @JaredBusch
                last edited by

                @jaredbusch said in Verifying MS SQL Server 2017 Licensing:

                @scottalanmiller Standard - per core pricing for 8 cores would be 4 x 2 core packs that cost $3,717 each.

                For a total MSRP of $14,868.

                That is if SQL Server requires you to license all physical cores or not. I never looked. I assume it does, but I cannot say it does.

                Well I'll be fucked. You can license per virtual core.

                Minimum is 4 cores (physical or virtual).
                Physical, you license all cores.
                Virtual, you license per vCore assigned to the VM.
                https://download.microsoft.com/download/B/C/0/BC0B2EA7-D99D-42FB-9439-2C56880CAFF4/SQL_Server_2017_Licensing_Datasheet.pdf
                0_1536698534631_aba3b662-53fb-49ae-aa9c-115c55922159-image.png

                S 2 Replies Last reply Reply Quote 1
                • D
                  DustinB3403
                  last edited by

                  Based on this is looks like they operate with the same per-core fashion as everywhere else.

                  **PER CORE:** Gives customers a more precise measure of
                  computing power and a more consistent licensing metric,
                  regardless of whether solutions are deployed on physical
                  servers on-premises, or in virtual or cloud environments.
                  
                  • Core based licensing is appropriate when customers are
                  unable to count users/devices, have Internet/Extranet
                  workloads or systems that integrate with external facing
                  workloads.
                  
                  • To license a physical server—when running SQL Server in
                  a physical OSE—all physical cores on the server must be
                  licensed.
                  
                  • A minimum of four core licenses are required for each
                  physical processor on the server.
                  

                  Direct download Licensing Datasheet

                  1 Reply Last reply Reply Quote 0
                  • S
                    scottalanmiller @JaredBusch
                    last edited by

                    @jaredbusch said in Verifying MS SQL Server 2017 Licensing:

                    @jaredbusch said in Verifying MS SQL Server 2017 Licensing:

                    @scottalanmiller Standard - per core pricing for 8 cores would be 4 x 2 core packs that cost $3,717 each.

                    For a total MSRP of $14,868.

                    That is if SQL Server requires you to license all physical cores or not. I never looked. I assume it does, but I cannot say it does.

                    Well I'll be fucked. You can license per virtual core.

                    Minimum is 4 cores (physical or virtual).
                    Physical, you license all cores.
                    Virtual, you license per vCore assigned to the VM.
                    https://download.microsoft.com/download/B/C/0/BC0B2EA7-D99D-42FB-9439-2C56880CAFF4/SQL_Server_2017_Licensing_Datasheet.pdf
                    0_1536698534631_aba3b662-53fb-49ae-aa9c-115c55922159-image.png

                    When did THIS change?? WTF

                    1 Reply Last reply Reply Quote 1
                    • S
                      scottalanmiller @JaredBusch
                      last edited by

                      @jaredbusch one of the complications is that there IS no virtual core. vCPU is NOT core.

                      D J 2 Replies Last reply Reply Quote 0
                      • D
                        DustinB3403 @scottalanmiller
                        last edited by

                        @scottalanmiller said in Verifying MS SQL Server 2017 Licensing:

                        @jaredbusch one of the complications is that there IS no virtual core. vCPU is NOT core.

                        Don't get bogged down in the semantics, you license each vCPU in the guest.

                        S 1 Reply Last reply Reply Quote 0
                        • S
                          scottalanmiller @DustinB3403
                          last edited by

                          @dustinb3403 said in Verifying MS SQL Server 2017 Licensing:

                          @scottalanmiller said in Verifying MS SQL Server 2017 Licensing:

                          @jaredbusch one of the complications is that there IS no virtual core. vCPU is NOT core.

                          Don't get bogged down in the semantics, you license each vCPU in the guest.

                          But traditionally, it WAS that semantics that determined the licensing.

                          1 Reply Last reply Reply Quote 0
                          • J
                            JaredBusch @scottalanmiller
                            last edited by

                            @scottalanmiller said in Verifying MS SQL Server 2017 Licensing:

                            @jaredbusch one of the complications is that there IS no virtual core. vCPU is NOT core.

                            a vCPU has vCores. Always. It might just be one. That is how it works.

                            S 1 Reply Last reply Reply Quote 0
                            • ObsolesceO
                              Obsolesce
                              last edited by

                              It was like 2 years ago, and it was MS SQL 2014, we licensed a VM (4 vCPU) and it was not anywhere near $30k. If I remember correctly, it was only a few thousand dollars, unlimited users, 4 vCPU.

                              1 Reply Last reply Reply Quote 0
                              • S
                                scottalanmiller @JaredBusch
                                last edited by

                                @jaredbusch said in Verifying MS SQL Server 2017 Licensing:

                                @scottalanmiller said in Verifying MS SQL Server 2017 Licensing:

                                @jaredbusch one of the complications is that there IS no virtual core. vCPU is NOT core.

                                a vCPU has vCores. Always. It might just be one. That is how it works.

                                Not in any system I've seen. What people call vCores are actually vCPUs. The vCPU might tell the OS it has multiple cores, but the idea of a vCore has never existed, only vCPUs. Vmware, KVM, etc. all the same. Core means physical, it's like having a physical virtual, it cancels itself out.

                                J 1 Reply Last reply Reply Quote 0
                                • ObsolesceO
                                  Obsolesce
                                  last edited by

                                  For MS SQL Server 2014, but may still apply:
                                  0_1536701606161_58a667f3-fd69-4d2f-9302-65645e5a98d5-image.png

                                  S 1 Reply Last reply Reply Quote 0
                                  • S
                                    scottalanmiller @Obsolesce
                                    last edited by

                                    @obsolesce said in Verifying MS SQL Server 2017 Licensing:

                                    For MS SQL Server 2014, but may still apply:
                                    0_1536701606161_58a667f3-fd69-4d2f-9302-65645e5a98d5-image.png

                                    So at some point, MS made a new, industry conflicting term. vCPU has been standard and means something at the hypervisor level. The MS term is an MS only term.

                                    ObsolesceO 1 Reply Last reply Reply Quote 0
                                    • ObsolesceO
                                      Obsolesce @scottalanmiller
                                      last edited by Obsolesce

                                      @scottalanmiller said in Verifying MS SQL Server 2017 Licensing:

                                      @obsolesce said in Verifying MS SQL Server 2017 Licensing:

                                      For MS SQL Server 2014, but may still apply:
                                      0_1536701606161_58a667f3-fd69-4d2f-9302-65645e5a98d5-image.png

                                      So at some point, MS made a new, industry conflicting term. vCPU has been standard and means something at the hypervisor level. The MS term is an MS only term.

                                      I also see this:

                                      0_1536701798983_a859d9b1-0b58-424b-bb19-ec3327a2f3ed-image.png

                                      So if you have hyper-threading enabled on your Hyper-V host, and you give the VM 2 vCPUs, you need to license for 4 cores.

                                      Edit: This is also for SQL 2014, not sure about 2017.

                                      S 1 Reply Last reply Reply Quote 0
                                      • S
                                        scottalanmiller @Obsolesce
                                        last edited by

                                        @obsolesce said in Verifying MS SQL Server 2017 Licensing:

                                        @scottalanmiller said in Verifying MS SQL Server 2017 Licensing:

                                        @obsolesce said in Verifying MS SQL Server 2017 Licensing:

                                        For MS SQL Server 2014, but may still apply:
                                        0_1536701606161_58a667f3-fd69-4d2f-9302-65645e5a98d5-image.png

                                        So at some point, MS made a new, industry conflicting term. vCPU has been standard and means something at the hypervisor level. The MS term is an MS only term.

                                        I also see this:

                                        0_1536701798983_a859d9b1-0b58-424b-bb19-ec3327a2f3ed-image.png

                                        So if you have hyper-threading enabled on your Hyper-V host, and you give the VM 2 vCPUs, you need to license for 4 cores.

                                        Edit: This is also for SQL 2014, not sure about 2017.

                                        That's tough as most deployments, people don't know what is supporting the vCPU. It's also confusing that this seems to ONLY apply with Hyperthreading in one case, but multiple cores in the second. Why does the HT get mentioned, given the second statement?

                                        ObsolesceO 1 Reply Last reply Reply Quote 0
                                        • ObsolesceO
                                          Obsolesce @scottalanmiller
                                          last edited by

                                          @scottalanmiller said in Verifying MS SQL Server 2017 Licensing:

                                          @obsolesce said in Verifying MS SQL Server 2017 Licensing:

                                          @scottalanmiller said in Verifying MS SQL Server 2017 Licensing:

                                          @obsolesce said in Verifying MS SQL Server 2017 Licensing:

                                          For MS SQL Server 2014, but may still apply:
                                          0_1536701606161_58a667f3-fd69-4d2f-9302-65645e5a98d5-image.png

                                          So at some point, MS made a new, industry conflicting term. vCPU has been standard and means something at the hypervisor level. The MS term is an MS only term.

                                          I also see this:

                                          0_1536701798983_a859d9b1-0b58-424b-bb19-ec3327a2f3ed-image.png

                                          So if you have hyper-threading enabled on your Hyper-V host, and you give the VM 2 vCPUs, you need to license for 4 cores.

                                          Edit: This is also for SQL 2014, not sure about 2017.

                                          That's tough as most deployments, people don't know what is supporting the vCPU. It's also confusing that this seems to ONLY apply with Hyperthreading in one case, but multiple cores in the second. Why does the HT get mentioned, given the second statement?

                                          Who knows.

                                          But here you go, just found this for 2017, which also confirms the above:
                                          0_1536702921116_97d03f27-b3f3-46bf-b527-ec80b0e7c813-image.png

                                          1 Reply Last reply Reply Quote 0
                                          • J
                                            JaredBusch @scottalanmiller
                                            last edited by

                                            @scottalanmiller said in Verifying MS SQL Server 2017 Licensing:

                                            @jaredbusch said in Verifying MS SQL Server 2017 Licensing:

                                            @scottalanmiller said in Verifying MS SQL Server 2017 Licensing:

                                            @jaredbusch one of the complications is that there IS no virtual core. vCPU is NOT core.

                                            a vCPU has vCores. Always. It might just be one. That is how it works.

                                            Not in any system I've seen. What people call vCores are actually vCPUs. The vCPU might tell the OS it has multiple cores, but the idea of a vCore has never existed, only vCPUs. Vmware, KVM, etc. all the same. Core means physical, it's like having a physical virtual, it cancels itself out.

                                            I am almost certain that VMWare lets you make a 1 CPU VM with 2 cores.

                                            Hyper-V just says virtual processors.
                                            0_1536703623096_9bebc766-93a2-498e-aa75-f621eb5bb0da-image.png

                                            KVM says CPUs.
                                            0_1536703642847_0252def6-e3e4-40f0-93ec-98417b2bb6ff-image.png

                                            But I very clearly remember some hypervisor letting me specify a vCPU and vCores.

                                            ObsolesceO momurdaM S D 4 Replies Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 1 / 2
                                            • First post
                                              Last post