This is a multi-part message in MIME format.

------=_NextPart_000_0225_01C3D9F6.9C6E4380
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

My client is setting up some ASP pages on his site to pull client =
specific info from the SQL Server on his SBS2000 setup. For now, there =
would only be a handful of clients accessing the data (through the IUSR =
account most likely).

What licensing issues do I need to address to maintain compliance? We =
have 25 SBS cals and maybe 15 actual users at this time.

Thanks!

--=20
Kevin Hill
President=20
3NF Consulting

www.3nf-inc.com

------=_NextPart_000_0225_01C3D9F6.9C6E4380
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1276" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>My client is setting up some ASP pages =
on his site=20
to pull client specific info from the SQL Server on his SBS2000 =
setup.&nbsp; For=20
now, there would only be a handful of clients accessing the data =
(through the=20
IUSR account most likely).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>What licensing issues do I need to =
address to=20
maintain compliance?&nbsp; We have 25 SBS cals and maybe 15 actual users =
at this=20
time.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks!</FONT></DIV><FONT face=3DArial =
size=3D2>
<DIV><BR>-- <BR>Kevin Hill<BR>President <BR>3NF Consulting</DIV>
<DIV>&nbsp;</DIV>
<DIV>www.3nf-inc.com<BR></FONT></DIV></BODY></HTML>

------=_NextPart_000_0225_01C3D9F6.9C6E4380--

Re: licensing question by Javier

Javier
Tue Jan 13 17:48:16 CST 2004

Hi Kevin!

Since SQL in SBS2k cannot be used to backend a public website the users (the
"handful of clients") will need to be authenticated somehow. Which in legal
terms means that you need one CAL for each one (even if the use one
account).

Another option would be to upgrade to SBS2k3 which allows SQL to backend a
public website.

--
-Javier

<< SBS ROCK!!! >>

"Kevin3NF" <KHill@NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
news:%23vAWoji2DHA.3196@TK2MSFTNGP11.phx.gbl...
My client is setting up some ASP pages on his site to pull client specific
info from the SQL Server on his SBS2000 setup. For now, there would only be
a handful of clients accessing the data (through the IUSR account most
likely).

What licensing issues do I need to address to maintain compliance? We have
25 SBS cals and maybe 15 actual users at this time.

Thanks!

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com



Re: licensing question by Henry

Henry
Tue Jan 13 17:48:05 CST 2004

The SBS 2000 EULA prohibits the use of the SQL Server component to
Backend data for Public websites.

Given that it is a really -bad- idea to host a website and backend
Database within SBS ( Either Host Off-site, or in a DMZ )
if the user insists on doing it, then they need to :

- move to another Database to Backend the Web.
( Full SQL Server on a per Processor License, MSDE, Jet, PostgreSQL,
MySQL Flat File etc... )

- Obtain CALs for each Client and create an SBS Account for each.
( Clients will effectively be Offsite Users and so eligible to access
data on the SQL Server.)

- Upgrade to SBS 2003 Premium where the restriction has been lifted.

But I cannot say strongly enough that it is NOT NOT NOT advisable to
give -anyone- access to live data on the Internal SBS Database even IF
the Web App is extremely well written, and a Web Application Firewall is
in place. Replicate to an Offsite, or DMZ'd Database on a server separate
to the Web Server and include stringent security controls.

( As you're 3NF, how'd you like to authenticate me to your Live Database
if I enter my UserName as ";Drop Table Customers;" ? ...and that is just
a trivial example of the security risks involved as I'm sure your well
aware.)

--
Henry Craven.

========= Post It Appropriately: ============
SBS 4/4.5 : microsoft.public.backoffice.smallbiz
SBS 2000 : microsoft.public.backoffice.smallbiz2000
SBS 2003 : microsoft.public.windows.server.sbs
=====================================
"Kevin3NF" <KHill@NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
news:%23vAWoji2DHA.3196@TK2MSFTNGP11.phx.gbl...
My client is setting up some ASP pages on his site to pull client
specific info from the SQL Server on his SBS2000 setup. For now, there
would only be a handful of clients accessing the data (through the IUSR
account most likely).

What licensing issues do I need to address to maintain compliance? We
have 25 SBS cals and maybe 15 actual users at this time.

Thanks!

--
Kevin Hill
President
3NF Consulting

www.3nf-inc.com