Discussion Locked

Hardware/Software upgrading freq.

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have to come up with graphs that show the need and frequency for upgrading hardware and software for our customer. At our site we only have 33 computers in the LAN with a dual pentium 200 Mhz server running NT 4. We run several overhead intensive database programs. I'm only 3 months into this job and I don't have access to past records so I would appreciate information from anyone with experience in how often upgrades should be done for a small site.

5 replies

by bv2

Hmmm...If you have several overhead intensive db programs, you need to upgrade that server, period. I don't have a graph, or literature, but if you are using overhead intensive programs and are using technology that is four generations behind as your backbone, that's bad business. In general, try and get a screamin' demon for your own use, then run the same apps everyone else is running. Note the difference in time to operate and load programs, then graph that, or table it, or whatever. Thesignificant difference should be enough to convince the powers that be to upgrade the machines. Rule of thumb is upgrade when there is a significant upgrade that has been proven. Let the gamers work out the bugs...As an example, my company is now replacing PIIs with PIIIs - the price has gone down and the technology is proven. We're not doing 800s or 900s, but around 650-700 PIIIs because of their relative "age" and success in the marketplace.

by donq

If your apps are overhead intensive applications (where the data modeling isn't the problem) then you should definately upgrade the server to (4 ea 600-700Mhz) as suggested by a previous answer. If you problem is data modeling that should be PRIORITY ONE before wasting money on ever changing hardware.

by geno

The data modeling is a portion of the problem but because the database had to be designed around an existing database used by other sites and integrated into a much larger database that covered functions peculiar to our site it couldn't be helped.

This discussion is closed to new replies.