Re: Windows 2003 Small Business Premium Edition SQL Server limits

From: Jay (jay_at_noemail.nospam)
Date: 02/17/05 

Date: Wed, 16 Feb 2005 19:39:01 -0800

Taking the line below from your reply:
"...with SBS's SQL it's only unlimited for anonymous access and that for
authenticated access SBS CALs are needed..."

Is the "authenticated access" Windows Active Directory authentication only?
What if someone creates a Forms Authentication to expose a web app where
username and passwords are stored in a file or in a table? What is someone
uses custom authentication and uses his/her own mechanism to autheticate
users for a web app? So you are authenticating and authorising those users to
acces the web app but they are not touching the Windows authentication - is
that allowed? Or does SBS 2003 does not make a distinction between the
various authentication modes, i.e. as long as any authentication mode is used
it's termed under "authentication"?

Thank you for your input,

-- Jay Scale

"David Copeland [MSFT]" wrote:

> Henry,
>
> Just wanting to make sure that it's clear that with SQL Per Processor
> licenses no user/device cals are needed (as you mentioned below).. whereas
> with SBS's SQL it's only unlimited for anonymous access and that for
> authenticated access SBS CALs are needed and are not based on concurrent
> usage.
>
> Just in case they might have skipped/missed the other line.. and remembered
> only the "Per Processor" part.
>
> --
>
> Hope that helps,
> David Copeland
> Microsoft Small Business Server Support
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> Newsgroups:
> SBS v4.x : microsoft.public.backoffice.smallbiz
> SBS 2000: microsoft.public.backoffice.smallbiz2000
> SBS 2003: microsoft.public.windows.server.sbs
>
>
> "Henry Craven [SBS-MVP]" <IUnknown@Dot.Nyet> wrote in message
> news:OXd1xJJFFHA.2608@TK2MSFTNGP10.phx.gbl...
> > Sorry David,
> > .... I thought I'd addressed the Authenticated issue with:
> > " - If you're accessing the SQL Server via SBServer authentication
> > your restricted to a maximum of connections as can be covered by your SBS
> > User/Device CALs " ...and that's SBS's limit in SBS Authentication, not a
> > CAL limit within SQL Server.
> >
> > So
> > Given the SQL Server EULA states:
> > "A Processor license includes access for an unlimited number of devices or
> > users to connect from either inside the corporate LAN or WAN or outside
> > the firewall"
> >
> > and if in SBS's SQL Server using Anonymous Access from the web there is no
> > limit or individual CALs required to access the SQL Server, and the
> > Authentication to the SBServer is the limiting factor not the number of
> > connections to the SQL server, then isn't that effectively SQL Server Per
> > Processor licensing ?
> >
> > I don't see your distinction there ....
> >
> > Anyway, whatever one does or doesn't call it, I'm happy as long as I've
> > not mis-stated the limits to the OP.
> >
> > --
> > Henry Craven {SBS-MVP}
> > CI Information Technology
> > ----------------------------------------------------
> > Melbourne SBS Users Group
> > http://groups.yahoo.com/group/melb-SBSusers/
> >
> > "David Copeland [MSFT]" <davidcop@online.microsoft.com> wrote in message
> > news:uh7iVFHFFHA.3336@TK2MSFTNGP10.phx.gbl...
> >> Henry,
> >>
> >> I would exactly say its "effectively "Per Processor"" since the back
> >> ending only applies if the usage is via anonymous access. For
> >> authenticated access, you still require SBS CALs.
> >>
> >> http://www.microsoft.com/WindowsServer2003/sbs/techinfo/overview/licensingfaq.mspx
> >>
> >> Q. Can I use the SQL Server component for Web-based business
> >> applications?
> >>
> >> A. Yes, new with Windows Small Business Server 2003 is the ability
> >> for you to use the SQL Server component for an unlimited number of
> >> un-authenticated users. As long as you are un-authenticated, you also do
> >> not need a Windows Small Business Server 2003 CAL.
> >>
> >>
> >>
> >>
> >> Also, might want to look at the SBS EULA regarding it not being able to
> >> be used for commercial hosting..
> >>
> >>
> >> --
> >>
> >> Hope that helps,
> >> David Copeland
> >> Microsoft Small Business Server Support
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >> Newsgroups:
> >> SBS v4.x : microsoft.public.backoffice.smallbiz
> >> SBS 2000: microsoft.public.backoffice.smallbiz2000
> >> SBS 2003: microsoft.public.windows.server.sbs
> >>
> >>
> >> "Henry Craven [SBS-MVP]" <IUnknown@Dot.Nyet> wrote in message
> >> news:%2350JA0FFFHA.2032@tk2msftngp13.phx.gbl...
> >>> The SQL Server is SQL Server std. so pretty much the same limitations
> >>> apply but with a couple of bonuses.
> >>>
> >>> - As SQL server std you get a Terrabyte of Data Storage.
> >>>
> >>> - Because in SBS 2003 MS removed the restriction on Back-ending
> >>> public Websites with the SQL Server it's effectively "Per Processor"
> >>>
> >>> - Because SBS 2003 Supports 2 Physical ( 4 Hyperthreaded ) CPUs
> >>> it's effectively a 2 CPU License
> >>>
> >>> - MS have allowed Unlimited SQL Server Instances on SBS 2003.
> >>>
> >>> - Because it's SBS you -cannot- install the SQL Server(s) on other
> >>> than the SBServer Server.
> >>>
> >>> - It's Still SQL Server Std so will only use 2 GB RAM. ( Even
> >>> though SBS itself allows 4Gb )
> >>>
> >>> - If you're accessing the SQL Server via SBServer authentication
> >>> your restricted to a maximum of connections as can be covered by your
> >>> SBS User/Device CALs
> >>>
> >>> That's about it.
> >>>
> >>> --
> >>> Henry Craven {SBS-MVP}
> >>> CI Information Technology
> >>> ----------------------------------------------------
> >>> Melbourne SBS Users Group
> >>> http://groups.yahoo.com/group/melb-SBSusers/
> >>>
> >>> "SARPER SARIDAL" <sarper@saridal.com> wrote in message
> >>> news:erWL3lFFFHA.4004@tk2msftngp13.phx.gbl...
> >>>> What are the limits of SQL server in Windows 2003 Small Business Server
> >>>> Premium Edition.?
> >>>>
> >>>> Maximum number of connections? Licensing? Maximum database size? and so
> >>>> on...
> >>>>
> >>>> Urgent please reply.
> >>>>
> >>>> Thank you.
> >>>
> >>>
> >>
> >>
> >
> >
>
>
>

Relevant Pages