SQL Server 7 CAL question

Question

Post reply

SQL Server 7 CAL question

aadba

Mr or Mrs. 500

Points: 569
More actions
October 29, 2003 at 9:54 pm

#59385

I am running a small web hosting company, I have been using MS Access for database driven web sites. Recently I was asked if I offer SQL/Server, so I went ahead & purchased SQL/Server 7 for 20 CAL.

Does 20 CAL means that only 20 clients/20 web sites can use the SQL Server database? What about concurrent users who are accessing the web site with SQL Server on the backend, do I have to be concerned about the number of concurrent users accessing each web site too?

Any input/advise is greatly appreciated. I bought SQL Server thru eBay, I wanted to make sure I am using the licenses properly..

Thank you,

@tom

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Jonathan SSC-Insane Points: 20427 More actions · Answer 1

20 CALs in SQL 7 meant that you could choose either "per seat" or "per server" licensing model. With one server, the obvious choice was "per server", as that meant you could support up to 20 concurrent users. If you added more SQL 7 Servers, the "per seat" licensing often became more economical, and you had a one-time right to switch from "per server" to (nonconcurrent device-specific) "per seat". There was also a special "Internet Connector" that allowed an unlimited number of concurrent external internet connections.

http://www.microsoft.com/sql/howtobuy/70/pricing.asp

I am using the past tense, as the licensing for the current version (SQL Server 2000) is very different.

http://www.microsoft.com/sql/howtobuy/sqlserverlicensing.asp

With either version, Microsoft is very clear that every user of an application that uses SQL Server, no matter how many layers removed from the database server, requires a SQL Server license.

--Jonathan

NPeeters SSChampion Points: 12358 More actions · Answer 2

With 20 CAL's, you can only have 20 concurrent users. For a webserver, one user can be compared to a single session on IIS.

So for every (concurrent) visitor of any site on your server, you should have a CAL.

Like Jonathan stated, for any kind of public website you should buy the Internet Connector kind of license...

With SQL Server 2000, you have the option of buying a per processor license, which means you do not need any CALs at all. This can be compared to the Internet Connector license.

Jonathan SSC-Insane Points: 20427 More actions · Answer 3

quote:

With 20 CAL's, you can only have 20 concurrent users. For a webserver, one user can be compared to a single session on IIS.

So for every (concurrent) visitor of any site on your server, you should have a CAL.

This is only true for versions prior to SQL Server 2000, which has no model, other than per processor licenses, for concurrent licensing.

--Jonathan

aadba Mr or Mrs. 500 Points: 569 More actions · Answer 4

aadba

Mr or Mrs. 500

Points: 569

October 30, 2003 at 10:36 am

#480343

Thank you guys for your input.

One more question, for the web hosting purposes ONLY, do I need Processor Licensing & Internet Connector Licensing or Internet Connector Licensing would suffice?

Thank you.

Jonathan SSC-Insane Points: 20427 More actions · Answer 5

quote:

Thank you guys for your input.

One more question, for the web hosting purposes ONLY, do I need Processor Licensing & Internet Connector Licensing or Internet Connector Licensing would suffice?

Thank you.

With SQL 7, it's Internet Connector license; with SQL Server 2000, it's per-processor licensing. I doubt you can still purchase a SQL 7 Internet Connector license, but you can purchase SQL Server 2000 licenses and then use them with SQL Server 7 "for a reasonable period of time." Of course, this means your recent purchase of SQL Server 7 is sunk, but your clients might rightly grouse if you provide them a version that was superceded more than two years ago...

--Jonathan