Whenever we develop various applications using ADO.NET, the requirements will be different with these applications with respect to working with data. Sometimes you will only want to display the data on a form, whereas in some cases that data might be needed to pass on to some other company. Whatever operations you do with the data, fundamental concept of data approach in ADO.NET is the same. In ASP.NET, data access from the database is done by making use of the technology ADO.NET. In this section, let us discuss how to access data using ADO.NET technology.

ADO.NET does not depend on live connections continuously

As we are aware that in traditional client/server applications, components will be connected to a database and it is kept open while the …show more content…
In many cases, databases will be able to maintain only a small number of parallel connections. The overall maintaining all these connections reduces the overall application performance.
• Similarly, applications that work with an open database connection are very difficult to scale up. The web applications of ASP.NET in particular need to be easily scalable, as the traffic to a Web site can go up by orders of magnitude in a very short period.
• In ASP.NET Web applications, the components are disconnected from each other. The browser will request a page from the server; once the server has finished the process and sends the page, it has no further connection with the browser till the next request. Under such situations, maintaining an open connection to a database is not feasible, as there is no way to know whether the client will require further access to the data.
• A data that is always-connected will be difficult and impractical to exchange data through various applications. If two components are required to share the same data, both will have to be connected, or there must be a way where in the components can be pass the data back and