UNIVERSAL DATA ACCESS (ODBC)

UNIVERSAL DATA ACCESS (ODBC)

ODBC

A open standard to connectivity between data bases machine.

This standard provide API able to be used to run and connecting an application with a data bases management system ( SMBD).

Designer ODBC make it with a purpose to [so that/ to be] ODBC free from usage of Programming Language selected, selected data bases management system, and selected operating system.

ODBC Component

  1. ODBC API : A group of function call, mistake codes and syntax SQL defining how do data in a DBMS accessed.
  2. Driver data bases ODBC : driver ( which in the form of dynamic link library) capable to process the function call ODBC to a DBMS.
  3. ODBC Driver Manager : ODBC Driver Manager : commissioned to load driver data bases ODBC required by application

Can be woke up to the specification of:

  1. “ Front-End” or “ client” desktop application, is also known as “ ODBC CLIENT”. This Application walking in computer user.
  2. ODBC DRIVER to “ Back-End” or “ Server” DBMS ( Database management Systems). Application DBMS this reside in [at] used computer to [be] depository [of] data to in accessing by some user

Application Server this [is] more ROBUST(faster, with central security and back up data) from [at] application client. ODBC DRIVER reside in [among/between] ODBC Client and DBMS.

Usage ODBC:

For usage ODBC required [by] 3 component :

  1. ODBC CLIENT : ODBC ENABLED front-end example [of] : Microsoft Access, Application which is woke up with Ms. Access, Application which is woke up with VB, Application which is woke up with C++ Win SDK+ODBC SDK, or the application woke up from vendor besides Microsoft.
  2. ODBC DRIVER : ODBC DRIVER to ODBC Server. The example : Ms. ODBC DRIVER pack, SQL Server ODBC, Informix ODBC, MySQL
  3. ODBC DBMS Server ( back-end) : DBMS server this can in accessing by ODBC Client with medium ODBC Driver

Example DBMS Server : SQL SERVER, Oracle, AS/400,Foxpro, Ms. Access, Mysql

No comments: