Re: Client license question

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Steve Kass (skass_at_drew.edu)
Date: 07/03/04 

Date: Sat, 03 Jul 2004 01:13:41 -0400

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.
>
>
>

Relevant Pages

  • Re: Remobjects v KBM
    ... >> client query components) follow from that. ... Then, connections can be created to say SQL Server, Oracle, Interbase and ... can then be created from the abstract dataset definition in 'customers' to ... implicitly - this makes your code not be database connection specific). ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: Opinions needed about the best "Middleware suite" kbmMW vs. RODA
    ... kbmMW supports cross db in such way that all you need to do in your application is to set one property to switch to ... What one have to concentrate about is minimizing the amount of data moved from the app server to the client. ... C/S setup's usually have a quite active chatter going on between the client and the database, ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: Help with first VB application - Data Entry form
    ... I assumed a desktop / winform client application ... time' stamp from the database machine - control machine ... ... problem solved - web server is control system. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Help with first VB application - Data Entry form
    ... I assumed a desktop / winform client application ... time' stamp from the database machine - control machine ... ... problem solved - web server is control system. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Help with first VB application - Data Entry form
    ... JavaScript, for example) and thus, will get the time from the web server, ... function on the client. ... the database is not the place to put a time stamp of this ...
    (microsoft.public.dotnet.languages.vb)