Thursday, 28 July 2016

difference between connected and disconnected architecture in ado.net

x
 


Connected and Disconnected Architecture Ado.Net


Differences between Connected and Disconnected Architecture in ADO.Net inAsp.net. To communicate with database we must have connection from front end application to database.

They can be of two type.
Connected Architecture:
(1)- In Connected Architecture you have to declare the connection explicitly by using Open() and close the connection by using Close() and you can execute commands using different methods likeExecuteNonQuery(),ExecuteScalar() and ExecuteReader().

(2)- Connected Environment needs constantly connection of user to datasource while performing any operation.

(3)- Only one operation can be performed at a time in connected environment.

(4)- Connected environment is slower in speed.

(5)- We get updated data in connected environment.

Disconnected Architecture:
(1)- In Disconnected Architecture, you don't need to define the connection explicitly.Sql DataAdopter itself can open and close the connection and you can use dataset for storing the information temporarily and Fill() is used to execute the commands give in adopter.

(2)- Disconnected environment doesn't need any connection.

(3)- Multiple operations can be performed at a time in disconnected environment.

(4)- It has a good speed.

(5)- In disconnected environment, there is a problem in dirty read.

Also check What is Connection Pooling in Asp.Net ?




Connected Disconnected
It is connection oriented.
It is dis_connection oriented.
Datareader DataSet
Connected methods gives faster performance
Disconnected get low in speed and performance.
connected can hold the data of single table disconnected can hold multiple tables of data
connected you need to use a read only forward only data reader
disconnected you cannot
Data Reader can't persist the data
Data Set can persist the data
It is Read only, we can't update the data.
We can update data