![sql server client access license sql server client access license](https://metrixdata360.com/wp-content/uploads/2020/06/Away-Button.png)
User accessing a static Excel file created thro TSQL/SSIS. MS Excel directly querying SQL via MS Query.CAL required MS Excel pivot table accessing a SSAS Cube.CAL required And you are absolutely right about separating components. I think that websites typically fall into the "multiplexer" scenario in the document I mentioned.
SQL SERVER CLIENT ACCESS LICENSE SOFTWARE
the license for the software on the disk is NOT for the components, but for the CPU or machine it is purchased for. If the report is exported to a file and placed somewhere for retrieval, then only the service that creates that file needs the CAL.Īlso, you probably already know this but for others, a separate license is required when placing SSRS on a separate box from SQL Server even if SSRS is not installed on the same box as SQL Server i.e. So, if these reports are deployed in a fashion where anyone can access them and that access requires touching SQL Server then they need a CAL. For example, if a website touches SQL Server then every person who visits that website requires a cal i.e. When talking to Microsoft about this, they said any person or device directly or indirectly touching the SQL Server requires a CAL. I can take the view (and explain to my FD) that to cover off licence compliance we should assume that we need CALs for "N" users to receive such emails.but as I sure you will appreciate.if there are costs to be saved, then save them !!Īlso.I have read elsewhere, but cannot now find the url, that if we used TSQL to generate an Excel spreadsheet.the recipient would require a CAL.but if that spreadsheet was then forwarded on.all other recipients would be CAL "exempt"Īpologies for appearing to be financially pedantic.but thats the situation i find myself in it would appear a CAL is required for each recipient, because the SQL service generated the initial email. "A SQL Server User CAL is required in order for a user (employee, customer, partner, and so on) to access or use the services or functionality of Microsoft SQL Server." On re reading this part (extract from "2008 SQL Licensing Overview final.docx") do the "N" recipients require a "single user CAL".? JOIN AS pĮXEC _send_dbmail = 'Work Order = 'HTML' Td = (p.ListPrice - p.StandardCost) * wo.OrderQtyįROM as wo To try and be more specific.say for example we intend to email "N" users with a daily report summary Thanks Elliott,we have read this doc and many others "views" on this subject. "A SQL Server User CAL is required in order for a user (employee, customer, partner, and so on) to access or use the services or functionality of Microsoft SQL Server. Processor sockets, not cores IN the processor are licensed, ie 2 x 4 core processors is 2 processors not 8. I believe a user of SSRS fully fits within the definition and WHAT you connect to to report on is not relevant, you connected to SSRS, you are a user.įor many businesses processor licensing is a better solution. If these components are in a separate server than the main database server, then they require an additional license of each additional server where they are installed." To use any of these components, the server on which Business Intelligence is installed must have a valid SQL Server 2008 license. "The Business Intelligence components for SQL Server 2008 include Analysis Services, Reporting Services, and Integration Services. A single user CAL grants access to multiple servers for one user.
![sql server client access license sql server client access license](https://proceedings.esri.com/library/userconf/proc02/pap0572/p05722.gif)
A single device CAL grants access to multiple servers for one device (CAL must be same version as latest version of any of the servers).
SQL SERVER CLIENT ACCESS LICENSE PLUS
The Server plus user CAL model will likely be more cost effective if there are multiple devices per user (for example, a user who has a desktop PC, laptop, PDA, and so forth).Ī CAL is not software it is a legal document granting a device or user access to server software. From the doc "2008 SQL Licensing Overview final.docx":