In a workstation-only environment, each PC does all its own processing. Depending on the applications and workload, this can cause slow turnaround of information and results.

In a true server-workstation environment, some processing tasks can be given to the server, which is in most cases faster and more capable than the workstation. In addition, when a database resides on the server, the workstation can pose a question, also known as a query, to the server, and let the server do the hard work. Often the server has the database on its hard drive, and so it has the fastest possible access to the data. By returning only the correct answer(s), there is much less network traffic than if the workstatation has to access, sort, and filter through the entire database using a network connection.

If this sounds confusing, think of a simple example: Using a phone book to find a number vs. calling directory assistance. On one hand, you have to stop what you’re doing, find the right phone book, flip through the pages, and scan the right page for the result. When calling directory assistance, you merely state your request and their powerful server returns the answer to you instantly. The server does all the work and just gives you what you want.

A properly designed network can increase speed and productivity by correctly balancing workloads between the server(s) and the workstations(s).

It might also be worth noting the strictly “server” operating systems out there such as IBM’s AIX, HP’s HP-UX and Tru64, as well as Sun Microsystems’ Solaris. When a TRULY robust and mission critical server environment is required, the task is handed to one of these flavors of UNIX.

Lets suffice to say that THE MOST CRITICAL computer systems in the world are running one of these commercial operating systems.