Shulou(Shulou.com)06/02 Report--

This article mainly explains "how to understand the debugging of ADO.Net database". Interested friends may wish to have a look at it. The method introduced in this paper is simple, fast and practical. Next let the editor to take you to learn "how to understand ADO.Net database debugging problems"!

This is why we generally use only one connection for a database in Delphi. In order to reduce the number of database connections to reduce the database burden, of course, COM+ and MTS also provide connection pooling mechanism, but its connection pooling mechanism does not seem to be very mature, especially the use of system data connection pooling in MTS may cause system deadlock. Of course, we can use our own connection pooling or third-party connection pooling to manage database connections.

In ADO.Net, this function is part of the system, but it is found that only when the connection is closed will it be returned to the pool. if the database connection that has been used has not been returned to the pool continuously, ADO.Net will actually create the database connection and return it to the user.

Thus it can be seen that it is a terrible thing to keep asking for a connection without closing the connection in ADO.Net. My view of connections in ADO.Net is to close (return to the system connection pool) as early as possible, which can speed up the system response and reduce the number of database connections. It's interesting to close ADO connections. Sometimes the speed at which we connect to the database limits how often we close and open connections, so we may need to keep some connections to get speed.

ADO.Net is a new generation of Microsoft data access engine, which uses OLE DB as the basis of data access technology and adopts the way of data set separation to access and modify data. ADO is Microsoft's previous generation data access engine, and it is also a data access engine (or component) for data access based on OLE DB. ADO is a data access component encapsulated by OLE DB engine using COM.

The data access technology for ADO is relatively mature. ADO can disconnect or keep opening connections when accessing data. But keeping a connection is wasteful for ADO.Net because its data has been referred to the client for processing and has nothing to do with the database.

So in ADO.Net 's database system, the database connection is usually closed after the data is retrieved or the operation is completed (in fact, it may not be closed). The closing of ADO.Net 's database connection is returned to the buffer pool rather than being disconnected from the database. When to close this connection is determined by ADO.Net 's buffer pool management mechanism. And if the connection is closed when ADO is in use, then the connection is really closed.

At this point, I believe that everyone on the "ADO.Net database debugging problems how to understand" have a deeper understanding, might as well to the actual operation of it! Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.