Sending control information with database statement

• US 8,825,702 B2
• Filed: 02/24/2004
• Issued: 09/02/2014
• Est. Priority Date: 02/24/2004
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Wong, Daniel Manhung
• Primary Examiner(s): Beausoliel, Jr., Robert
• Assistant Examiner(s): Pham, Michael
• Application Number:
  US10/786,941
• Publication Number:
  US 20050187958A1
• Time in Patent Office: 3,843 Days
• Field of Search: 707 1-100, 707/781
• US Class Current: 707/781
• CPC Class Codes: G06F 16/217 Database tuning G06F16/2282 takes precedence; database performance monitoring G06F11/3409
• CPC Class Codes: G06F 16/2448 for particular applications; for extensibility, e.g. user defined types
• CPC Class Codes: G06F 16/2457 with adaptation to user needs

Abstract

Sending control information that is associated with a statement that controls how the statement is processed is disclosed. The information is available to the server even after the window session is closed. The information may be contained in a tag appended to the statement. In an embodiment, the information may be viewed by an administrator. The information may determine aspects of how the statement is executed that is not controlled by the execution engine. For example, the information may relate to security access, priority, quality of service, scheduling, and or use supplied routines.

Claims

1. A machine-implemented method for executing a database statement, the method comprising the steps of:

a database server receiving a request to execute the database statement, wherein the request includes the database statement and a tag that does not conform to a database language of said database statement, wherein said tag is not embedded in said database statement;

wherein said tag specifies at least one parameter field and at least one parameter value;

in response to receiving the request, said database server storing information from the tag in a manner that is associated with said database statement and accessible to a tag access mechanism; and

said database server executing said database statement, wherein during execution of said database statement said database server provides access to one or more of the at least one parameter value through said tag access mechanism provided by said database server.

2. The method of claim 1, wherein the database statement is written in a language in which results desired are specified by the database statement, and no procedures for obtaining the results desired are specified by the database statement.

3. The method of claim 1, wherein a priority for executing the database statement is determined based on the at least one parameter value.

4. The method of claim 1, wherein a security level is associated with the at least one parameter such that whether the database is entitled to access a component is based on the at least one parameter.

5. The method of claim 1, wherein the at least one parameter is accessible to a systems administrator.

6. The method of claim 1, wherein the at least one parameter is related to user context information.

7. The method of claim 1, wherein the tag comprises an indicator of a beginning of the tag, and an indicator of an end of the tag.

8. The method of claim 7, wherein the at least one parameter value is located between the indicator of the beginning and the indicator of the end of the tag.

9. The method of claim 8, wherein each of the at least one parameter fields comprises an indicator of a beginning of the parameter field, followed by the parameter value, which in turn is followed by an indicator of an end of the parameter field.

10. The method of claim 1, wherein the at least one parameter value can be accessed without accessing memory allocated to a database session, wherein the database statement was issued within the database session.

11. The method of claim 4, wherein the at least one parameter value can be accessed without accessing memory allocated to a database session, wherein the database statement was issued within the database session.

12. The method of claim 2, wherein the at least one parameter value can be accessed without accessing memory allocated to a database session, wherein the database statement was issued within the database session.

13. The method of claim 1, wherein the at least one parameter value can be accessed after a session window has closed, wherein the database statement was issued within the session window.

14. A non-transitory machine-readable storage medium storing one or more sequences of instructions, which when executed by one or more processors, cause:

a database server receiving a request to execute a database statement, wherein the request includes the database statement and a tag that does not conform to a database language of said database statement, wherein said tag is not embedded in said database statement;

wherein said tag specifies at least one parameter field and at least one parameter value;

in response to receiving the request, said database server storing information from the tag in a manner that is associated with said database statement and accessible to a tag access mechanism; and

said database server executing said database statement, wherein during execution of said database statement said database server provides access to one or more of the at least one parameter value through said tag access mechanism provided by said database server.

15. The non-transitory machine-readable storage medium of claim 14, wherein the database statement is written in a language in which results desired are specified by the database statement, but no procedures for obtaining the results desired are specified by the database statement.

16. The non-transitory machine-readable storage medium of claim 14, wherein a priority for executing the database statement is determined based on the at least one parameter value.

17. The non-transitory machine-readable storage medium of claim 14, wherein the at least one parameter is accessible to a systems administrator.

18. The non-transitory machine-readable storage medium of claim 14, wherein the at least one parameter is related to user context information.

19. The non-transitory machine-readable storage medium of claim 14, wherein the tag comprises an indicator of a beginning of the tag, and an indicator of an end of the tag.

20. The non-transitory machine-readable storage medium of claim 19, wherein the at least one parameter value is located between the indicator of the beginning and the indicator of the end of the tag.

21. The non-transitory machine-readable storage medium of claim 20, wherein each of the at least one parameter fields comprises an indicator of a beginning of the parameter field, followed by the parameter value, which in turn is followed by an indicator of an end of the parameter field.

22. The non-transitory machine-readable storage medium of claim 14, wherein the at least one parameter value can be accessed without accessing memory allocated to a database session, wherein the database statement was issued within the database session.

23. The non-transitory machine-readable storage medium of claim 15, wherein the at least one parameter value can be accessed without accessing-memory allocated to a database session, wherein the database statement was issued within the database session.

24. The non-transitory machine-readable storage medium of claim 14, wherein the at least one parameter value can be accessed after a session window has closed, wherein the database statement was issued within the session window.

25. The non-transitory machine-readable storage medium of claim 14, wherein a security level is associated with the at least one parameter such that whether the database is entitled to access a component is based on the at least one parameter.

26. The non-transitory machine-readable storage medium of claim 25, wherein the at least one parameter value can be accessed without accessing-memory allocated to a database session, wherein the database statement was issued within the database session.