Re: Tech Specs regarding SBS 2003 R2

What the others said with two other thoughts.

1. You could purchase SBS standard and a stand alone install SQL on an
application server, which you would have to do anyway.

2. You did not say what your environment is. If you have 25 computers and
three shifts, you could license the entire thing with device cals and be ok.
The limit here would be 75 devices, or even a mix of users and devices.

--
Larry


"Les Connor [SBS MVP]" <les.connor@xxxxxxxxxxxx> wrote in message
news:A7592382-7549-4D33-AAB6-4850F97875C1@xxxxxxxxxxxxxxxx
Hi,

The base OS is Windows Server 2003 Standard Edition, therfore 4 Gb of
memory is max.

70 users would be pushing it, depending on the load any SQL based
application might place on the server. Without any SQL app, you could
handle 70 users (predominantly Exchange and file/print), but the maximum
CAL count for SBS is 75 so if there was any growth at all you'd be up
against it.

The suite components (Exchange and SQL) that come with SBS cannot be
installed on another server. However, if you purchase SBS 2k3 R2, you can
purchase Exchange and/or SQL, install them on a member server, and not
have to purchase any additional Windows Server, Exchange, or SQL CALs.
That can be a pretty big financial incentive.

However, the primary concern remains the 70 users, and on that basis
you're probably either in Centro (Essential Business Server - not released
yet) camp, or Windows Server 2003/2008.

--
Les Connor [SBS MVP]


<dalemite@xxxxxxxxxxx> wrote in message
news:9664baf8-a4a7-4b14-98e1-db1a5b6b4bc0@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I'm in need of a ~70 user environment, so SBS 2003 R2 sounds like it
would do well. I am, however, wondering a few things before I buy,
and cannot find any information from FAQs or sales reps.

1) How much total memory can SBS2003 R2 handle?

2) Would I be able to install SQL on seperate hardware?

3) Is load balancing available?

To be honest if 2 & 3 can be met, 1 isn't an issue. If someone caould
enlighten me, I would appreciate it :)

Dale!



.

Relevant Pages

  • Re: Redundancy design in SBS Domain
    ... But virtualization was not on my radar, and Exchange and SQL need more with each iteration. ... I originally went the SBS route because it was by far the cheapest was to get a server up and running with SQL Server at the time. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Std - SQL Eval expired...will un-installing break SBS fun
    ... I agree with Claus that you're able to remove SQL 2005 instances if you did ... you can get SBS R2 which already contains SQL Server 2005 ... Workgroup Edition, and upgrade Sharepoint instance, and install other ...
    (microsoft.public.windows.server.sbs)
  • Re: sharepoint error
    ... If you are using SBS 2003 Premium Edition the easiest way is to follow ... to upgrade the SharePoint named instance. ... and search on "Migrating from WMSDE to SQL Server" ... Microsoft Small Business Server Support ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS
    ... Les Connor [SBS MVP] ... Is your server exhibiting significant performance problems, and if so, how ... SQL Server: ... >No wonder SBS brings servers with 4GB of RAM to their knees. ...
    (microsoft.public.windows.server.sbs)
  • Installing SQL7 Server on a Win2000 Server machine
    ... I am trying to install SQL 7 on a fresh new W2K ... parameters using SQL Server 7 under WinNT: ... B - RESTORE ERROR ...
    (microsoft.public.sqlserver.setup)