Scribd
Upload
47 views1 page

Recordset Connected: Firewalls

ADO had issues when implemented over networks due to keeping database connections open for the lifetime of an application, raising security and performance concerns as databases served more users. ADO.NET was introduced to address these problems with a disconnected data access model, opening connections only to fulfill requests and then closing them to conserve resources and maximize security while having less impact on system performance. ADO.NET also uses XML and converts data to XML format for efficient database operations. Data access in ADO.NET relies on two components: the DataSet and the Data Provider.

Uploaded by

Raghavendra Shivaram
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
47 views1 page

Recordset Connected: Firewalls

ADO had issues when implemented over networks due to keeping database connections open for the lifetime of an application, raising security and performance concerns as databases served more users. ADO.NET was introduced to address these problems with a disconnected data access model, opening connections only to fulfill requests and then closing them to conserve resources and maximize security while having less impact on system performance. ADO.NET also uses XML and converts data to XML format for efficient database operations. Data access in ADO.NET relies on two components: the DataSet and the Data Provider.

Uploaded by

Raghavendra Shivaram
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 1

ADO Connected Architecture

With ADO, all the data is contained in a recordset object which had problems when
implemented on the network and penetrating firewalls. ADO was a connected data
access, which means that when a connection to the database is established the
connection remains open until the application is closed. Leaing the connection open
for the lifetime of the application raises concerns about database securit! and
network traffic. Also, as databases are becoming increasingl! important and as the!
are sering more people, a connected data access model makes us think about its
productiit!. "or e#ample, an application with connected data access ma! do well
when connected to two clients, the same ma! do poorl! when connected to $% and
might be unusable when connected to $%% or more. Also, open database connections
use s!stem resources to a ma#imum e#tent making the s!stem performance less
effectie.
ADO.&et'Disconnected
(o cope up with some of the problems mentioned aboe, ADO .&)( came into
e#istence. ADO .&)( addresses the aboe mentioned problems b! maintaining a
disconnected database access model which means, when an application interacts
with the database, the connection is opened to sere the re*uest of the application
and is closed as soon as the re*uest is completed. Likewise, if a database is +pdated,
the connection is opened long enough to complete the +pdate operation and is
closed. ,! keeping connections open for onl! a minimum period of time, ADO .&)(
conseres s!stem resources and proides ma#imum securit! for databases and also
has less impact on s!stem performance. Also, ADO .&)( when interacting with the
database uses -.L and conerts all the data into -.L format for database related
operations making them more efficient.
Data Access in ADO.&)( relies on two components/ Data0et and Data 1roider.

You might also like