Martin Feuersteiner (theintrepidfox@hotmail.com) writes:[color=blue]
> What I want to do it is to have an ASP.NET application that uses MSSQL
> as a backend. I'm using SQL Authentication and e.g. Each employee for
> Comapny A will have a login e.g. Employee1, Employee2 with separate
> passwords for each employe e.g. Pass1, Pass2 etc.. Makes Sense?[/color]
Yes, but it's better to use Windows Authentication. Now, exactly how
you do that over ASP .Net, I don't know. But that means that the web
page would recognize who the user is logged into to Window as, and
then SQL Server would pick up those credentials.
[color=blue]
> As far I understand, logins map to users so is it possible that Employee1
> and Employee2 map to the same user called e.g. 'Employee'?[/color]
No, all users must map to different logins. (But it can happen that
users map no login at all.)
[color=blue]
> And how do I know how many MSSQL CALs I need?
> Two (for each employee login) or only one for the user 'Employee'?[/color]
Licensing questions always leaves me in a maze, so i decline to answer
that bit.
--
Erland Sommarskog, SQL Server MVP,
esquel@sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp