Identifying database request sources

• US 20070100793A1
• Filed: 10/20/2005
• Published: 05/03/2007
• Est. Priority Date: 10/20/2005
• Status: Active Grant

• Current Assignee: Teradata US, Inc. (Teradata Corporation)
• Original Assignee: Teradata US, Inc. (Teradata Corporation)
• Inventors: Ramesh, Bhashyam, Brown, Douglas, Richards, Anita
• Granted Patent: US 8,280,867 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems

Abstract

A method, computer program, and database system are disclosed for identifying a second source of a request sent to a database management system by a first source. A database message is received from the first source. The database message includes a second value for a second source-identifying parameter. The second value identifies a second source. The second value for the second source-identifying parameter is stored in a log.

Claims

1. A method for identifying a second source of a request sent to a database management system by a first source, the method including:

receiving a database message from the first source, the database message including a second value for a second source-identifying parameter, the second value identifying a second source; and

storing the second value for the second source-identifying parameter in a log.

2. The method of claim 1 where:

the database message includes a first value for a first source-identifying parameter, the first value identifying the first source;

storing the first value for the first source-identifying parameter in the log.

3. The method of claim 1 where the second source is above the first source in a multi-tier architecture for sending requests to the database management system.

4. The method of claim 1 where the second source submits requests through the first source to the database management system in a session pooling environment.

5. The method of claim 1 where the database message includes a second timestamp information related to the time that the second source performed processing related to the message.

6. The method of claim 1 further including:

initiating a session associated with the second source when the database message is a session-initiating database message;

receiving a subsequent database message from the first source including the second value for the second source-identifying parameter; and

storing the second value for the second source-identifying parameter from the subsequent database message in the log in such a way that the second value from the subsequent database message is associated with the session.

7. The method of claim 1 further including:

using the second value stored in the log to manage the allocation of the database system resources.

8. A computer program, stored on a tangible storage medium, for use in identifying a second source of a request sent to a database management system by a first source, the computer program including executable instructions that cause a computer to:

receive a database message from the first source, the database message including a second value for a second source-identifying parameter, the second value identifying a second source; and

store the second value for the second source-identifying parameter in a log.

9. The computer program of claim 8 where:

the database message includes a first value for a first source-identifying parameter, the first value identifying the first source;

storing the first value for the first source-identifying parameter in the log.

10. The computer program of claim 8 where the second source is above the first source in a multi-tier architecture for sending requests to the database management system.

11. The computer program of claim 8 where the second source submits requests through the first source to the database management system in a session pooling environment.

12. The method of claim 8 where the database message includes a second timestamp information related to the time that the second source performed processing related to the message.

13. The computer program of claim 8, where the computer program further includes executable instructions that cause the computer to:

initiate a session associated with the second source when the database message is a session-initiating database message;

receive a subsequent database message from the first source including the second value for the second source-identifying parameter; and

store the second value for the second source-identifying parameter from the subsequent database message in the log in such a way that the second value from the subsequent database message is associated with the session.

14. The method of claim 8, where the computer program further includes executable instructions that cause the computer to:

use the second value stored in the log to manage the allocation of the database system resources.

15. A database system including:

a massively parallel processing system including

one or more nodes;

a plurality of CPUs, each of the one or more nodes providing access to one or more CPUs;

a plurality of data storage facilities each of the one or more CPUs providing access to one or more data storage facilities;

a process, running on one or more of the plurality of CPUs, for identifying a second source of a request sent to a database management system by a first source, the process including;

receiving a database message from the first source, the database message including a second value for a second source-identifying parameter, the second value identifying a second source; and

storing the second value for the second source-identifying parameter in a log.

16. The database system of claim 15 where the second source is above the first source in a multi-tier architecture for sending requests to the database management system.

17. The database system of claim 15 where the second source submits requests through the first source to the database management system in a session pooling environment.

18. The database system of claim 15 where the database message includes a second timestamp information related to the time that the second source performed processing related to the message.

19. The database system of claim 15 where the process further includes:

initiating a session associated with the second source when the database message is a session-initiating database message;

receiving a subsequent database message from the first source including the second value for the second source-identifying parameter; and

storing the second value for the second source-identifying parameter from the subsequent database message in the log in such a way that the second value from the subsequent database message is associated with the session.

20. The database system of claim 15 where the process further includes:

using the second value stored in the log to manage the allocation of the database system resources.