Bill
Wed Mar 02 06:55:27 CST 2005
This is a multi-part message in MIME format.
------=_NextPart_000_003E_01C51EFD.32769AC0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Thanks!
--=20
=20
"Cris Hanna [SBS-MVP]" =
<crisnospamhanna@computingnospampossibilities.net> wrote in message =
news:Oy3LHqtHFHA.2456@TK2MSFTNGP09.phx.gbl...
You have SQL Standard Edition and you have enough CALS no need to =
purchase from them
--=20
Cris Hanna [SBS-MVP]
Small Business Server Specialist
The Trinity Companies - Microsoft Gold Partner
St. Louis, MO
www.trinitycos.com
------------------------------------------------------------------
Please only respond in the newsgoup and not to me directly so that all =
can benefit from the information
SBS 2003 - microsoft.public.windows.server.sbs
SBS 2000 - microsoft.public.backoffice.smallbiz2000
SBS 4.5 - microsoft.public.backoffice.smallbiz
"Bill Sanderson" <Bill_Sanderson@msn.com.plugh.org> wrote in message =
news:%23bLcbltHFHA.2276@TK2MSFTNGP15.phx.gbl...
(hows that for being honest up front!)
I've got an SBS-2000 installation which is not presently using the =
Sql=20
server portion.
We've had a proposal from a vendor to move an app from a dedicated =
Unix=20
server to Windows, and the Windows piece runs on SQL Server. So, =
their=20
proposal includes SQL Server @ $666, and 6 Sql Server User cals =
@$146 each.
Since I've already got Sql Server, how much of this can I save? Do =
I need=20
the cals? We've got either 15 or 20 SBS cals, as I recall--the=20
sub-operation that will use this software is probably 6 users max, =
which is=20
why the spec.
Pointers about where to read to understand limitations of Sql =
licensing=20
welcome. As I recall from previous research, I'm not allowed to use =
the SBS=20
SQL Server as a backing to a Web site. This issue will come up, but =
we are=20
presently solving that via MySql, and may well continue to do that.
--=20
=20
------=_NextPart_000_003E_01C51EFD.32769AC0
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.2900.2604" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Thanks!</FONT></DIV>
<DIV><BR>-- <BR> </DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Cris Hanna [SBS-MVP]" <<A=20
=
href=3D"mailto:crisnospamhanna@computingnospampossibilities.net">crisnosp=
amhanna@computingnospampossibilities.net</A>>=20
wrote in message <A=20
=
href=3D"news:Oy3LHqtHFHA.2456@TK2MSFTNGP09.phx.gbl">news:Oy3LHqtHFHA.2456=
@TK2MSFTNGP09.phx.gbl</A>...</DIV>
<DIV><FONT face=3DArial size=3D2>You have SQL Standard Edition and you =
have enough=20
CALS no need to purchase from them</FONT></DIV>
<DIV><BR>-- <BR>Cris Hanna [SBS-MVP]<BR>Small Business Server=20
Specialist<BR>The Trinity Companies - Microsoft Gold Partner<BR>St. =
Louis,=20
MO<BR><A=20
=
href=3D"
http://www.trinitycos.com">www.trinitycos.com</A><BR>------------=
------------------------------------------------------<BR>Please=20
only respond in the newsgoup and not to me directly so that all can =
benefit=20
from the information<BR>SBS 2003 - =20
microsoft.public.windows.server.sbs<BR>SBS 2000 - =20
microsoft.public.backoffice.smallbiz2000<BR>SBS =
4.5 =20
- microsoft.public.backoffice.smallbiz</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Bill Sanderson" <<A=20
=
href=3D"mailto:Bill_Sanderson@msn.com.plugh.org">Bill_Sanderson@msn.com.p=
lugh.org</A>>=20
wrote in message <A=20
=
href=3D"news:%23bLcbltHFHA.2276@TK2MSFTNGP15.phx.gbl">news:%23bLcbltHFHA.=
2276@TK2MSFTNGP15.phx.gbl</A>...</DIV>(hows=20
that for being honest up front!)<BR><BR>I've got an SBS-2000 =
installation=20
which is not presently using the Sql <BR>server =
portion.<BR><BR>We've had a=20
proposal from a vendor to move an app from a dedicated Unix =
<BR>server to=20
Windows, and the Windows piece runs on SQL Server. So, their=20
<BR>proposal includes SQL Server @ $666, and 6 Sql Server User cals =
@$146=20
each.<BR><BR>Since I've already got Sql Server, how much of this can =
I=20
save? Do I need <BR>the cals? We've got either 15 or 20 =
SBS=20
cals, as I recall--the <BR>sub-operation that will use this software =
is=20
probably 6 users max, which is <BR>why the spec.<BR><BR>Pointers =
about where=20
to read to understand limitations of Sql licensing =
<BR>welcome. As I=20
recall from previous research, I'm not allowed to use the SBS =
<BR>SQL Server=20
as a backing to a Web site. This issue will come up, but we =
are=20
<BR>presently solving that via MySql, and may well continue to do=20
that.<BR>-- =
<BR> <BR><BR></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_003E_01C51EFD.32769AC0--