My remote network consists of 3 servers (Web, Terminal/Production, Database). All internal users access these three servers using Device CALs from my Terminal Server Licensing pool.
I am about to purchase SQL Server 2005 Standard and install it on the Database server.
The SQL server will be queried/touched by:
- apps on the Web server (not public so concurrency, while important, is not extremely high)
- users on the Terminal server (i.e. from within Microsoft Access via ODBC)
- developers/administrators on the Database server (directly logging in to the server)
From one perspective, I would say that I need 3 Device CALs only: There are but 3 devices which will touch the SQL server within the network, since remote users connect via Terminal Services. Is this scenario realistic?
From another perspective, I could imagine that Microsoft would ignore the local devices in use and look out toward the end-user devices, such as my home PC, even though my actions are routed through a local device. Should I be considering User CALs for this reason?
From a third perspective, I realize that more than one simultaneous query will be passed to SQL Server from, say, multiple concurrent users on the web applications, or multiple users on the Terminal server querying the back-end database, etc. If I am using Device CALs, and knowing the 3 servers within my network (despite the fact that there are multiple external users, both web-based and terminal-based), should I be OK?