The big box theory

Hospital ports apps to 32-processor Unisys server.

Truman Medical Centers • Kansas City, Mo. • The word "explosion" is never good when you're in an IT environment. But that's how Rob Jones describes the growth of two-processor Intel servers at his company, Truman Medical Centers, as he continually added new applications  over the past few years.

"We were seeing the number of servers per technician rising, and we needed to get above that curve," says Jones, director of IT at Truman in Kansas City, Mo.

To continue reading, register here and become an Insider. You'll get free access to premium content from CIO, Computerworld, CSO, InfoWorld, and Network World. See more Insider content or sign in.

Truman Medical Centers • Kansas City, Mo. • The word "explosion" is never good when you're in an IT environment. But that's how Rob Jones describes the growth of two-processor Intel servers at his company, Truman Medical Centers, as he continually added new applications  over the past few years.

"We were seeing the number of servers per technician rising, and we needed to get above that curve," says Jones, director of IT at Truman in Kansas City, Mo.

Jones knew he was outgrowing his one-or-two-application-per-server environment, where each new server meant one more box to maintain, patch, back up, network and pay maintenance on. So even though the cost of a 32-processor ES7000 server from Unisys  was not exactly inexpensive, Jones knew it would consume fewer internal resources and also provide flexibility he couldn't get on his stand-alone Windows systems.

"Supporting a two-processor box is just as hard as supporting a four- or eight- or 32-processor box, so it frees up time, plus availability is higher on the [ES7000]," he says. Jones also wanted the ability to rearrange the server's RAM, hard drives and network segments, and reallocate processors according to his application needs.

Jones achieved those goals by implementing the Unisys box running Windows Server 2003 DataCenter Edition. The first application to move onto a partition on the Unisys box was Exchange 2003, which knocked out five Windows servers. Next to move was a cluster of nine file-sharing servers containing personal directories. Jones also centralized storage on an EMC  SAN connected to a StorageTek automated library, which got rid of nine direct-attached storage servers.

The next step, Jones says, is to move Truman's custom version of SQL Server and the Microsoft Sharepoint document library.

Jones says he is very happy with the ES7000's ability to dedicate processors to applications, and he likes doing this at the machine level rather than setting up virtual machines. He can set up one hardware partition on the entire machine or break it down into several. Right now, there are two eight-way and two four-way partitions. "They all share one set of RAM, and I can move processors from one partition to another for flexibility," he says.

Working with virtual servers, he says, would have been too complex. "I have people trained on Windows, and if I had said, 'You have to learn VMWare,' that's one more layer they would have had to learn," he says.

Things will get a little more complicated when Jones begins porting Truman's multiple flavors of SQL Server to the ES7000. "You have to be really careful about which applications you can consolidate," he says. "SQL is the toughest one because you have to look at which databases can really be together in one particular box." Already, Jones knows he'll need to maintain several separate servers for particular instances of SQL Server that need to be stand-alone.