November 7, 2011 at 3:32 am
Hello Everyone,
I hope someone out there will have an answer for this. I need to make sure we have enough client licences to cover us. And I am not entirely clear on what constitutes as needing a licence.
If you have 10 users that use an application that has a SQL backend database, and the users use a client module of the application (not accessing SQL directly, but I guess, indirectly), do I they require a SQL client licence each? Or would I require just one client license to cover the main central part of the application that accesses and writes to the database with what is received from the client module (end user)?
Thank you in advance for any help, I hope I am making sense.
Kind Regards,
D.
November 7, 2011 at 4:30 am
Duran (11/7/2011)
If you have 10 users that use an application that has a SQL backend database, and the users use a client module of the application (not accessing SQL directly, but I guess, indirectly), do I they require a SQL client licence each?
Yes
Or would I require just one client license to cover the main central part of the application that accesses and writes to the database with what is received from the client module (end user)?
The application is not a user. The end user (the one sitting at the keyboard) is a user.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 7, 2011 at 12:29 pm
Additionally, if those users are accessing an application on another computer that is not their workstation (client-server/multi-tier/etc), then the server that is accessing SQL Server requires a Machine CAL in addition to each user requiring a separate User CAL.
Eddie Wuerch
MCM: SQL
November 8, 2011 at 5:30 am
Thank you for the replies. The users all have their own workstations so I dont think I need to worry about the machine licence. Thanks again!
Regards,
D.
November 8, 2011 at 7:56 am
Think of it this way, as a Microsoft rep once told me... If a user or a machine directly or indirectly touches SQL Server, it needs a CAL. A great example of this is w webserver that is hosting a website that accesses SQL Server. In that case, you would need a CAL for every person that goes to that website. This is why they have licenses with unlimited CALs.
Thanks,
Jared
Jared
CE - Microsoft
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply