Upgrading to Client/Server

By Rich Eichacker
Vibrance Technology Corporation

"Desktop" databases, such as Microsoft Access or FileMaker Pro, provide an inexpensive way for small and mid-sized businesses to manage data. These programs make it easy for novice users to create data tables, data entry forms and reports. As a software developer, I've used Access quite a bit when building applications for clients. Administration is easy for both parties, clients can add their own queries and reports, and the database can easily be copied or emailed to other systems.

There are some drawbacks to desktop databases however, and in some situations an upgrade to a client/server platform may provide increased reliability and functionality. The main drawback is the fact that the database file is actually open in memory on each user's computer. And if, during an update, one of the user's PC crashes, the entire database can become corrupted. Usually the corrupted file can be repaired, but there are times when it cannot and must be restored from backups. Another drawback: in networked environments, multiple users accessing the database can slow down processing and increase the likelihood of a corruption.

Client/server databases provide a layer of isolation so that users never actually open the database files. In effect, when data is updated, the client asks the server to do the update, supplying the appropriate data. The server then takes that information and performs the update. If errors occur, the server backs out the update and alerts the client that there was a problem. This completely eliminates the possibility of a corruption by the client. Client/server databases are also designed to handle large numbers of users and intense processing. The isolation of the server from the clients allows the server to juggle many requests and respond to them efficiently.

Should you upgrade? There are 4 main factors to consider:

  1. Number of users. In the real world, the performance of a desktop database may start to degrade even when there are only 5-10 users running the database.
  2. Heavy processing activity. A small number of users can effect the performance of a desktop database if they are performing high-intensity data queries.
  3. Frequent corruptions and/or loss of data. This may be caused by either #1 or #2 or it may be caused by hardware problems, such as unstable computers or intermittent network connections.
  4. Security. Desktop databases generally don't have good security and can be accessed or stolen by unauthorized personnel.

Client/server databases range greatly in price, but many have come down in recent years. One example of this is Microsoft SQL Server, which, for some versions, can be purchased for about the same price as a high-end PC.

Summer 2003 -Volume 13, Number 3

 

 

All articles are copyrighted by the authors in the year published.