SQL Server CAL Licensing Requirement to be legit
Posted on 2017-11-14
We are running a document management system called FileDirector. The main server app is .NET 4.0 based and is hosted on IIS, and the client app (running on Windows workstations) connects to the FileDirector server via the HTTP protocol. FileDirector's document related and configuration data is all contained in an SQL Server instance running on the same server.
Now, before we fork out loads of money for SQL Server, I want to be sure I understand the licensing requirement. SQL Express is not going to be good enough for the job, as we're exceeding the 10GB ceiling by quite a lot (DB is about 30GB). I'm looking at licensing SQL Standard, but my question is about our obligations re Client Access Licenses. Am I correct in understanding that for every FileDirector client app that connects into the FileDirector Server (which has SQL Server on the back-end) I will need either a User or Machine CAL? So, for examples sake, if we have a total of 17 users of the FileDirector client (about what we have), I'll need to buy a license of SQL Standard, but then 17 User CALs (assuming I'm choosing the User licensing route)?
Or can we license just SQL Standard and a single Machine CAL for the FileDirector Server directly connecting into it (I already very highly doubt this, but just want people to confirm this would not be correctly licensed).
Many thanks in advance :-)