Database-Desktop or server?

Selecting a database platform for your organization's infrastructure can be an overwhelming project. IT professionals faced with this daunting task may have no prior database experience and are suddenly thrown into an arena full of vaguely familiar terms and a vast range of products with drastically differing price tags. Database management systems (or DBMSs) can be divided into two categories--desktop databases and server databases. Generally speaking, desktop databases are oriented toward single-user applications and reside on standard personal computers (hence the term desktop). Server databases contain mechanisms to ensure the reliability and consistency of data and are geared toward multi-user applications. These databases are designed to run on high-performance servers and carry a correspondingly higher price tag. Its important to do a careful needs analysis before you commit to a database solution. You'll often find that a desktop database is suitable for your business requirements when you originally planned to purchase an expensive server- based solution. On the other hand, you may uncover hidden requirements--present or future--that necessitate the deployment of a scalable server-based database. The needs analysis team should include individuals involved in the design, deployment and support processes as well as a representative sample of end users. When you sit this group of people around a conference table and discuss your proposed solution, you're guaranteed to uncover issues nobody considered in the past. Don't let this be a blow to your ego - take it in stride and be thankful that it was discovered at this early stage rather than after massive expenditures of time and money.

The needs analysis process will be specific to your organization but, at a minimum, should answer the following questions* Who will be using the database and what tasks will they perform?

* How often will the data be modified? Who will make these modifications?

* Who will be providing IT support for the database?

* What hardware is available? Is there a budget for purchasing additional hardware?

* Who will be responsible for maintaining the data?

* Will data access be offered over the Internet? If so, what level of access should be supported?

Once you've gathered the answers to these questions, you'll be prepared to begin the process of evaluating specific database management systems. You may discover that a sophisticated multi-tier server platform (like SQL Server or Oracle) is necessary to support your complex requirements.

On the other hand, a desktop database like Microsoft Access might be just as capable of meeting your needs (and much gentler on your pocketbook!)

Desktop Databases

Desktop databases offer an inexpensive, simple solution to many less complex data storage and manipulation requirements. They earn their name by virtue of the fact that they are designed to run on 'desktop' (or personal) computers. You're probable familiar with a few of these products already--Microsoft Access, FoxPro, FileMaker Pro, Paradox and Lotus Approach are the major players.

The following are a few of the benefits gained by utlizing a desktop database

* Desktop databases are inexpensive.

You'll find that most desktop solutions are available for around $100 (compare to thousands of dollars for their sever-based cousins). In fact, if you own a copy of Microsoft Office Professional, you're already a licensed owner of Microsoft Access.

* Desktop databases are user-friendly.

A thorough understanding of SQL is not required when using these systems (although many do support SQL for die-hards out there). Desktop DBMS's usually offer an easy-to-navigate graphical user interface 

* Desktop databases offer web solutions.

Many modern desktop databases provide limited web functionality enabling you to publish your data on the web in a static or dynamic fashion.

After reading this far, you might wonder why anyone would use something other than a desktop database. Well, as the old adage goes, you get what you pay for. Desktop databases also have a number of limitations:

Despite the claims of manufacturers, most desktop database only allow one concurrent user to modify the database. Attempting to use a desktop database in a multiuser environment could lead to disastrous consequences. Generally speaking, if more than one person will be modifying the data, its best to consider a server -based database.

* Desktop databases have weak security

Most desktop databases support a simple password protection scheme. If you're looking for complex security and auditing capabilities, a server based database is the way to go.

* Desktop databases are not designed for the Internet.

If you're simply looking to publish data on the web, a desktop database will work just fine. However if you'd like to create an interactive system that allows Internet users to modify and insert data, you'll be better off with a server-based DBMS.

Server Databases

Oracle and Microsoft SQL Server dominate this industry while IBM's DB2 offering and the Postgres, Ingres and Sybase systems maintain a smaller market share. These systems have become household names due to the great opportunities they offer organizations to manage large amounts of data quickly, efficiency and in a manner that enables many users to access and update the data simultaneously. If you're able to meet the hefty pricetag, a server-based database can provide you with a comprehensive data management solution. The benefits achieved through the use of a server-based system are diverse which include:

* Flexibility. Unlike their desktop cousins, server-based databases can handle just about any data management problem you can throw at them. Developers love these systems because they have progammer- friendly application programme interfaces (or APIs) that provide for the rapid development of database oriented custom applications. The Oracle platform is even available for multiple operating systems, providing Unix junkies with a level playing field when paired off against Microsoft users.

* Powerful performance.

Server-based databases are as powerful as you want them to be. The major players are able to efficiency utilize just about any reasonable hardware platform that you're able to construct for them. Modern databases can manage multiple high-speed processors, clustered servers, high bandwidth connectivity and fault tolerant storage technology.

* Scalability.

This attribute goes hand-in-hand with the previous one. If you're willing to provide the necessary hardware resources, server databases are able to gracefully handle a rapidly expanding amount of users and/or data. It's not all peaches and cream with server-based databases. Here are a few of the limitations

* Specialized knowledge/training is required.

A server-based database is not something that you want to learn by the seat of your pants. It's advisable to gain the specialized knowledge required to implement this type of system BEFORE you make the investment in hardware and software. This training will help you to assess the need for this substantial investment and provide you with the background necessary to plan an effective deployment and implementation strategy

* Expensive.

The benefits achieved by a server-based system are going to cost you. First, you'll need to make a significant hardware investment to purchase the dedicated high-performance system that many database applications demand. Second, you can expect to shell out somewhere between $3,000 and $15,000 in licensing fees for an average single processor system.

* Difficult for end users.

Generally speaking, your end users will not be presented with a friendly graphicael front end unless you create or purchase one for them--something you'll have to do unless your users are versed in the intricacies of SQL. Desktop databases often serve as excellent front ends for server databases. As an example, many organizations use desktop copies of Microsoft Access to provide a friendly, familiar interface for analysts accessing a corporate SQL Server database.