Modifying Connection Records

1. A method of modifying a set of connection records, the method comprising: determining that an application failed to access a first database via a connection record, wherein the connection record includes data to access the first database; determining that a second database is accessible, wherein the second database is a failover database to the first database; modifying a set of connection records associated with the first database to enable access to the second database; identifying a connection record that was not successfully modified to enable access to the second database; and deleting the connection record that was not successfully modified.

2. The method of claim 1 , further comprising modifying the connection record to enable access to the second database before modifying the set of connection records, wherein modifying the connection record enables the application to continue processing substantially without interruption.

3. The method of claim 1 , wherein each connection record in the set of connection records is modified to enable access to the second database in response to determining that the application failed to access the first database via the connection record.

4. The method of claim 3 , wherein modifying each connection record of the set of connection records to enable access to the second database is performed substantially concurrently.

5. The method of claim 1 , wherein before modifying the set of connection records to enable access to the second database, at least one connection record in the set of connection records is identified as not currently in use.

6. A computer program product comprising a non-transitory computer usable medium including a computer readable program, wherein the computer readable program when executed by a computer causes the computer to: detect a failed attempt to access a first database via a connection record; modify the connection record to enable access to a second database; identify a set of connection records associated with the first database; modify each connection record of the set of connection records to enable access to the second database; and delete at least one modified connection record from the set of connection records, wherein the at least one deleted modified connection record was not successfully modified to enable access to the second database.

7. The computer program product of claim 6 , wherein one or more connection records from the set of connection records are used by an application to enable access to the second database after each connection record of the set of connection records is modified to enable access to the second database.

8. The computer program product of claim 6 , wherein the connection record is modified to enable access to the second database after determining that the second database is accessible.

9. A system, comprising: a database driver module adapted to: determine that a second database is accessible after detecting a failed attempt to access a first database via a connection record; modify the connection record to enable access to the second database; modify each connection record of a set of connection records associated with the first database to enable each connection record to enable access to the second database, wherein at least one connection record of the set of connection records is identified as currently not in use; and delete at least one modified connection record from the set of connection records, wherein the at least one deleted modified connection record was not successfully modified to enable access to the second database.

10. The system of claim 9 , further comprising: a connection pool manager module to: identify the set of connection records associated with the first database before the database driver module modifies the set of connection records to enable access to the second database.

11. The system of claim 9 , wherein the database driver module is adapted to send a message to the connection pool manager module, wherein the message indicates whether each connection record of the set of connection records was successfully modified.

12. The system of claim 11 , wherein further comprising: an event listener module to: receive from the database driver module a message indicating that an event occurred; and send an event notification message to the connection pool manager module that the event occurred.

13. A method, comprising: receiving a reroute notification that a connection record was modified to enable the connection record to enable access to a second database instead of a first database, wherein the second database comprises a failover database to the first database; identifying a set of other connection records associated with the first database; sending a mass reroute request to modify the set of other connection records; receiving a mass reroute result identifying connection records that were not successfully modified; and deleting the connection records that were not successfully modified.

14. The method of claim 13 , wherein at least one connection record of the set of other connection records has an idle status, and wherein the at least one connection record with the idle status is not in use by an application.

15. The method of claim 13 , wherein the reroute notification that the connection record was modified to enable access to a second database.

16. The method of claim 15 , wherein the mass reroute request identifies the set of other connection records to be modified to enable access to the second database.

17. A non-transitory computational component for use in directing one or more computing devices to reroute a set of connections from a database to a failover database, the computational component comprising encoded computing device instructions emanating from a tangible computer readable medium, the encoded computing device instructions electronically accessible to at least one of the one or more computing devices for execution, the execution causing the one or more computing devices to: modify a connection record to access a second database instead of a first database to enable access to a second database, wherein the connection record is modified to include information to route data with respect to the second database; identify a set of connection records associated with the first database; modify the set of connection records to enable access to the second database; and delete connection records of the set of connection records that were not successfully modified.

18. The computational component of claim 17 , wherein the execution of the encoded computing device instructions further causes the one or more computing devices to modify the connection record to enable access to the second database in response to detecting a failure of an application to access the first database via the connection record.