Jul 11, - Buying Microsoft SQL Server R2 Enterprise. 50 51 ill. De Vries Evans Susanna. The Impressionists Revealed: Masterpieces from, Private. Nov 5, - In Enterprise, Microsoft giveth and Microsoft taketh away. SQL R2's BI tools include a new Master Data Services tool. It's targeted at. Mar 8, - I was recently asked question about SQL Server pricing. which lists the pricing. Official site: What's New in SQL Server R2 Editions via Server CAL. Enterprise, $28,, $13, with 25 CALs I recently come across very interesting white paper written for Microsoft by Solid Quality Mentors.
It was still limited to the lesser of four sockets or 16 physical cores. Microsoft raised the core limit for SQL Server It was limited to the lesser of four sockets or 24 physical cores. Recent Hardware Advances In June , Intel Broadwell processors had a maximum of 24 physical cores, which meant that you could hit the SQL Server core license limit on one socket. This was a more common scenario.
These hardware advances mean that there is a good argument that the core license limit should be increased to a higher number. If Microsoft increased the core limit to 64, you would be able to use a two-socket server with two flagship Intel core processors. I also believe that the per instance memory limit should raised to a higher value.
My suggestion would be to go to GB, which would double the current limit. Being able to use higher core count processors and more memory would be an attractive combination which would increase revenues from SQL Server Standard Edition.
Microsoft could and really should do a better job of demonstrating the value of SQL Server Enterprise Edition for performance, scalability, and useful Enterprise-only features.
They could use KB articles, whitepapers, and blog posts to discuss the low level optimizations that are already in Enterprise Edition but not in Standard Edition.
Putting all of this information together would be extremely valuable. For example, running a common benchmark like DBHammer on SQL Server Standard Edition, and then doing an Edition Upgrade and re-running the benchmark on the exact same system would be a pretty simple way to confirm performance increases.
SQL Server licensing is platform agnostic. The same licensing models apply irrespective of the operating system being used if the operating system is supported.
So, what is a Docker container? A Docker container is like a virtual machine whereby only a fraction of the processing power may be required to run a given application. The below illustrations demonstrate how the two differ in configuration. Figure 1 — Typical Virtual Machine configuration Where a Docker container differs from virtual machines is that the containers share the same hardware and operating system, but the applications are stored in the containers refer to Figure 2 — Typical Docker Container configuration.
The container method is less resource intensive and allows for faster deployment of services. Docker container technology may also bring cost saving opportunities for the operating system.
Figure 2 — Typical Docker Container configuration How many licenses do I need to license individual containers using the Per Core licensing model? The process to determine this is essentially the same as for determining the cores under a virtual machine configuration scenario. For example: Example 1 — I have a server that has two SQL Server containers, one with access to two virtual cores and the other with access to four virtual cores.
Ascertain how many individual containers are present Count the total number of virtual cores in each container keeping in mind there is a minimum requirement of four cores per container: As a result, four SQL Server core licenses will be required Container 2 has access to four virtual cores. The same number of four SQL Server core licenses will be required A total of six virtual cores are present, but since a minimum of four virtual cores are required for Container 1, the total licenses required are eight.
SQL Server core licenses are sold in packs of two. There are also two users accessing the SQL Server containers:
What does End of Support mean? We recommend upgrading to the latest versions of our software to continue to get regular security updates, either in Azure or on-premises.
However, for customers that are not able to transition before the End of Support date, we have options to help protect data and applications during the End of Support transition: Extended Security Updates in Azure: For many customers, this is an easy first step before upgrading or modernizing with newer versions or services in Azure.
These customers will also have access to Extended Security Updates for no additional charges above the cost of running the virtual machine. Extended Security Updates for on-premises or hosted environments: Extended Security Updates will also be available for workloads running on-premises or in a hosting environment like another cloud provider. Product licenses and Software Assurance do not need to reside on the same enrollment. Customers can purchase Extended Security Updates only for the servers they need to cover.
Extended Security Updates can be purchased directly from Microsoft or a Microsoft licensing partner. When will the Extended Security Updates offer be available? In Azure: Customers can begin migrating workloads to Azure Virtual Machines immediately and apply regular security updates until the End of Support date, at which time Extended Security Updates will become available, ensuring continuous coverage. On-premises or hosted environments: Extended Security Updates are now available for purchase, and can be ordered from Microsoft or a Microsoft licensing partner.
The delivery of Extended Security Updates will begin after the End of Support dates, if and when available. What do Extended Security Updates include?
For Windows Server and R2: Extended Security Updates will be distributed if and when available. Extended Security Updates do not include technical support, but you may use other Microsoft support plans to get assistance on your Server and R2 questions on workloads covered by Extended Security Updates.
Extended Security Updates do not include new features, customer-requested non-security hotfixes, or design change requests. However, Microsoft may include non-security fixes as deemed necessary. There is no retroactive effect for any update that the engineering teams declined in the past. SQL Server does not ship a general monthly security update. If there are situations where new SQL Server important updates will not be provided and it is deemed critical by the customer but not by MSRC, we will work with the customer on a case-by-case basis to suggest appropriate mitigation.
What Licensing programs are eligible for Extended Security Updates? Software Assurance does not need to be on the same enrollment. Are customers required to cover all on-premises servers with active Software Assurance to get Extended Security Updates on-premises? No, customers can choose to cover as many on-premises servers with Software Assurance as they need for Extended Security Updates. Pricing is available on published price lists. Contact your Microsoft partner or account team for more details.
Hosted environments: The price of Extended Security Updates acquired through Microsoft resellers is set by the reseller. Pricing for Windows Server Extended Security Updates is based on Windows Server Standard per core pricing, based on the number of virtual cores in the hosted virtual machine, and subject to a minimum of 16 licenses per instance.
Pricing for SQL Server Extended Security Updates is based on SQL Server per core pricing, based on the number of virtual cores in the hosted virtual machine, and subject to a minimum of 4 licenses per instance. Software Assurance is not required. Contact your Microsoft reseller or account team for more details. If a SQL Server and R2 customer with Software Assurance purchased a number of cores for their on-premises environment, and is using Software Assurance to have a secondary passive server e.
The price of Extended Security Updates will be calculated based on the number of cores licensed for a customer's on-premises environment. Customers can then apply updates to their licensed virtual machined, including the secondary passive server. However, they can move their workloads to Azure and get the Extended Security Updates for no additional charges above the cost of using the Azure service.
What are the details for the Extended Security Updates offer on-premises? Customers can choose which servers to be covered. Customers with Software Assurance through other enrollments e. Prices will remain the same for years 1, 2, and 3. Pricing for Extended Security Updates will follow the current license model for the server. For example, Windows Server is licensed by core and is required for all physical cores on each server.
Consult the published price lists or your reseller for actual prices. Coverage will be available in three consecutive month increments following End of Support. Customers cannot buy partial periods e. Customers must have active Software Assurance coverage or subscription licenses for at least one month at the start of each coverage period in order to be eligible for Extended Security Updates in that period.
If customers purchase Extended Security Updates while Software Assurance is active, but Software Assurance lapses before the Extended Security Update coverage period begins, customers will not be able to receive updates. Extended Security Updates are available annually, for a fixed month period. If a customer purchases Extended Security Updates in month 10 of the month period, that customer would still need to purchase the full 12 months.
Customers must have purchased coverage for year 1 of Extended Security Updates in order to buy year 2, and coverage in year 2 in order to buy year 3. Customers may buy coverage for previous years at the same time they buy coverage for a current period. It is not necessary to buy a certain period of coverage within that coverage period. Premier Support is not a base requirement, but an additional support contract is recommended if technical support will be required.
Can customers license just the virtual machine? For example, if a customer is running a Windows Server or R2 virtual machine on Windows Server or another host, do they need Extended Security Updates for the full server? What if the host is running Windows Server or R2, but none of the virtual machines are? Customers cannot license individual Windows Server virtual machines. They must license the full physical server. Licensing requirements for Extended Security Updates on-premises align to the licensing requirements for the underlying Software Assurance coverage or subscription.
Customers will only need to know their Windows Server license position for a given server, to know how many Extended Security Update licenses they need. Customers who have covered all the underlying cores of the physical server with Windows Server Datacenter licenses should buy Extended Security Updates for the number of physical cores, irrespective of the number of VMs running on that physical server.
Customers who have covered all the underlying cores of the physical server with Windows Server Standard licenses should buy Extended Security Updates for the number of physical cores, but will only be licensed to run and update two virtual machines on the server. Customers who wish to run and update more than two virtual machines on a server licensed with Windows Server Standard must re-license all of the physical cores on the server with both Windows Server Standard and Extended Security Updates for each additional pair of virtual machines.
Microsoft will only produce updates which can be applied on the latest Service Pack. Here are the links to the latest service packs: