Correct understanding of SQLServer licenses)

I saw a discussion on how many CALS are required for using SQLServer as the SEPM background database: Login. Isitaone-to-onerelationshipwhereeachclientthatchecksint

I saw a discussion on how many CALS are required if SQL Server is used as the SEPM background database: if I do have to use SQL Server what type of licensing is required in terms of user CALs. is it a one-to-one relationship where each client that checks int

I saw a discussion on how many CALS are required if SQL Server is used as the SEPM background database:

If I do have to use SQL Server what type of licensing is required in terms of user CALs. is it a one-to-one relationship where each client that checks into a SEP 11 management server needs a SQL Server CAL? Or do only the management agents on the SEPM server need a CAL since client machines technically check-in via HTTP and not directly to the database?

Participants have two points of view:

The first method is that the SEP client does not support database access, so no permission is required. Only the Manager that directly accesses the database needs permission:

The SEP clients do not acess the DB directly. you'll just need to license the SQL DB for the SEPM, since the client talks to the SEPM, and then the SEPM talks to the Database.

In another statement, users who use the SQL Service must purchase the CAL. Because the client needs the SQL service, they must purchase the CAL for each client:

Microsoft are very clear on SQL Licensing:

A SQL Server CAL is required for a user or device to access or use the services or functionality of either edition of SQL Server.

This statement implements tively means that if you purchase user or device CAL's you MUST purchase enough CAL's to cover all your users or clients, NOT just for SEPM's. I will leave you to do the math, but once you hit a certain number, processor licensing is MUCH cheaper!

Haha, interesting discussion: the pre-sales work is rarely involved. I have no idea at first glance, so I can check it on the official website of MS:

SQL Server supports three types of licenses: processor-based, user-based, and client-based.

When the number of users or devices is large or the SQL server load is heavy, it is more cost-effective to use the processer license. The user or device license is used anyway. If the user shares the device, the device is used. If one user has multiple devices, the user is used.

Regarding whether the client that indirectly uses the SQL service needs CAL, the MS statement is:

In most cases, Microsoft requires a CAL for every device that accesses or uses the services of SQL Server 2005. if you are unsure whether a CAL is required, you should contact your Microsoft sales representative or account manager. inquires can be directed to the Microsoft Sales and Partner Information line by calling (800) 426-9400.

Interestingly, what does In most cases mean? Contact sales if you don't know? It seems that there are still discussions.

In my experience, if SQL is used as the backend of the front-end Web server, Web server users need to purchase licenses. However, for most Web servers, users are not fixed, in this case, you should purchase the processor license. I think other applications that use SQL as the background database should also be the same.

-----------------------------------------------

Client Access License Model

Microsoft Server products mainly use three CAL models: per user, per device, and per server. Not all CAL types are available for all products, and a specific product may provide other types of CAL. For more information about specific CAL licenses, see the Microsoft CAL guide. What is the URL? LinkId = 91230 (the page may be in English ).

Per User CAL

For each user's CAL model, each user accessing the server needs a separate CAL. If a user uses multiple computers, the user can access the server from each computer and use only one CAL. However, if another user logs on to one of the computers, the user needs to access the server separately with each user CAL.

A company with 200 employees uses two Exchange servers on 220 computers as a typical example of each user's CAL. This requires two server licenses (to install products on the server) and 200 per user CAL. Because CAL is assigned to each user, the number of computers accessing the server is not important.

CAL per device

For each device's CAL model, each device accessing the server needs a separate CAL. If multiple people use a specific computer, a CAL allows them to access the server from that computer. However, if one of these users uses another computer to access the server, the other computer will also require the CAL per device.

A company with 200 employees uses two Exchange servers on 150 computers as a typical example of CAL per device. In this way, two server licenses (to install the product on the server) and 150 CALS per device are required. Because CAL is assigned to each device, the number of users accessing the server is not important.

Per server CAL

For each server's CAL model, each device accessing the server simultaneously requires a separate CAL. During installation, the server administrator will enter the number of CALS purchased for a specific server. If this number is set to 30, only 30 computers are allowed to connect to the server at the same time. However, if the server serves 100 computers, all these computers can access the server, as long as there are no more than 30 connections at the same time. After the computer is disconnected from the server, the CAL is released so that another computer can connect to the server. If multiple computers are used for load balancing, each server needs a separate CAL. For example, if you are using two Exchange servers and have purchased 200 CALS for each Server, you need to allocate 100 CALS for each Server.

How to calculate the CAL count of an asset smart report

If the hardware Configuration is enabled for the client computer, the Configuration Manager 2007 hardware Configuration client agent analyzes the security audit logs on the computer running the Windows Server operating system. Then, the list of users and IP addresses associated with the server is included in the hardware list report sent by the customer. When an asset intelligent CAL report is run, the information collected from the client is merged Based on the CAL model described earlier. The report shows the individual cumulative CAL usage for Windows of each version. In addition, the number of users and computers connected to Windows servers running Exchange Server will be compiled and reported as Exchange CAL.

The following assumptions are made for users and devices Exchange CAL and Windows Server Device CAL.

Exchange CAL computing assumes that the Exchange Server is installed on a single workload computer. If other server products run on the same computer, only users or devices connected to those products are reported as Exchange CAL.

The device CAL report identifies the computer based on the IP address. Therefore, when listing the usage of the device's CAL, you may observe the following situations:

If some clients are behind vrouters with network address translation, all computers connected by a single IP address are counted as one.

If a computer has multiple IP addresses because it uses multiple network interface cards, each IP address is counted as a separate device CAL.

Note:

User CAL is not based on IP addresses, so it is not affected by these IP-related restrictions.