Cris
Sat Jul 16 09:35:49 CDT 2005
This is a multi-part message in MIME format.
------=_NextPart_000_0059_01C589E9.BFE8D6A0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Agreed here..
If you want to move anything...only the SQL does that with any grace
--=20
Cris Hanna [SBS-MVP]
-------------------------------------------------
Please do not email me directly for assistance. Reply only in the =
Newsgroups for the benefit of everyone
"SuperGumby [SBS MVP]" <not@your.nellie> wrote in message =
news:eVsfQCdiFHA.2904@tk2msftngp13.phx.gbl...
due to SBS2000 and later (SBS2003) integration I suggest it is highly=20
desirable for Exchange to remain on the SBS.
Only _you_ can say whether I am right when I suggest that a better =
move=20
would be to move the WHOLE LOT (SBS) to a new box. If so, look at=20
www.sbsmigration.com.
A new system with a pair of slow Xeons (2.0? GHz), hardware SCSI 320 =
RAID,=20
and dual channel DDR would EAT your box in a moment and not feel a =
necessity=20
to burp.
With dual PIII 1GHz you really may not require any increase in CPU. =
You=20
don't mention what sort of drive that 'plenty free HD space' is on, am =
I=20
right guessing it is either IDE or SATA? But that dual PIII is =
probably=20
using 100/133 SDRAM and moving to a more recent CPU (and mobo) will =
allow=20
you to increase RAM IO.
It _may_ even be possible to 'forklift' your current install to new=20
hardware, alleviate your performance problems, and not require the=20
assistance of the SQL DB app providers.
How do I move my server to new hardware
http://www.smallbizserver.net/Default.aspx?tabid=3D141 discusses =
SBS2003 (or=20
really, Windows 2003) but if you PRACTICE a bit you can do a very =
similar=20
thing with 2000.
"John McCann" <JohnMcCann@discussions.microsoft.com> wrote in message=20
news:5B4D5226-3F65-496D-BF68-20EA7E51B0B8@microsoft.com...
> Sorry, I didn't make it very clear. I understand that you can't =
split the
> product. I am going to purchase either Exchange or SQL seperately =
and stop
> the relevent services on the SBS. I was hoping someone could advise =
if it
> would be easy enough to move everyone to a different Exchange =
server, or=20
> if
> SQL was the easier one to move. Obviously, cost will play a part in =
this.
>
> The current server is an HP Netserver LC2000 with Dual 1GHZ PIII=20
> processors
> and 4 GIG ram. It's got plenty free HD space.
>
> Thanks,
>
> "Cris Hanna [SBS-MVP]" wrote:
>
>> You can't move either one...
>> Check the EULA for SBS all applications must be on the same server.
>>
>> Now you can add another server...bring up a RETAIL copy of SQL=20
>> Server...buy cals for the SQL Server and move the database.
>>
>> How much RAM in the server??? Have you considered adding more =
RAM??
>>
>> --=20
>> Cris Hanna [SBS-MVP]
>> -------------------------------------------------
>> Please do not email me directly for assistance. Reply only in the=20
>> Newsgroups for the benefit of everyone
>> "John McCann" <John McCann@discussions.microsoft.com> wrote in =
message=20
>> news:6AAB46BF-54D4-493A-BAB8-AB538B8FD2EB@microsoft.com...
>> One of my customers is using SBS 2000 with circa 40 clients. They =
are=20
>> using
>> Exchange and SQL production application pretty heavily, so =
performance=20
>> is a
>> bit iffy.
>> They need to move either the Exchnage or the SQL app to another =
box.=20
>> This
>> will be a basic Proliant with Server 2003 installed.
>>
>> Question is, what is the easier one to move? Exhange or SQL. I =
know=20
>> that
>> they'll have to purchase one or the other, so it's about the most =
cost
>> effective and the easier re-config.
>>
>> The client would prefer to move Exchange because they've had a =
lot of
>> bespoke work done on the SQL app and are terrified that they'll =
have to=20
>> go
>> back to the standard application and try and run all their mods =
again.
>>
>> Any comments would be appreciated.
>>
>> Thanks,
>>
>> John=20
------=_NextPart_000_0059_01C589E9.BFE8D6A0
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.2668" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Agreed here..</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>If you want to move anything...only the =
SQL does=20
that with any grace</FONT></DIV>
<DIV><BR>-- <BR>Cris Hanna=20
[SBS-MVP]<BR>-------------------------------------------------<BR>Please =
do not=20
email me directly for assistance. Reply only in the Newsgroups for =
the=20
benefit of everyone</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"SuperGumby [SBS MVP]" <<A=20
href=3D"mailto:not@your.nellie">not@your.nellie</A>> wrote in =
message <A=20
=
href=3D"news:eVsfQCdiFHA.2904@tk2msftngp13.phx.gbl">news:eVsfQCdiFHA.2904=
@tk2msftngp13.phx.gbl</A>...</DIV>due=20
to SBS2000 and later (SBS2003) integration I suggest it is highly=20
<BR>desirable for Exchange to remain on the SBS.<BR><BR>Only _you_ can =
say=20
whether I am right when I suggest that a better move <BR>would be to =
move the=20
WHOLE LOT (SBS) to a new box. If so, look at <BR><A=20
=
href=3D"
http://www.sbsmigration.com">www.sbsmigration.com</A>.<BR><BR>A =
new=20
system with a pair of slow Xeons (2.0? GHz), hardware SCSI 320 RAID, =
<BR>and=20
dual channel DDR would EAT your box in a moment and not feel a =
necessity=20
<BR>to burp.<BR><BR>With dual PIII 1GHz you really may not require any =
increase in CPU. You <BR>don't mention what sort of drive that 'plenty =
free HD=20
space' is on, am I <BR>right guessing it is either IDE or SATA? But =
that dual=20
PIII is probably <BR>using 100/133 SDRAM and moving to a more recent =
CPU (and=20
mobo) will allow <BR>you to increase RAM IO.<BR><BR>It _may_ even be =
possible=20
to 'forklift' your current install to new <BR>hardware, alleviate your =
performance problems, and not require the <BR>assistance of the SQL DB =
app=20
providers.<BR>How do I move my server to new hardware<BR><A=20
=
href=3D"
http://www.smallbizserver.net/Default.aspx?tabid=3D141">http://ww=
w.smallbizserver.net/Default.aspx?tabid=3D141</A>=20
discusses SBS2003 (or <BR>really, Windows 2003) but if you PRACTICE a =
bit you=20
can do a very similar <BR>thing with 2000.<BR><BR><BR>"John McCann" =
<<A=20
=
href=3D"mailto:JohnMcCann@discussions.microsoft.com">JohnMcCann@discussio=
ns.microsoft.com</A>>=20
wrote in message <BR><A=20
=
href=3D"news:5B4D5226-3F65-496D-BF68-20EA7E51B0B8@microsoft.com">news:5B4=
D5226-3F65-496D-BF68-20EA7E51B0B8@microsoft.com</A>...<BR>>=20
Sorry, I didn't make it very clear. I understand that you can't split=20
the<BR>> product. I am going to purchase either Exchange or SQL =
seperately=20
and stop<BR>> the relevent services on the SBS. I was hoping =
someone could=20
advise if it<BR>> would be easy enough to move everyone to a =
different=20
Exchange server, or <BR>> if<BR>> SQL was the easier one to =
move.=20
Obviously, cost will play a part in this.<BR>><BR>> The current =
server=20
is an HP Netserver LC2000 with Dual 1GHZ PIII <BR>> =
processors<BR>> and=20
4 GIG ram. It's got plenty free HD space.<BR>><BR>>=20
Thanks,<BR>><BR>> "Cris Hanna [SBS-MVP]" =
wrote:<BR>><BR>>> You=20
can't move either one...<BR>>> Check the EULA for SBS all =
applications=20
must be on the same server.<BR>>><BR>>> Now you can add =
another=20
server...bring up a RETAIL copy of SQL <BR>>> Server...buy cals =
for the=20
SQL Server and move the database.<BR>>><BR>>> How much RAM =
in the=20
server??? Have you considered adding more=20
RAM??<BR>>><BR>>> -- <BR>>> Cris Hanna =
[SBS-MVP]<BR>>>=20
-------------------------------------------------<BR>>> Please =
do not=20
email me directly for assistance. Reply only in the <BR>>> =
Newsgroups for the benefit of everyone<BR>>> "John =
McCann"=20
<John <A=20
=
href=3D"mailto:McCann@discussions.microsoft.com">McCann@discussions.micro=
soft.com</A>>=20
wrote in message <BR>>> <A=20
=
href=3D"news:6AAB46BF-54D4-493A-BAB8-AB538B8FD2EB@microsoft.com">news:6AA=
B46BF-54D4-493A-BAB8-AB538B8FD2EB@microsoft.com</A>...<BR>>> &=
nbsp;=20
One of my customers is using SBS 2000 with circa 40 clients. They are=20
<BR>>> using<BR>>> Exchange and SQL =
production=20
application pretty heavily, so performance <BR>>> is=20
a<BR>>> bit iffy.<BR>>> They need =
to move=20
either the Exchnage or the SQL app to another box. <BR>>>=20
This<BR>>> will be a basic Proliant with Server 2003 =
installed.<BR>>><BR>>> Question is, what is =
the easier=20
one to move? Exhange or SQL. I know <BR>>> =
that<BR>>> =20
they'll have to purchase one or the other, so it's about the most=20
cost<BR>>> effective and the easier=20
re-config.<BR>>><BR>>> The client would prefer =
to move=20
Exchange because they've had a lot of<BR>>> bespoke =
work=20
done on the SQL app and are terrified that they'll have to =
<BR>>>=20
go<BR>>> back to the standard application and try =
and run=20
all their mods again.<BR>>><BR>>> Any comments =
would=20
be appreciated.<BR>>><BR>>> =20
Thanks,<BR>>><BR>>> John=20
<BR><BR></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0059_01C589E9.BFE8D6A0--