Nah...
You will be able to get/process as many
requests as your clients request.
It's just that you'll be in technical violation
of your license agreement if you do.
There's no hard-wired limit.
It's up to you, and your sense of fair play,
or up to Microsoft lawyers if they find out.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
======================
"Ben" <Be*@discussions.microsoft.com> wrote in message
news:84**********************************@microsof t.com...
Thanks for the reply.
Just to confirm one thing:
With 20 CALs, the no. of process ID's for the procedures that the web
application (using sp_who) called is up to 20 only?
Thanks,
Ben
"Cowboy (Gregory A. Beamer) - MVP" wrote:
If you are sitting at 20 CALs, no more than 20 clients can ever be
connected
at one time. While I am not sure there is a definitive answer on the
pooling
size, I would not have a pool larger than 20, as you only have 20
licenses.
The 21st person to get a connection object would violate the license.
---
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
***************************
Think Outside the Box!
***************************
"Ben" wrote:
> We have a MSSQL with per seat license of 20. The MSSQL is sitting in
> the same
> machine as the asp.net.
>
> Does that mean that the the no. of connections and Max Pool Size are
> limited
> up to 20 only?
>
> Thanks,
> Ben