menu close

Networking Support

The client/server model in the database environment is defined as a separation of information processing into two parts: a client portion that requests database information and a server portion which manages that database information.

Network Performance

Many PC database systems extract data inefficiently from the server, resulting in increased network traffic. In this type of system all of the data needed to process a request travels over the network and the processing occurs on the client machine. The client/server model results in a decrease of network traffic because all data processing occurs on the server machine so that only the data requested by the client travels over the network.

Utilization of Resources

The client / server architecture also allows you to better utilize your company’s computer resources. Powerful machines can be utilized as servers since these machines tend to perform large amounts of data processing. Client / server architecture also utilizes the client machines because the power provided in the client side PC’s can be used to implement end-user applications that are user friendly. For example; an end-user is able to take advantage of a number of graphical user interfaces (GUI) such as Microsoft Windows. The client / server separation also allows for a separation in the management of the database system. A company could have one group or department responsible for the maintenance and backup of the database and other groups responsible for the creation and maintenance of the database files.


For each server, multiple clients may attempt to simultaneously access the same information. The client / server model ensures concurrence, without jeopardizing data integrity, among multiple clients, The server resolves any concurrence issues. For example, if two clients update the same data at the same time, row level locking ensures that concurrence issues do not affect the integrity of the data.


Security of the database can be enforced and managed because the client / server model defines a clear separation of information processing. The database remains properly guarded against improper access since the database server physically resides on a machine that is independent of the clients.

Have Questions?

Contact MeasurLink Today

If you have installation problems with any product, please contact us as soon as possible. We can help resolve the issue or take other measures to get you up to speed as quickly as possible.

Contact Us


Structured Query Language (SQL) is an ANSI standard method for describing the access to relational databases. MeasurLink accesses the database by using embedded SQL statements in the Microsoft Visual programming languages code that created the various modules. Database servers automatically adapt to utilize a computer’s available memory and resources for increased performance.

Data Integrity

SQL implements transaction processing to ensure the integrity of the information in the database. Transaction processing guarantees that any transaction is performed as a single unit of work. Transaction processing is enabled through the COMMIT and ROLLBACK statements. At any time, issuing a COMMIT statement makes any work in progress permanent. Alternatively, issuing a ROLLBACK statement will undo all of the work back to the last COMMIT statement. More importantly, if the system goes down (power failure, machine failure) a ROLLBACK statement is automatically issued when the database is restarted.

Data Consistency

The MeasurLink database is created without the use of primary or foreign keys. Each table in the database is, however, created with indexes which ensures uniqueness and completeness of data entries. The indexes also provide a method for query optimization to improve response time on database interaction.
Referential integrity between tables is programmatically enforced to ensure that insertions, modifications, and deletions are properly made across the entire database.

Cost-based Query Optimization

The database server automatically optimizes transactions to determine the fastest way possible to perform SQL queries. Cost-based optimization of the query means that no matter which way the query was worded, the execution time of the query will always be the same. Also, the database server automatically takes advantage of the existing indexes to improve the performance of the query.