So, it is always a good idea to consult your Microsoft Rep or your third-party rep, give them a clear picture about what your software environment looks like and then they can tell you about the CALs you need. Now that we have our SQL server licensing models laid out, we can move onto the next level of complication: Editions. Microsoft offers four different Editions : Standard popular selection , Enterprise also popular , Express, and Developer.
Standard: The basic experience with standard reporting and analytic capabilities. There is a limit of memory, database size, and a maximum number of cores. Enterprise: Having all the basic features of the Standard Edition, Enterprise also offers tools for analyzing business and financial data, along with critical applications and data warehousing features essential for enterprises, whom this edition is primarily targeted towards.
Where the Standard edition had limits on its space and usage, the Enterprise edition has the sky as the limit. It is only offered in core-based licensing models, which makes sense since enterprise customers usually chose core-based licensing models. Express: This free version offers a limited experience, even when compared to the Standard edition.
It is excellent though for general database use, including small applications with both hardware and software limitations. Many organizations will first deploy SQL Server Express to see if it is sufficient for their specific applications and will only move to the fee-based editions when they can confirm that Express will not meet their requirements.
Developer: This edition allows you to build, test, and demonstrate applications in a non-production environment. A piece of software will be considered in production if individuals, either inside or outside of the organization, use the software for any reason beyond development, including evaluation acceptance testing such as a review of the application before it is put into general use. A SQL server will also be considered in production if it is connected to another database that is in production or runs as a backup or to provide disaster-recovery to a SQL server in production.
As you can probably imagine, mixing production and non-production environments is a recipe for disaster, as this can cause hyper complexity and compliance issues, especially if access controls are not established that prohibits use outside of development and testing. There are a few ways to counteract this problem:. The main challenge with these editions is proving which edition you have. For example, if you are in a software audit, unless provided with evidence that proves otherwise, the software auditors will assume that you only have Enterprise editions, which are the most expensive.
Proving which editions, you have could mean the difference between owing hundreds of thousands of dollars and owing nothing. 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.
This does not exist. When MS makes licensing so complicated there is a certification test of it's own you know there is a problem. My fault for not making that clear. External Users to me equal non employees. Internal users to me are named users. Where it gets overly confusing is when you add ecommerce to the mix. Are these non company users aka customers named users or not? They have a account with their name and they login to the system. They seem to keep it purposely vague. What if your shopping cart uses a SQL back end.
MS licensing has never really correctly adapted to e-commerce. A vast majority of these are used to host websites. No, you don't need a SQL CAL for customers on your website, whether or not they have a customer "account" in your ecommerce back office suite. They aren't touching the SQL server -- that's handled through a broker or some other software construct on the web host. To claim otherwise would be akin to saying that Exchange CALs are required for every entity that sends an email into your Exchange server, or receives one from it.
Just pure silliness. You have front end Windows Servers setup to support your website, and backend servers e. Since users are accessing the backend commerce servers which web workloads are not running — CALs or External Connectors will be required for users to access these back end servers.
This is completely wrong. It's everyone pulling data out of it, so web users would be every single user that hits the web page needs to be CAL'd, one way or another. Exchange is licensed differently, so the comparison doesn't apply.
They are exactly the same. It's anyone making use of the service, there is no concept of "touching" in either system. It definitely is. It's not the only benefit that Linux has, but it's the lb gorilla. That it is easier, a little faster, more flexible - all great things. To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks.
Best Answer. We'll cover licenses for server software, licenses for clients, and some advanced Microsoft licensing scenarios. And while this article focuses on Microsoft server applications, similar issues can arise with other server applications. The license required to install and run most server applications usually comes bundled with the software itself.
So you can install and run most applications "out of the box," as long as you have the right number of client licenses and meet the server licensing requirements.
More detail on client licensing is provided below. In some cases, though, you may need additional licenses in order to run your server software:. Leave a Comment We encourage you to share your comments on this post.
Be sure to enter a unique name. You can't reuse a name that's already in use. Be sure to enter a unique email address.
You can't reuse an email address that's already in use. Website optional. Preview Exit Preview. Latest Comments. UrsRenggli on: HPE ranked 1 for social media. Makes Microsoft Di HPE Webinars. Find out about the latest live broadcasts and on-demand webinars. Online Expert Days. The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise.
By using this site, you accept the Terms of Use and Rules of Participation.
0コメント