> Anyone else who's recently read the full SQL 7 license care to
> confirm/deny this? I may well be on crack...
Yes, the link to the license was in the message you just replied to. Read
it and weep. It very specifically and explicitly singles out the scenario
you mention, and states that you must have an ICL to use with middleware on
a publically available website.
-Cameron
--------------------
Cameron Childress
elliptIQ Inc.
p.770.460.7277.232
f.770.460.0963
> -----Original Message-----
> From: Zachary Bedell [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 30, 2001 10:53 AM
> To: CF-Talk
> Subject: RE: SQL Server Licensing Woes
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> The last time I read the full SQL 7 license agreement, I found a
> little loophole. They fixed it in the SQL 2000 agreement, but if
> you're only using 7, maybe this could help you.
>
> <CF_Disclaimer>I am *not* a lawyer. I am a coder. That said, my
> grasp of the English language is automatically suspect. Before
> betting the farm on this, you probably ought to have a lawyer check
> it out...</CF_Disclaimer>
>
> The way the 7.0 license was stated, it *looks* like you need either
> the ICL, OR one CAL per concurrent access TO THE SQL SERVER.
>
> Since CF is automatically limited to no more concurrent access than
> it has threads (set in the CF Administrator), you should only need
> that many CALs. Alternately, I *think* you can limit the number of
> concurrent DB accesses per data source in the Administrator as well.
>
> I know that in the SQL 2000 license, they specifically said you can't
> do that anymore, but the SQL 7 license seems to allow it.
>
> It would probably be wise to grab and ICL if you can get one, but you
> *may* not need one.
>
> Anyone else who's recently read the full SQL 7 license care to
> confirm/deny this? I may well be on crack...
>
> Best regards,
> Zac Bedell
>
> > -----Original Message-----
> > From: Dave Watts [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, January 29, 2001 8:19 PM
> > To: CF-Talk
> > Subject: RE: SQL Server Licensing Woes
> >
> >
> > > Actually if you are using a WebServer to connect to the SQL
> > > Server you do not need an Internet Connector License. Internet
> > > Connector Licenses are for users from the internet connecting
> > > directly to the SQL Server as in many Win32 apps that were
> > > developed. Attached is the link to this information. I was
> > > advised of this by the Microsoft Licensing Center. You would
> > > need a CAL for every WebServer that will connect to the SQL
> > > Server and any other device from the internet that would be
> > > accessing the resources of the SQL Server.
> > >
> > > http://www.microsoft.com/SQL/productinfo/70pricing.htm
> >
> > Uh, there are a couple of problems here.
> >
> > First, according to the SQL 7 pricing info in your link, if
> > you allow access
> > to SQL Server through a web server, you would need to either get
> > the Internet Connector License, or purchase a CAL for each
> > concurrent user,
> > depending on whether the users of the application are "internal" or
> > "public":
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>
> Comment: Please use PGP!
>
> iQA/AwUBOnbjbKvhLS1aWPxeEQIzAwCgvkfOXFTQC5EP5j+z6kORHTwSGZ8AoJiA
> MHjDVjUcrZMcOQMpENPvvbSC
> =dzga
> -----END PGP SIGNATURE-----
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
