ms licencing is a very long and complicated business, but as I understand it
there are basically 2 licencing models:
1. CAL licencing - this requires you to have a licence for each user that
uses the application (IIRC it talks about a 'device' but basically it's one
licence per user)
2. server based licencing - you buy a licence for the server and it can be
used by as many people as you want
the licencing restrictrions apply regardless of how (of if) users
authenticate to the application, and the model is basically the same for SQL
server as it is for windows itself.
so basically if your app is on the internet, you will need to use the server
licencing model.
note 1: obviously many of these restrictions cannot be enforced in
software - if you use your own authentication, MS has no way of knowing how
many users are using it so you could cheat them (this would be illegal)
note 2: there is a cheap version of windows server especially for running
web sites but you are explicitly forbidden from running SQL server on it (or
connecting to another SQL server from it)
Andy
"Hani Atassi" <ha**@community.nospam> wrote in message
news:15**********************************@microsof t.com...
If i am using a form type authintication, do I need a licence for each
logged
in user?
The application maintain their own user list and they are not Windows
accounts.
If I am using SQL Server from my web application, and SQL server uses 1
windows account, how many CAL do I need for my web application to run on
the
internet?