FUNDAMENTALS OF RESEARCH

PROF: ROSICAR ESCOBER

GIOVANNI V. MENDOZA IT III-1

DATABASE ISSUE Database Connection Problem

Introduction
Database connection problem is a common problem usually encountered by the programmer. It is the problem where some errors or problems occurs when connecting the database into applications that we are making.

Use this topic to troubleshoot problems that you experience when connecting to a report server. This topic also provides information about "Unexpected error" messages.

Study of Discussions from Other Authors about the Issue

Author: Jinwoo Hwang
a software engineer, inventor, author, and technical leader within the IBM WebSphere Application Server Technical Support team, which is based in Research Triangle Park, N.C. He joined IBM in 1995

Database connection
In computer science, a database connection is the means by which a database server and its client software communicate with each other. The term is used whether or not the client and the server are on different machines. The client uses a database connection to send commands to and receive replies from the server. Connections are a key concept in data-centric programming. Since some DBMSs require considerable time to connect, connection pooling is used to improve performance. No command can be performed against a database without an "open and available" connection to it. Connections are built by supplying an underlying driver or provider with a connection string, which is used to address a specific database or server and to provide instance and user

authentication credentials (for example, Server=sql_box;Database=Common;User

ID=uid;Pwd=password;).

Once a connection has been built, it can be opened and closed at will,

and properties (such as the command time-out length, or transaction, if one exists) can be set. The connection string consists of a set of key/value pairs, dictated by the data access interface of the data provider. Some databases, such as PostgreSQL, only allow one operation to be performed at a time on each connection. If a request for data (a SQL Select statement) is sent to the database and a result set is returned, the connection is open but not available for other operations until the client finishes consuming the result set. Other databases, such as SQL Server 2005 (and later), do not impose this limitation. However, databases that allow multiple concurrent operations on each connection usually incur far more overhead than those that only allow one operation at a time.

Pooling
Database connections are finite and 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 and close a database connection whenever it needs to update a database. Connection pooling is a technique designed to alleviate this problem. A pool of database connections is created and then shared among the applications that need to access the database. When an application needs database access, it requests a connection from the pool. When it is finished, it returns the connection to the pool, where it becomes available for use by other applications. The connection object obtained from the connection pool is often a wrapper around the actual database connection. The wrapper handles its relationship with the pool internally 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 might instead return it to the pool. The application does not need to be aware of the connection pooling when it calls the methods on the wrapper object.

This approach encourages the practice of opening a connection in an application only when needed, and closing it as soon as the work is done, rather than holding a connection open for the entire life of the application. In this manner, a relatively small number of connections can service a large number of requests. This is also called multiplexing. 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. It is desirable to set some limit on the number of connections in the pool. Using too many connections may just cause thrashing rather than get more useful work done. In case an operation is attempted and all connections are in use, the operation can block until a connection is returned to the pool, or an error may be returned.

Analysis/Findings
- I have found out that the common cause of this problem is that, when we dont pay attention on the important things to consider when connecting the database into the application that we are creating. -The basic solution for resolving these problems is compare and check if we really made the proper way of connecting the database considering the important part of the database connection.

Conclusion
My conclusion is that these connection problem would not occur if we will just be careful in connecting the database, we should make sure that we check first the important consideration before we connect it.

Recommendation

Make sure that the database server running If you're using WAMP, XAMPP, MAMP, Acquia Dev Desktop or any other type of *AMP stack that includes a control panel, ensure that the database server (usually a MySQL server) is running. This is often indicated by a red (not running) or green (running) light.

Select the correct Database type If you're using an *AMP stack, the "Database type" should be set to "MySQL, MariaDB, or equivalent".

Make sure that you enter the correct Database name Prior to installing Drupal, an empty database must be present - the name of this empty database must match the "Database name" that is entered during Drupal's installation process.

Make sure that the proper credentials was supplied in the settings file These settings are usually added to the settings.php file automatically via user prompts during Drupal's installation process. Ensure that the correct values were provided. These credentials are usually created during the *AMP installation process.

Check if you connecting to the proper database port Under most circumstances, the default database port and other settings in the "advanced options" fieldset do not need to be modified during installation unless the user specified non-default settings during the *AMP installation. A common mistake is modifying the default "advanced options" settings unnecessarily.