Client license question

Hi all,
This is a question related to licensing...
Environment :
Server 1 - Windows 2000/2003 with SQL Server 2000
Server 2 - webserver (IIS/Apache/etc)
Server 2 is connecting to the SQL Server database (Server
1) using SQL Server authentication (i.e.
SQLServerAccount/Password)
There are multiple users connecting to the webserver
using anonymous authentication to pull out some data from
the SQL Server.
There is going to be only one user connected to the SQL
Server (which is 'SQLServerAccount') ... and is going to
have several instances for each user...
Basically the external users will not have access to the
SQL Server database ... without using the webbased front-
end application...
How many licenses (SQL Server) do I need for the
server/clients?
Best regards,
Alin V.
As I posted within .server:
Is the web server only serving up pages (and data) to a distinct, known set
of individuals (such as employees or partners that have access to the web
site)? If so, it is my understanding that you can probably go the user CAL
route.
Otherwise you will have to go the PER PROCESSOR route
http://www.microsoft.com/sql/howtobuy/default.asp
http://www.microsoft.com/sql/howtobu...rlicensing.asp
Keith
"Alin" <anonymous@.discussions.microsoft.com> wrote in message
news:2575401c4606b$b6f56840$a501280a@.phx.gbl...
> Hi all,
> This is a question related to licensing...
> Environment :
> Server 1 - Windows 2000/2003 with SQL Server 2000
> Server 2 - webserver (IIS/Apache/etc)
> Server 2 is connecting to the SQL Server database (Server
> 1) using SQL Server authentication (i.e.
> SQLServerAccount/Password)
> There are multiple users connecting to the webserver
> using anonymous authentication to pull out some data from
> the SQL Server.
> There is going to be only one user connected to the SQL
> Server (which is 'SQLServerAccount') ... and is going to
> have several instances for each user...
> Basically the external users will not have access to the
> SQL Server database ... without using the webbased front-
> end application...
> How many licenses (SQL Server) do I need for the
> server/clients?
> Best regards,
> Alin V.
>
|||Alin,
I think that anyone interacting with the database from a client
computer, whether that interaction passes through an intermediary such
as a web server or not, is considered a client. If your anonymous user
requests are handled through transactions specifically for them against
the database, they need to be covered by either individual client
licenses or by a processor license on the web server. You should
probably contact Microsoft for an official answer, but I think the only
possible situation in which you can consider the web server to be the
sole client would be if the web server's interactions with the database
were independent of the anonymous users' interactions with the
webserver. This might be the case if the web server only served up a
collection of canned reports off the data. The SQL Server could supply
the information for these reports, but the users would only be able to
select which report they wanted to see, or request a report with some
sort of customization that could be handled by the web server alone. As
soon as the database is asked specific questions on behalf of someone,
that someone has become a client.
When it's released, SQL Server 2005 Express Edition may be a zero-cost
solution as a back-end database for many kinds of Web applications.
See http://lab.msdn.microsoft.com/express/sql/default.aspx.
Steve Kass
Drew University
Alin wrote:

>Hi all,
> This is a question related to licensing...
> Environment :
> Server 1 - Windows 2000/2003 with SQL Server 2000
> Server 2 - webserver (IIS/Apache/etc)
> Server 2 is connecting to the SQL Server database (Server
>1) using SQL Server authentication (i.e.
>SQLServerAccount/Password)
> There are multiple users connecting to the webserver
>using anonymous authentication to pull out some data from
>the SQL Server.
> There is going to be only one user connected to the SQL
>Server (which is 'SQLServerAccount') ... and is going to
>have several instances for each user...
> Basically the external users will not have access to the
>SQL Server database ... without using the webbased front-
>end application...
> How many licenses (SQL Server) do I need for the
>server/clients?
>Best regards,
> Alin V.
>
>
|||A small correction - I should have said "processor license on Server 1,"
not "processor license on the web server
SK
Steve Kass wrote:

> Alin,
> I think that anyone interacting with the database from a client
> computer, whether that interaction passes through an intermediary such
> as a web server or not, is considered a client. If your anonymous
> user requests are handled through transactions specifically for them
> against the database, they need to be covered by either individual
> client licenses or by a processor license on the web server. You
> should probably contact Microsoft for an official answer, but I think
> the only possible situation in which you can consider the web server
> to be the sole client would be if the web server's interactions with
> the database were independent of the anonymous users' interactions
> with the webserver. This might be the case if the web server only
> served up a collection of canned reports off the data. The SQL Server
> could supply the information for these reports, but the users would
> only be able to select which report they wanted to see, or request a
> report with some sort of customization that could be handled by the
> web server alone. As soon as the database is asked specific questions
> on behalf of someone, that someone has become a client.
> When it's released, SQL Server 2005 Express Edition may be a
> zero-cost solution as a back-end database for many kinds of Web
> applications. See
> http://lab.msdn.microsoft.com/express/sql/default.aspx.
> Steve Kass
> Drew University
> Alin wrote:
>
|||Thanks guys for your quick responses... from the License
Agreement I got the same feeling...
Best regards,
Alin V.

>--Original Message--
>Alin,
> I think that anyone interacting with the database from
a client
>computer, whether that interaction passes through an
intermediary such
>as a web server or not, is considered a client. If your
anonymous user
>requests are handled through transactions specifically
for them against
>the database, they need to be covered by either
individual client
>licenses or by a processor license on the web server.
You should
>probably contact Microsoft for an official answer, but I
think the only
>possible situation in which you can consider the web
server to be the
>sole client would be if the web server's interactions
with the database
>were independent of the anonymous users' interactions
with the
>webserver. This might be the case if the web server only
served up a
>collection of canned reports off the data. The SQL
Server could supply
>the information for these reports, but the users would
only be able to
>select which report they wanted to see, or request a
report with some
>sort of customization that could be handled by the web
server alone. As
>soon as the database is asked specific questions on
behalf of someone,
>that someone has become a client.
> When it's released, SQL Server 2005 Express Edition may
be a zero-cost
>solution as a back-end database for many kinds of Web
applications.
>See
http://lab.msdn.microsoft.com/express/sql/default.aspx.[vbcol=seagreen]
>Steve Kass
>Drew University
>Alin wrote:
(Server[vbcol=seagreen]
from[vbcol=seagreen]
the
>.
>