An additional exception is communication exclusively between the servers running SQL Server.Īnyone using your Application has to be covered by a CAL, including someone who uses it solely to generate Excel Reports but someone who only receives a copy of one of those Excel Reports by e-mail doesn't.Įdited to add This is just one of many aspects of SQL server licensing and it's only relevant if you choose the Server+CAL licensing model. For example, if an employee sends a Microsoft Excel version of a report to another employee, the receiving employee does not require a CAL. An exception to this includes the manual transfer of data from employee to employee. This remains true no matter how many tiers of hardware or software exist between the server running SQL Server and the client devices that ultimately use its data, services, or functionality. This is for SQL 2005 but I don't think it is any different for other versions:Ī CAL is required for each distinct device or user to the multiplexing or pooling software or hardware front end. Microsoft use the term "multiplexing" for the scenario you describe. You need CAL's for every user of the business logic server, even though there is no direct connection between them and the SQL server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |