Database connectivity in .

Net

Before .NET TECH

DATABASE:It is used to store,maintain retrieve
or manipulate the data
It is of 3 types:

ISAMDB

These are stand alone and n/w unaware database

models like

VSAMDB

These are n/w aware and client server based databases

for e.g.: ms-excess,dbase

For e.g. : Oracle,Sql-server

INTERNET DATABASE

These can be any database which can be populated on

the web

For eg:OLTP DB,OLAP DB,Index Server etc

Normal structure

Application

Drivers

database

Classic Implementation

Win 32 API

Application

Drivers

pro

db

Drawback and Solution

The

limitation of the above model is: It

is mandatory for the user to know the
host and the destination data types.
So the requirement was a database
object model to interact with the
databases without the knowledge of the
Host and the destination data types.
Solution : Object Models

Database connectivity using

Object Models
Application

Drivers/
Providers

Object Model

Protocols

db

DAO

Data Access Objects

RDO

Remote Data Objects

ADO

ActiveX Data Objects

SQL

SQL Server Config Manager

For one requirement you have many

solutions when to use which model

APPLICATION

DAO

JET
ENGINES

ISAM DB

RDO

ODBC DRIVERS
(DSN-BASED CONNECTIVITY

VSAM DB

ADO

OLEDB
PROVIDERS

Internet
db

DAO
It

is a special model to interact with the

ISAM db with the support of JET
engines.If DAO model is used to interact
with the VSAM db,then data
inconsistency might occur

RDO
It is a special model to interact with the VSAM
db using the ODBC(open database connectivity)
drivers.If RDO model is used to interact with the
ISAM db as that model performs all the N/W
verifications and all the performance of the
application might decrease to 10-15%
Requirement: An object model to interact any
type of DBS in the past and future dbs without
any performance loss
Solution is ADO

ADO
It

is a special model to interact with any

type of databases with the support of
OLEDB providers or ODBC drivers