Like the subject says - I'm a newbie with this stuff. I know pretty much
nothing about SQL.
I work for a small school system and we are preparing to install a new
student management program. It uses SQL Server 2000, and all the access will
be from the web. Basically, a school administrator can go in and look at a
student's records with this, and they are planning to have the teachers
enter their absentees, tardies, and so forth at the beginning of each class
period. So, several times a day we will have something like 50 teachers
entering their absentees within say, 5 minutes of each other. I haven't been
able to actually use the program yet, just see a brief demo. I assume they
will just pull up a class roll, check off the pupils who are present, and
My question is, do we need a SQL CAL for each of these 50 users? My
understanding is that we need 1 CAL for each concurrent access, meaning that
if only 25 people access it at a time we only need 25, even if 100 people
are actually using it. I'm just not sure how long each connection to the
server will last. Does that make sense? Do I need to know more about how the
app actually works or is it possible to come up with an answer with the
limited info I have available?
The real question we are dealing with is do we want to use CAL's or do we
want to purchase the 'per processor' version which I understand allows you
to have as many simutaneous users you need.
Any help, including suggestions as to where else I might look to find this
info, is appreciated.