| Hal Berenson 2002-10-05, 9:07 pm |
| Not really the best place for a licensing question, but
then I don't think any newsgroup is. You need to call
Microsoft to get this question answered. So even though
I'm going to give you my take on it, please don't rely on
my answer. Call MS to get something official.
You don't say what version of SQL Server, but I'll assume
SQL Server 2000. Then I'll discuss a variation. Note
that SQL Server licensing info is at
http://www.microsoft.com/sql/howtob...rverlicensing.a
sp?SD=GN&LN=en-us&gssnb=1
SQL Server 2000 has two licensing models, per-CPU and per-
Seat. CALS only apply to per-Seat. SQL Server
explicitly disallows (from a licensing perspective) the
use of software that multiplexes multiple end-users down
to a smaller number of database users. So with per-Seat
licensing you must purchase enough CALS to cover every
individual user who runs an application that eventually
talks to a SQL Server. If 20 people can run the client
app on the Citrix box, then you need 20 CALS to cover
them.
Earlier versions of SQL Server supported a "per-server"
licensing model in which you would purchase the number of
CALS for the maximum number of concurrent users of
applications accessing SQL Server. The per-CPU model
replaced this in SQL Server 2000.
For more help on licensing see
http://www.microsoft.com/licensing/default.asp?
SD=GN&LN=en-us&gssnb=1
Hal
>-----Original Message-----
>Anyone know how I can tell how many SQL CALs I need in
the
>following enviroment:
>
>I have a three win2k standard servers, a DC, an SQL, and
a
>Citrix. Citrix users use a client app loaded on the
citrix
>server to access the main app on the DC. The app on the
DC
>them gets its info off of the SQL server.
>
>Initialy, I set these up with:
>
>20 "per seat" Win2k CALs
>20 Terminal Server CALs
>20 SQL CALs
>and the metaframe CALs also.
>
>I've come to find out that we need more CALs but I don't
>know how to tell how many SQL cals we need. The SQL CALs
>don't show up in AD licensing MMC. Any ideas?
>
>P.S. forgive if this is posted in wrong forum - new to
>this.
>
>.
>
|