views:

248

answers:

2

I would like to user SQL Server 2008 for my public web site.

It will be installed on a quad-core CPU and it will be used only through several web applications installed on the same server.

My options are:

  1. Per-CPU license - around 5-6k US$
  2. Per client - around 1k US$ + cost per client

Now, I don't understand the second model. I have thousands of users, but they all access the SQL Server through ASP.NET SqlClient connections, and they are pooled. I believe the default is 20 pooled connections.

So, if I choose per-client option, do I:

  1. Pay 1 CAL total
  2. Pay 1 CAL for each pooled ASP.NET SQL connection
  3. Pay 1 CAL for every web user accessing my web site

Additional info:

  • BizSpark is not an option, since the company is too large
  • We have SQL 2000 license
A: 

When you have a public facing site you need a per CPU licence. The per user is only for internal users.

Shiraz Bhaiji
+1  A: 

I believe a client CAL is not about a pooled connection, but a physical user, e.g. if you have 20 pooled connection, but 100 users accessing the website, you have to buy 100 CALs regardless . Generally this scheme is less expensive in some situation, but not when using public websites.

That being said, you might want to take a look at Bizspark program that gives you SQL Server 2008 for free at least for the first 3 years.

Alternatives in case $5-6k per CPU is more than you can afford: SQL Server Express (max 4GB database) or some other database - Postgresql etc.

SQL Anywhere is pretty solid in my experience and they have a free web edition specifically for webapps. It supports Entity Framework as well.

liggett78

related questions