Bert, while the article is correct, the question still remains:
In a client-server architecture, how much work is being done on the server and how much is being done on the client?
Let me give you an example:
Lets say we want to find all patients with the first name james and then order the results by last name in ascending order (A-Z).
The SQL Query will have two parts:
1) SELECT * from patients WHERE first name='James'
2) ORDER by LastName ASC
The speed of this query depends on WHERE the ordering is done and there are 2 scenarios:
1) Send the entire query to SQL Server and have the server do the 'SELECTING' and the 'ORDERING'
2) Send only the select to SQL Server and have the CLIENT do the ordering.
The most efficient way to do this is to let the server do the processing and return the result set exactly as it is desired. This way the CLIENT is only DISPLAYING, ALTERING and SUBMITTING DATA. The server is doing the PROCESSING.
The most efficient client server systems we use today are WEB PAGES that transact business. The browser is only used to display the data, and does no processing on the client. The processing power of the client is irrelevant. All the data is sent to the server to process. So when we are looking at our bank transactions the data is not sent to the browser for organization and processing, instead we see a grid that displays all the rows of data we need.
Last edited by gkfahnbulleh; 02/08/2009 7:06 PM.
