Connected and Disconnected Architecture in Ado.Net

Connected Architecture:-

In the connected architecture,connection with a data source is kept open constantly for data access as well as data manipulation operations.
the ado.net connect architecture consider mainly three type of objects.

sqlconnection con;]
sqlcommand cmd;
sqldatareader dr;

Disconnected Architecture:-

Disconnected is the main features of .net framework.ado.net contains various classes that support this architecture. the .net application does not always stay connected with the database. the classes are designed in a way that they automatically open and close the connection. the data is stored client-side and is updated in the database whenever required.
The ado.net disconnected architecture considers primarily the following types of objects are :-

dataset ds;
sqldataadapter da;
sqlconnection con;
sqlcommandbulider bldr;

OLEDB and SQL Managed Providers:-

ado.net, the successor of the Microsoft's highly successful ActiveX data objects offers two managed providers. this providers are similar in their object model but are chosen at design time based on the data provider been used. the SQL managed provider offers a direct link into Microsoft SQL server database application (version 7.0 or higher), while the OleDB provider is used for all other data providers. following is a brief description of each of the managed provider .next we will show you how the managed provider work and specify when the particular object property method or event is unique to only one of the managers providers.

Oledb Managed provider:-

the olddb managed provider use native Ole DB and com interop to establish a connection to a data store and negotiate commands. the OleDB provider is the data access provided to use when you are working with data from any data source that is not Microsoft SQL server 7.0 and higher. to use the oledb be managed provider, you must import the system.data.oledb namespace.

2. SQL Managed Provider:-

the SQL managed provider is designed to work directly with Microsoft SQL server 7.0 or greater. It connects and negotiate directly with SQL server without using oledb. This provides a better performance model than the OleDB managed provider, but it is a restricted to use with Microsoft SQL server 7.0 or higher. To use the SQL managed provider you must import the system. Data. SQL client namespace.

3.Managed Connections:-

must like much like classic ADO, the ole DB and SQL managed connection objects (ole DB connection and SQL connection) provide a set of properties and that might be familiar to use.

.Net Framework Notes

Always learning

Connected and Disconnected Architecture in Ado.Net