IIS and SQL Server CAL question

Hello, I'm sure this is a common question but I couldn't find the answer. I'm
setting up a web site with a SQL Server 2000 backend. The only purpose of the
database server will be to work with IIS in delivering web content. Since
obviously it is possible for many web requests to hit IIS simultaneously,
would it be possible to exceed the CAL limit if IIS tried to connect too many
times at once? Or is IIS considered to be a single client?
Many thanks for your help,
BrianHi
No, if SQL Server is used to provide data for a Web Server, you have to use
Per Processor Licensing. CAL or Device licensing is not allowed.
Look at the licensing page on www.microsoft.com/sql
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Brian" <Brian@.discussions.microsoft.com> wrote in message
news:13E2868A-F1CF-4ADB-8574-1F73433F778F@.microsoft.com...
> Hello, I'm sure this is a common question but I couldn't find the answer.
I'm
> setting up a web site with a SQL Server 2000 backend. The only purpose of
the
> database server will be to work with IIS in delivering web content. Since
> obviously it is possible for many web requests to hit IIS simultaneously,
> would it be possible to exceed the CAL limit if IIS tried to connect too
many
> times at once? Or is IIS considered to be a single client?
> Many thanks for your help,
> Brian
>|||Hello Mike,
Thanks for your reply. I looked at the page you referenced and read the
document "SQL_UnderstandingDBPrici
ng.doc", but nowhere did it indicate what you have described. In fact, the
document didn't describe the concept of client access licenses at all. Are
you saying that CAL specifically excludes web servers? Where can I find an
authoritative resource on this?
Brian
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> No, if SQL Server is used to provide data for a Web Server, you have to use
> Per Processor Licensing. CAL or Device licensing is not allowed.
> Look at the licensing page on www.microsoft.com/sql
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Brian" <Brian@.discussions.microsoft.com> wrote in message
> news:13E2868A-F1CF-4ADB-8574-1F73433F778F@.microsoft.com...
> > Hello, I'm sure this is a common question but I couldn't find the answer.
> I'm
> > setting up a web site with a SQL Server 2000 backend. The only purpose of
> the
> > database server will be to work with IIS in delivering web content. Since
> > obviously it is possible for many web requests to hit IIS simultaneously,
> > would it be possible to exceed the CAL limit if IIS tried to connect too
> many
> > times at once? Or is IIS considered to be a single client?
> >
> > Many thanks for your help,
> > Brian
> >
> >
>
>|||I'm pretty sure you will need to use processor licensing, unless you enforce
Windows authentication (which allows you to tie each web user to a specific
CAL).
On 3/10/05 7:47 PM, in article
13E2868A-F1CF-4ADB-8574-1F73433F778F@.microsoft.com, "Brian"
<Brian@.discussions.microsoft.com> wrote:
> Hello, I'm sure this is a common question but I couldn't find the answer. I'm
> setting up a web site with a SQL Server 2000 backend. The only purpose of the
> database server will be to work with IIS in delivering web content. Since
> obviously it is possible for many web requests to hit IIS simultaneously,
> would it be possible to exceed the CAL limit if IIS tried to connect too many
> times at once? Or is IIS considered to be a single client?
> Many thanks for your help,
> Brian
>|||http://www.microsoft.com/resources/sam/lic_cal.mspx#perprocessor
http://www.microsoft.com/resources/documentation/sql/2000/all/reskit/en-us/p
art2/c0461.mspx
http://www.windowsitpro.com/Article/ArticleID/15606/15606.html
http://64.233.161.104/search?q=cache:OAbE4tuJTbEJ:https://www.microware.ch/w
eb/en/services/letter/Letter_0404MSEN.pdf+cal+processor+licensing+web+%22sql
+server+2000%22&hl=en&client=safari
On 3/10/05 8:23 PM, in article
09FF5789-2BEB-4864-8BCB-BD3A9E31EC23@.microsoft.com, "Brian"
<Brian@.discussions.microsoft.com> wrote:
> Hello Mike,
> Thanks for your reply. I looked at the page you referenced and read the
> document "SQL_UnderstandingDBPrici
> ng.doc", but nowhere did it indicate what you have described. In fact, the
> document didn't describe the concept of client access licenses at all. Are
> you saying that CAL specifically excludes web servers? Where can I find an
> authoritative resource on this?
> Brian
> "Mike Epprecht (SQL MVP)" wrote:
>> Hi
>> No, if SQL Server is used to provide data for a Web Server, you have to use
>> Per Processor Licensing. CAL or Device licensing is not allowed.
>> Look at the licensing page on www.microsoft.com/sql
>> Regards
>> --
>> Mike Epprecht, Microsoft SQL Server MVP
>> Zurich, Switzerland
>> IM: mike@.epprecht.net
>> MVP Program: http://www.microsoft.com/mvp
>> Blog: http://www.msmvps.com/epprecht/
>> "Brian" <Brian@.discussions.microsoft.com> wrote in message
>> news:13E2868A-F1CF-4ADB-8574-1F73433F778F@.microsoft.com...
>> Hello, I'm sure this is a common question but I couldn't find the answer.
>> I'm
>> setting up a web site with a SQL Server 2000 backend. The only purpose of
>> the
>> database server will be to work with IIS in delivering web content. Since
>> obviously it is possible for many web requests to hit IIS simultaneously,
>> would it be possible to exceed the CAL limit if IIS tried to connect too
>> many
>> times at once? Or is IIS considered to be a single client?
>> Many thanks for your help,
>> Brian
>>
>>|||Thanks, Aaron.
"Aaron [SQL Server MVP]" wrote:
> http://www.microsoft.com/resources/sam/lic_cal.mspx#perprocessor
> http://www.microsoft.com/resources/documentation/sql/2000/all/reskit/en-us/p
> art2/c0461.mspx
> http://www.windowsitpro.com/Article/ArticleID/15606/15606.html
> http://64.233.161.104/search?q=cache:OAbE4tuJTbEJ:https://www.microware.ch/w
> eb/en/services/letter/Letter_0404MSEN.pdf+cal+processor+licensing+web+%22sql
> +server+2000%22&hl=en&client=safari
> On 3/10/05 8:23 PM, in article
> 09FF5789-2BEB-4864-8BCB-BD3A9E31EC23@.microsoft.com, "Brian"
> <Brian@.discussions.microsoft.com> wrote:
> > Hello Mike,
> >
> > Thanks for your reply. I looked at the page you referenced and read the
> > document "SQL_UnderstandingDBPrici
> > ng.doc", but nowhere did it indicate what you have described. In fact, the
> > document didn't describe the concept of client access licenses at all. Are
> > you saying that CAL specifically excludes web servers? Where can I find an
> > authoritative resource on this?
> >
> > Brian
> >
> > "Mike Epprecht (SQL MVP)" wrote:
> >
> >> Hi
> >>
> >> No, if SQL Server is used to provide data for a Web Server, you have to use
> >> Per Processor Licensing. CAL or Device licensing is not allowed.
> >>
> >> Look at the licensing page on www.microsoft.com/sql
> >>
> >> Regards
> >> --
> >> Mike Epprecht, Microsoft SQL Server MVP
> >> Zurich, Switzerland
> >>
> >> IM: mike@.epprecht.net
> >>
> >> MVP Program: http://www.microsoft.com/mvp
> >>
> >> Blog: http://www.msmvps.com/epprecht/
> >>
> >> "Brian" <Brian@.discussions.microsoft.com> wrote in message
> >> news:13E2868A-F1CF-4ADB-8574-1F73433F778F@.microsoft.com...
> >> Hello, I'm sure this is a common question but I couldn't find the answer.
> >> I'm
> >> setting up a web site with a SQL Server 2000 backend. The only purpose of
> >> the
> >> database server will be to work with IIS in delivering web content. Since
> >> obviously it is possible for many web requests to hit IIS simultaneously,
> >> would it be possible to exceed the CAL limit if IIS tried to connect too
> >> many
> >> times at once? Or is IIS considered to be a single client?
> >>
> >> Many thanks for your help,
> >> Brian
> >>
> >>
> >>
> >>
> >>
>|||"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:BE56601B.289A%ten.xoc@.dnartreb.noraa...
> I'm pretty sure you will need to use processor licensing, unless you
> enforce
> Windows authentication (which allows you to tie each web user to a
> specific
> CAL).
>
Yes. You don't need to use Windows authentication, but you do need a SQL
Server CAL for each user or each device which might hit the app, and it
can't be on the Internet. Basically, on an internal network (intranet) you
can deploy a 3-tier app with the same licenses you would need for a 2-tier
client/server app (licensing shouldn't drive architecture).
There is no concurrent user type license for SQL Server. The two licensing
modes are Per Processor, Server+CAL. A SQL Server CAL can be deployed to a
user or a device. If you deploy a CAL to a device (usually a desktop), then
any user can access SQL Server using that device (think the receptionist's
PC). If you deploy a CAL to a user, that user can access SQL Server through
any device (think Knoledge Worker with a PC, a SmartPhone and a VPN
connection from home). In either case it's not the number of concurrent
users who need CAL's but the total number of clients.
If the SQL Server only services the web app and is relatively small you
might be able to deploy on MSDE for free.
David