The annual 2012 sa edition

The semiconductor industry grew and diversified in the subsequent decades and it was not until that the US semiconductor community decided to formulate a page document detailing all the aspects of the industry. In the meantime the semiconductor community had expanded to other regions and therefore it became clear that a broader world-wide approach to roadmapping needed to be taken.

Its primary purpose was to serve as the main reference into the future for university, consortia, and industry researchers to stimulate innovation in various areas of technology. This announcement heralded the introduction of the iPhone and the iPad in the following years. Therefore, in December , during the annual meeting held in Taiwan, the ITRS decided to reorganize in order to address the renewed ecosystem of the microelectronics industry.

For example, the first time a customer purchases a Windows Server Datacenter license as an Additional Product under any of these enrollments, that license type is added to the customer's EA price sheet at the then-current price, even if the customer purchases only a single unit. The price thereafter remains unchanged for subsequent purchases through the end of the EA enrollment.

Before the end of the current EA enrollment term. When an EA enrollment is renewed, the customer's price sheet is updated to reflect the products available and associated prices as of the date of renewal. Currently, RDS CALs may be used only for session-based remote desktops that are deployed on on-premises servers, or on dedicated servers not shared with other customers of a third-party service provider. By early , RDS CALs with active SA will also be valid for workloads running on shared multitenant servers of service providers although the VM running the workload must be for the exclusive use of the particular customer.

Existing rule. Under current rules, the only way to license session-based remote desktops deployed on third-party shared servers is through the provider's Service Provider License Agreement SPLA. Under the SPLA, service providers account for software used by customers and remit monthly payments to Microsoft.

New rule. These CALs will license client access to the customer's session-based remote desktops running on the provider's shared servers. The ability to run such workloads on Windows Azure is a recent development: on July 1, , Microsoft lifted its restriction prohibiting Windows Azure VMs from hosting session-based remote desktops. The Jan. An alternative to session-based remote desktops is VDI.

With VDI, each user's desktop including the OS, applications, and user data executes in its own VM, hosted on a centrally managed server. With the session-based remote desktop architecture, in contrast, all users' Windows desktop applications and desktops run on the same shared instance of Windows Server; Windows Server mimics the "look" of the Windows client OS, but no instances of the client OS actually run on the server.

Under current rules, VDI workloads may only be run on customers' on-premises hardware or on third-party service provider equipment that is dedicated to the particular customer. Running VDI workloads on a service provider's shared multitenant hardware is prohibited, and no changes to this rule have been announced.

Windows Server R2 pricing and licensing information is at download. Windows Server licensing briefs are posted at download. Windows Server R2 licensing was covered in the Nov. Rules for reassigning server-side licenses from on-premises to third-party service providers are discussed in " Enterprise Cloud Licensing Rules Clarified " on page 22 of the Aug.

Skip to main content. Windows Server R2 Pricing and Licensing. Microsoft used to allow its customers to freely move VMs around machines, although there was a day restriction for some of the licensing. DeGroot said this SA requirement for moving VMs will add 25 percent per year to the cost of licensing SQL Server over a three-year term, amounting to a 75 percent cost increase.

There are three editions Enterprise, Business Intelligence and Standard , but they have different licensing models. Enterprise edition licensing is now sold on a per-core basis. The BI edition is not available on a per-core basis — it can only be licensed on a per-server basis. The Standard edition is available in either licensing model per core or per server.

DeGroot said that Microsoft's licensing team did a poor job for organizations by making it difficult for them to plan. For instance, if an organization is moving to the Enterprise edition, it may have to "throw away" its CALs.

However, it won't be possible for those organizations to buy any more new per-server licenses, DeGroot said. One relies on using the true-up process with SQL Server R2 licenses to gain additional core entitlements.

A true-up is licensing lingo for contract renewals under Microsoft's Enterprise Agreements. DeGroot noted that true-ups will cost the least during the third year of an agreement. The idea behind a true-up is that organizations can add software during the year and pay for the additional licensing later at the annual true-up assessment time. The true-up fee is the cost of the software license plus a certain amount of SA cost, he said.

The cost-cutting example presented by DeGroot was installing SQL Server Enterprise edition with 20 core licenses and then using the true-up process for SQL Server R2 installations with eight cores to get the rights to 20 cores at the price of eight cores. Organizations can run a tool such MAP to demonstrate that the organization ran a server with 20 cores. The SQL Server Enterprise edition that's run for this assessment using MAP doesn't actually have to have a workload to be counted for licensing true-up purposes, he explained.

Another strategy is to defer paying for SA. So, instead of paying for SA on all machines, an organization could license a server with 12 cores to run 12 VMs without SA coverage. This approach was described as getting the vMotion capability through "overlicensing. The rationale for that rule is simply that Microsoft wants to make things less flexible for people without SA coverage, he explained.

Microsoft has said that the SQL Server product will be released in either the fourth quarter of or in the first quarter of , DeGroot said. DeGroot's talk was more detailed than can be summarized in this article. However, it illustrated why a whole consulting industry continues to revolve around Microsoft's often complex licensing structures. DeGroot offered few details, but he called the Product and Services Agreement "scary" because it requires an organization to put SA on all existing servers and clients, increasing costs.

When you visit our website, we store cookies on your browser to collect information. The information collected might relate to you, your preferences or your device, and is mostly used to make the site work as you expect it to and to provide a more personalized web experience.

However, you can choose not to allow certain types of cookies, which may impact your experience of the site and the services we are able to offer. Click on the different category headings to find out more and change our default settings according to your preference.

You cannot opt-out of our First Party Strictly Necessary Cookies as they are deployed in order to ensure the proper functioning of our website such as prompting the cookie banner and remembering your settings, to log into your account, to redirect you when you log out, etc. For more information about the First and Third Party Cookies used please follow this link.

You can set your browser to block or alert you about these cookies, but some parts of the site will not work as intended if you do so. You can usually find these settings in the Options or Preferences menu of your browser. Visit www. Under the California Consumer Privacy Act, you have the right to opt-out of the sale of your personal information to third parties.

These cookies collect information for analytics and to personalize your experience with targeted ads.