The first of these was the mainframe architecture. This had a powerful central host computer that carried out all the processing. To use the system the user connected to the mainframe via a dummy terminal. However as the industry moved towards the use of Graphical User Interfaces this model started to falter as incorporating them was very difficult.

The second type is the file sharing architecture. In this model the server sends the requested file to the terminal where it can be used. This means that it uses the terminals resources taking a lot of strain off the server. However it does have problems if the amount of data being transferred is high and it can also lead to problems with data consi

SQL is the backbone of the ODBC and JDBC standards. SQL started life in the 1970's as a prototype language from IBM called SEQUEL which stood for "Structured English Query Language". This evolved into SEQUEL/2 in 1977 but the name was later shortened to SQL. This change in name has led many to believe that the SQL is an acronym for "Structured Query language" and that it's pronounced "sequel". In fact SQL doesn't mean anything and is pronounced "S Q L". SQL is a 4th generation programming language however it is not fully formed so cant be used on its own and is normally combined with a 3rd generation programming/scripting languages like JAVA, C++, Perl, PHP and VB.

The most important part of ODBC is the driver manager. This stores information on all the database specific drivers installed on the system. This then allows it to quickly and easily make a function call to the required driver. Once the correct driver has been called it can then get down to work and process the request. First the driver will connect to the DBMS. If the data is in the right format for the DBMS to handle it will submit the requests immediately but many DBMS will need the SQL command translated into its native language. If translation is required this will be handled by the driver. Once the command has been executed it will pass the information back to the application so that it can manipulate it or display it on screen for the user. The driver can also pass back any error messages the DBMS gives it so that the user/application can use them to solve any problems with the system.

The type 3 driver is an 'All java driver'. The JDBC calls are translated into the middleware vendor's protocol and this is then changed into a database specific protocol by the middleware. This offers improved speed over types 1 and 2 and also allows a single JDBC driver to connect to more than one data source. The client also doesn't need any drivers installed locally.

SQL has three main tasks that it can carry out these are data manipulation, data definition and data management. The data manipulation part is involved with the inserting editing and retrieval of data. This is done through a number of commands some of which are SELECT (to retrieve data), INSERT (to store data), DELETE (to remove data) and UPDATE (to change data)

The application layer is the users interface into the system. When the user requests data the Application will first send a request for a connection, without a connection it is unable to retrieve the required data. If this connection request is accepted the application can then submit its request via an SQL statement. This SQL statement is then passed onto ODBC where it is handled.

Some common words found in the essay are:
JDBC Driver, Process ODBC, Transaction Processing, Design Louis, User Interfaces, Database Management, Unlike TP, DBMS SQL, Client/Server Models, Management System, middle tier, database management, database management system, management system, drivers installed, system allows, server system, transaction processing, client/server model, sql statement, client server, transaction processing monitor, middle tier implemented, graphical user interfaces, tier client server,
Approximate Word count = 2302
Approximate Pages = 9 (250 words per page double spaced)