[quoted text, click to view] > So the question still stands - if you have an IIS site that provides
> information from the SQL 2005 database (Workgroup or Standard) and does
> not use Windows Authentication for credentials, does it need a CPU license
> like SQL 2000 did?
It is irrelevant as for the SQL Server licensing whether the client connects using Windows or SQL
Server authentication. If you can assure that every one that uses that SQL Server though your web
site has a SQL Server CAL, then you can go Per Seat. If not, you have to go Per Processor.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp http://sqlblog.com/blogs/tibor_karaszi [quoted text, click to view] "Leythos" <Void@nowhere.lan> wrote in message news:1176566907_9957@sp6iad.superfeed.net...
> On Sat, 14 Apr 2007 15:09:42 +1000, Greg Linwood wrote:
>
>> If you're concerned about license cost, have you considered SQL Server 2005
>> Express Edition?
>>
>> It's free & has nearly all funcionality of the DB engine, though little in
>> the way of GUI tools & some resource constraints..
>
> Yes, I've looked at Express, but, it doesn't have all of the features that
> the medical database requires for performance, not anywhere near enough.
>
> So the question still stands - if you have an IIS site that provides
> information from the SQL 2005 database (Workgroup or Standard) and does
> not use Windows Authentication for credentials, does it need a CPU license
> like SQL 2000 did?
>
>
>
> --
> Leythos
> spam999free@rrohio.com (remove 999 for proper email address)