Since Project Server only requires SQL User CALs for the following
accounts:
MSProjectServerUser
MSProjectUser
SQLadmin or SA
OLAP account (for building OLAP Cubes)
OLAP Role Group (for accessing OLAP Cube data in Portfolio Analyzer
Views)
I would think you would only need:
1 SQL Server License
5 SQL User CALs
But as I read it the SQL licensing at:
read it again.
Server plus device CAL licensing is optimal for customers who do not need access beyond the firewall and who have relatively low
CAL-to-server ratios (for example, approximately 25 or fewer devices per processor for Standard Edition and 75 or fewer devices per
processor for Enterprise Edition). The device CAL model will likely be more cost effective than user CALs if there are multiple
users per device (for example, a call center or an airport kiosk).
Server plus user CAL licensing is optimal for customers who do not need access beyond the firewall and who have relatively low
CAL-to-server ratios (for example, approximately 25 or fewer users per processor for Standard Edition and 75 or fewer users per
processor for Enterprise Edition). The user CAL model will likely be more cost effective than device CALs if there are multiple
devices per user (for example, a user has a laptop and handheld computer accessing SQL Server).
Accounts aren't Users in Microsoft licencing. Accounts aren't Devices in Microsoft SQL licencing.
Even though some legacy licence counting applications say they can be.
Users are users, therfore 600 Project users (web or thick client) being served by the SQL Service. 601 SQL CALS
Even SQL driven web servers (the only one IUSER account arguement) need one call per user(person or device)
Webs have many users, hopefully millions. The break even point on USER/device CALS vs Processor licencing is
very low (I remember calculating ~50 on dual proc/Standard edition). Applicable really only to dedicated single application access
in a tightly controlled network.
What of per device you say, Project Server and a single client, 600 people at one PC is a lot.
plus you loose the distributed nature of Project Server which is why you buy it.
Now this has taken on a bit of a rant. But I really wish the misinformation would stop.
I went to my IT manager, tried to explain SQL licencing to him, he came back at me with "well the reseller said".
Then a few days later "the reseller said" THE OPPOSITE. He didn't understand SQL licencing either.
Why is that bad besides the huge waste of time the chat was...That reseller employee leaves the resller.
A year later you get audited. 5 SQL CALS, 100's of PWA users all benefiting from the SQL Service,
whose responsibility is it that you are either short CAL's (a bunch of them) or not in possession of proc licences?
The guy who gave you bad advice, that is no longer a Microsoft sales person and all that he left you with was a "but he said".
This is going to change yet again slightly next version but for now. Think business strategy....
A low client count serving SQL machine still needs backup restore support, and fast hardware.
This for the most part can scale to serve backup for example one user or a thousand users
ex. a tape drive at $5000 for 1 person or $5000 for thousands of people which is the better value?
At this moment in time, unless you are a very small single purpose company and can enumerate all the SQL
queries from users/devices just get the proc licencing.
