Database connection: Difference between revisions

Revision as of 10:32, 7 November 2019

Latest revision as of 13:14, 19 July 2025

(11 intermediate revisions by 9 users not shown)

Line 1:

{{Short description|Link between a client and database server}}

A '''Database connection''' is a facility in [[computer science]] that allows [[Client (computing)|client]] software to talk to [[database server]] software, whether on the same machine or not. A '''connection''' is required to send [[command (computing)|commands]] and receive answers, usually in the form of a result set.

{{no inline sources|date=July 2025}}

A '''Databasedatabase connection''' is a facility in [[computer science]] that allows [[Client (computing)|client]] software to talk to [[database server]] software, whether on the same machine or not. A '''connection''' is required to send [[command (computing)|commands]] and receive answers, usually in the form of a result set.

Connections are a key concept in [[data-centric]] programming. Since some DBMS engines require considerable time to connect, [[connection pooling]] was invented to improve performance. No command can be performed against a database without an "open and available" connection to it.

Line 9 ⟶ 11:

== Pooling ==

Database connections are finite and [[time complexity|expensive]] and can take a disproportionately long time to create relative to the operations performed on them. It is very inefficient for an application to create, use, and close a database connection whenever it needs to update a database.

[[Connection pool]]ing is a technique designed to alleviate this problem. A pool of database connections can be created and then shared among the applications that need to access the database. When an application

The connection object obtained from the connection pool is often a wrapper around the actual database connection. The wrapper understands its relationship with the pool, and hides the details of the pool from the application. For example, the wrapper object can implement a "close" method that can be called just like the "close" method on the database connection. Unlike the method on the database connection, the method on the wrapper may not actually close the database connection, but instead return it to the pool. The application need not be aware of the connection pooling when it calls the methods on the wrapper object.

Line 19 ⟶ 21:

In a client/server architecture, on the other hand, a persistent connection is typically used so that server state can be managed. This "state" includes server-side cursors, temporary products, connection-specific functional settings, and so on.

An application failure occurs when the connection pool overflows. This can occur if all of the connectionconnections in the pool are in use when an application requests a connection. For example, the application may use a connection for too long when too many clients attempt to access the web site or one or more operations are blocked or simply inefficient.

== See also ==

* [[Open Database Connectivity]]

* [[ActiveX Data Objects|ADO]]

* [[ADO.NET]]

* [[ODBC|ODBC (Open Database Connectivity)]]

* [[JDBC]]

* [[RDBMS]]