Groups | Blog | Home
all groups > sql server (microsoft) > april 2007 >

sql server (microsoft) : Licensing for SQL 2000 and SQL 2005 for public website that uses database?



Leythos
4/13/2007 10:00:11 PM
I'm under the impression that SQL 2000 requires a CPU License for any
internet website that allows access to a database - even if you don't use
Windows authentication.

Is this true of SQL 2005 Workgroup (or any other version) also?

--
Leythos
David Portas
4/14/2007 1:27:17 AM
[quoted text, click to view]


The licence agreement is the same for Standard, Workgroup and
Enterprise.
Express is different and is free to install and licence.

--
David Portas, SQL Server MVP

Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.

SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
Leythos
4/14/2007 11:08:27 AM
[quoted text, click to view]

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
Greg Linwood
4/14/2007 3:09:42 PM
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..

Regards,
Greg Linwood
SQL Server MVP
http://blogs.sqlserver.org.au/blogs/greg_linwood

[quoted text, click to view]

Leythos
4/14/2007 3:30:13 PM
[quoted text, click to view]

That's exactly what I thought, a CPU license is needed for web apps that
cater to anon access with a SQL backend.

It's funny watching software groups sell clients on SQL 2000 Std or 2005
WG and then only buy CAL's instead of a CPU licenese.



--
Leythos
Tibor Karaszi
4/14/2007 8:14:37 PM
[quoted text, click to view]

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]
AddThis Social Bookmark Button