|
it
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
When is it worth buying an actual server?white box machine. I have never used an actual "server". I am running Exchange2k, web sites and SQL2k on these machines with no noticeable bad effects. Emphasis on noticable.... I have been trying to figure out a very occaisional SQL timeout and the only thing MS PSS can guess is that the machine gets tied up sometimes and ignores another machines request for interaction. So they said to go dual proc. So I am considering purchasing my first actual server machine, but I have to ask you all if its worth it. I am looking at a DL380 Dual proc from the refurb dept and even though they are refurb, they are still pretty proud of these so before I dive in, can I have some feedback on whether I should just get a dual proc workstation or go all the way to the 380. This unit will be the only server and will handle Win2k3 A/D and SQL2k. It might handle an internal web site at some point but that usage would be tied to the SQL anyway. There are about 12 workstations, 9 of which are cash registers and the SQL traffic is minimal. Even on the current "server" the unit is idle most of the time. Comments please? The basic diffrence is hardware and capabilities. But you know that.
I work primarily with servers, and have grown a disdain for using desktop PCs for centralized roles. Much of that is bias. So after thinking about the question I can stae several generic plusses to servers: 1. rackmount, easy storage and access. Add a nice 1u flatpanel KVM and you can drastically reduce the evil wires. 2. Many servers (most dl380s for example ) have built in raid controllers and hot swap bays. A fault tolerant disk loses all street cred if you have to reboot the serve to repair it. 3 Multiple powers supplies 4 Typically use registered and ecc ram. More stable and recover single bit memory errors. 5 replacement parts are available for years and years. This is one of the big reasons that most admins think it is irresponsible to use white box systems. If your dl380 mobo goes south (unlikley since the quality control is great) you can replace it with an exact duplicate repair part and not worry about having to reinstall the whole OS because the back up blue screens when you restore it. 6 I have never seen a high end PC motherboard that can handle 8 GB of ram. That being said, the use you dictate doesn't scream that you need a server, except that I heard cash registers in the statement. Taking money is a fundamental business need. Some would say the only thing a business must be able to do is take money. Don't play with a whitebox system, would be my advice. Keep in mind: http://h20000.www2.hp.com/bizsupport/CoreRedirect.jsp?targetPage=http%3A%2F%2Fh200002.www2.hp.com%2Fbc%2Fdocs%2Fsupport%2FSupportManual%2Fc00257520%2Fc00257520.pdf Show quoteHide quote ".:mmac:." wrote: > Every server I have worked with has been a generic high end motherboard > white box machine. I have never used an actual "server". I am running > Exchange2k, web sites and SQL2k on these machines with no noticeable bad > effects. Emphasis on noticable.... > I have been trying to figure out a very occaisional SQL timeout and the > only thing MS PSS can guess is that the machine gets tied up sometimes and > ignores another machines request for interaction. So they said to go dual > proc. > So I am considering purchasing my first actual server machine, but I > have to ask you all if its worth it. I am looking at a DL380 Dual proc from > the refurb dept and even though they are refurb, they are still pretty proud > of these so before I dive in, can I have some feedback on whether I should > just get a dual proc workstation or go all the way to the 380. > This unit will be the only server and will handle Win2k3 A/D and SQL2k. > It might handle an internal web site at some point but that usage would be > tied to the SQL anyway. > There are about 12 workstations, 9 of which are cash registers and the > SQL traffic is minimal. Even on the current "server" the unit is idle most > of the time. > Comments please? > > > I guess it's a choice I wouldn't regret. Buy once I do this I may never want
to go back! That could get expensive! Thanks for the feedback both of you. Show quoteHide quote "Manny Borges" <MannyBor***@discussions.microsoft.com> wrote in message news:DD1ACF49-DD3F-43AE-9189-0A9644B2F0F2@microsoft.com... > The basic diffrence is hardware and capabilities. But you know that. > I work primarily with servers, and have grown a disdain for using desktop > PCs for centralized roles. Much of that is bias. So after thinking about > the > question I can stae several generic plusses to servers: > 1. rackmount, easy storage and access. Add a nice 1u flatpanel KVM and you > can drastically reduce the evil wires. > 2. Many servers (most dl380s for example ) have built in raid controllers > and hot swap bays. A fault tolerant disk loses all street cred if you have > to > reboot the serve to repair it. > 3 Multiple powers supplies > 4 Typically use registered and ecc ram. More stable and recover single bit > memory errors. > 5 replacement parts are available for years and years. This is one of the > big reasons that most admins think it is irresponsible to use white box > systems. If your dl380 mobo goes south (unlikley since the quality control > is > great) you can replace it with an exact duplicate repair part and not > worry > about having to reinstall the whole OS because the back up blue screens > when > you restore it. > 6 I have never seen a high end PC motherboard that can handle 8 GB of ram. > > > That being said, the use you dictate doesn't scream that you need a > server, > except that I heard cash registers in the statement. Taking money is a > fundamental business need. Some would say the only thing a business must > be > able to do is take money. Don't play with a whitebox system, would be my > advice. > > > > Keep in mind: > http://h20000.www2.hp.com/bizsupport/CoreRedirect.jsp?targetPage=http%3A%2F%2Fh200002.www2.hp.com%2Fbc%2Fdocs%2Fsupport%2FSupportManual%2Fc00257520%2Fc00257520.pdf > > > ".:mmac:." wrote: > >> Every server I have worked with has been a generic high end >> motherboard >> white box machine. I have never used an actual "server". I am running >> Exchange2k, web sites and SQL2k on these machines with no noticeable bad >> effects. Emphasis on noticable.... >> I have been trying to figure out a very occaisional SQL timeout and >> the >> only thing MS PSS can guess is that the machine gets tied up sometimes >> and >> ignores another machines request for interaction. So they said to go dual >> proc. >> So I am considering purchasing my first actual server machine, but I >> have to ask you all if its worth it. I am looking at a DL380 Dual proc >> from >> the refurb dept and even though they are refurb, they are still pretty >> proud >> of these so before I dive in, can I have some feedback on whether I >> should >> just get a dual proc workstation or go all the way to the 380. >> This unit will be the only server and will handle Win2k3 A/D and >> SQL2k. >> It might handle an internal web site at some point but that usage would >> be >> tied to the SQL anyway. >> There are about 12 workstations, 9 of which are cash registers and >> the >> SQL traffic is minimal. Even on the current "server" the unit is idle >> most >> of the time. >> Comments please? >> >> >> I was in the same situation as you... running fine on the old grey box that
I turned into a 'server' and really, everything was working fine... what made me make the switch to a 'real' server was.. dual processor, room for more memory, faster hard drives available, more control over heating and cooling and the price was right. I am sure there are more technical reasons, but that's why I changed over. Show quoteHide quote ".:mmac:." <lost@sea> wrote in message news:ubYq2%23KbFHA.3144@TK2MSFTNGP14.phx.gbl... > Every server I have worked with has been a generic high end motherboard > white box machine. I have never used an actual "server". I am running > Exchange2k, web sites and SQL2k on these machines with no noticeable bad > effects. Emphasis on noticable.... > I have been trying to figure out a very occaisional SQL timeout and the > only thing MS PSS can guess is that the machine gets tied up sometimes and > ignores another machines request for interaction. So they said to go dual > proc. > So I am considering purchasing my first actual server machine, but I > have to ask you all if its worth it. I am looking at a DL380 Dual proc > from the refurb dept and even though they are refurb, they are still > pretty proud of these so before I dive in, can I have some feedback on > whether I should just get a dual proc workstation or go all the way to the > 380. > This unit will be the only server and will handle Win2k3 A/D and SQL2k. > It might handle an internal web site at some point but that usage would be > tied to the SQL anyway. > There are about 12 workstations, 9 of which are cash registers and the > SQL traffic is minimal. Even on the current "server" the unit is idle most > of the time. > Comments please? >
w2k3 blue screen at startup
NT4 & Windows 2000 / 2003 list of IP addresses for all network printers ... RPC error on member server, after installing WS2003 SP1 password changing? Upgrading NT4 to Windows 2003 Can't connect remotely? Cant open encrypted files Terminal Server Question! Event ID Event id 13568 JRNL_WRAP_ERROR. |
|||||||||||||||||||||||