While Development and Express environments can be great in saving you money, in testing and demonstrating your software before deployment, it is important that these scenarios are licensed properly and that you understand their limitations. Developer-Specific Licenses: Used primarily for debugging, designing, development, testing and demonstrating purposes. This license is for non-production use only and is often purchased when programmers, professional testers, technical writers, database professionals, or IT administrators are involved.
Developer specific licenses are assigned on a per-user basis, in which Users can install and access an unlimited number of SQL Server instances and share those instances only with other users who have been assigned the same type of developer-specific user licenses. That means, for this licensing model, if anyone wishing to access a development environment requires a developer-specific license, even for tasks as hands-off as administrative purposes.
The only exception to this is user acceptance testing. Installations can be set up and taken down at any time and can be placed on desktops, dedicated servers, shared servers, and cloud environments. Some potentially less expensive alternatives to this license include the following:.
Evaluation Licenses: Used to assess the software for potential business use. Again, only used for non-production environments but it is not often used in development and test environments. Usually comes with an expiration date days to evaluate the use of the software when obtained through volume license contracts. This will cover all the VMs that your software environment will ever see, which comes in handy since VMs are so easily and quickly cloned and installed. You will need a license for every virtual core that you have.
Licensing your Virtual Environment all depends on the licensing model you choose, with the per core model proving much more cost-effective for many clients. Power BI and SQL Server Power BI is one of the most popular services for large businesses, and it can quickly become the most complicated due to its robust environment and its complicated, although critical, relationship with SQL servers. Although you will still need to have a Power BI account for content creation. With the Desktop, however, you can retrieve SQL Server data from tables and run queries that can retrieve a subset of the data from multiple tables.
Licensing for Disaster Recovery and High Availability. Which is why Microsoft, as of November 1st, , has three enhanced benefits to offer to software assurance customers, which can be applied to any SQL Server that is still supported by Microsoft, including failover servers for high availability, disaster recovery, and disaster recovery in Azure.
What this means is that you can run passive SQL Server instances on separate operating system environments OSE or servers for high-availability on-prem or in Azure to cover any sort of failover event. If you have a secondary server that is only used as failover support , then you do not need to license that server separately from the SQL server it is supporting, as long as the server remains truly passive and the primary SQL Server is covered by your Software Assurance.
It is most important that you have a means of proving when your servers are passive, since during a software audit, the software auditors will assume that all your servers are active if given the chance to assume so. This means no more security or feature updates, no more help from Microsoft to keep your environment healthy and protected. Even if your license is perpetual and legally speaking you are allowed to keep the product forever, it may still be within your best interest to upgrade your license anyway to one that Microsoft supports.
However, it will not be easy since a SQL Server upgrade will take months and you should plan accordingly. When you are considering updating from one Server to the next, the first thing you need to do is make a to-do list containing everything you have to do, such as:. If you have Software Assurance, then you are covered to upgrade your SQL Server edition, if not then you will have to purchase more licenses.
Check to make sure what sort of changes have occurred since you last updated SQL Server, since depending on how old your SQL Server is, you may find yourself confronted with new features, new definitions, and new licensing metrics.
Do some research into the new SQL Server model you are planning on upgrading to and familiarize yourself on any differences the new edition has compared to your old model.
Lastly, decide whether, this time around with your new SQL Server, if Software Assurance is something that interests your company. SQL Servers are so thoroughly implemented throughout the software environments of organizations that a simple mistake could easily be scaled up to mean millions of dollars in software auditing fines.
Licensing model. Channel availability. Volume licensing, hosting. Standard - per core. Standard - server. Standard - CAL. Per user. See your hosting partner for pricing. Not applicable. Hosting only. Volume Licensing. SQL Server Standard.
Big data nodes core entitlement New. Fail-over servers for disaster recovery New. Fail-Over servers for disaster recovery in Azure New. Azure Hybrid Benefit. Fail-over servers for high availability. Unlimited virtualization. The licensing in SQL Server is the "honor" system. There is nothing in the installation which restricts the usage based on the license you purchased. If you want to know what you legally are authorized to use, you need to contact Microsoft Licensing.
SQL Server indeed will use added cpu's as it is not aware of your licensing, SQL on its own will not put any restriction if you add additional cpu's, but you need to take care of your licensing.
If it is SQL Server then licensing is on per processor based but onwards MS has changed licensing model, now it is core based. Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:.
0コメント