Re: Microsoft hating aside, and from a purely technical viewpoint, why would this be risky? Can you name the risks and assign a level of risk to them?
Steve,
Downtime, nuf said. Depending on the use of the server, downtime could be up to $1,000,000 per hour.
From a technical viewpoint, Windows is unstable. There are many, many, many problems. It's not as simple as one problem, if it was, Microsoft would've fixed it years ago. But I continue to get "blue screens of death" at least a few times a week. My computer isn't even used as a server either!!!
I recently worked on a project where we replaced NT servers with AS/400's. There site was so unstable due to memory leakage that as a last resort, they decided to restart their servers at 3am Pacific time to prevent crashes during the daytime. Too bad they were a Japanese company, because its the middle of the day there at 3am pacific. If you're global, there's no good time for downtime.
Actually, NT servers are so unstable that IBM ships its Netfinity line with the option of a piece of software that will automatically restart your servers. You set up the time and frequency, it does the rest. This prevents you from having to have your IT guy go in at 3am to restart the servers.
chic |
